[{"_1":2,"_142":-5,"_143":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_136":137},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_27":28,"_29":30,"_59":60,"_61":-7,"_62":-7,"_63":-7,"_64":-7,"_65":-5,"_66":-5,"_67":11,"_68":11,"_52":69,"_126":21,"_94":95,"_127":93,"_128":51,"_35":36,"_129":11,"_130":21,"_131":132,"_133":-5,"_134":11,"_135":11},"scanningType","none","tagData",{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},"content_type","image","creator",29930447,"digest","sha256:daa747afcdb9d2117803ae8fc3878a38fad67d93ad1fa79355532097ecdf2a80","full_size",7947,"id",910603343,"images",[],"last_updated","2025-06-03T19:36:04.796405Z","last_updater","last_updater_username","bitnamirobot","media_type","application/vnd.oci.image.index.v1+json","name","sha256-1aa15c2f221151e577cc5d6071de0cebf77a070a93bbbe1d907634d853054f89","repository",19064421,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_70":71,"_76":77,"_80":81,"_82":83,"_84":11,"_43":85,"_86":87,"_88":89,"_50":93,"_94":95,"_96":97,"_98":32,"_99":100,"_101":100,"_102":103,"_104":-5,"_105":106,"_107":108,"_109":11,"_110":95,"_111":112,"_117":11,"_118":119,"_123":95,"_124":125},"categories",[72],{"_50":73,"_74":75},"Integration & delivery","slug","integration-and-delivery","content_types",[78,79,32],"unrecognized","helm","date_registered","2023-01-24T10:54:25.437432Z","description","Bitnami Helm chart for Concourse","is_private","2025-08-07T20:51:13.563752Z","last_modified","2026-03-16T14:23:21.529458Z","media_types",[90,91,49,92],"application/vnd.cncf.helm.config.v1+json","application/vnd.oci.image.config.v1+json","application/vnd.vmware.tac.metadata.config.v1+json","concourse","namespace","bitnamicharts","pull_count",951026,"repository_type","star_count",1,"status","status_description","active","source","collaborator_count",0,"full_description","\n\n# Bitnami Secure Images Helm chart for Concourse\n\nConcourse is an automation system written in Go. It is most commonly used for CI/CD, and is built to scale to any kind of automation pipeline, from simple to complex.\n\n[Overview of Concourse](https://concourse-ci.org/)\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/concourse\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository.\n\n## Introduction\n\nThis chart bootstraps a [Concourse](https://concourse-ci.org/) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.\n\nIt also packages [Bitnami Postgresql](https://github.com/bitnami/charts/tree/main/bitnami/postgresql)\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n- PV provisioner support in the underlying infrastructure\n- ReadWriteMany volumes for deployment scaling\n\n## Installing the Chart\n\nTo install the chart with the release name `my-release`:\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/concourse\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\nThe command deploys concourse on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.\n\n> **Tip**: List all releases using `helm list`\n\n## Configuration and installation details\n\nThis section describes credentials, configuration, and other installation options.\n\n### Resource requests and limits\n\nBitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.\n\nTo make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcesPreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).\n\n### [Rolling vs Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-understand-rolling-tags-containers-index.html)\n\nIt is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.\n\nBitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.\n\n### Use an external database\n\nSometimes, you may want to have Concourse connect to an external database rather than a database within your cluster - for example, when using a managed database service, or when running a single database server for all your applications. To do this, set the `postgresql.enabled` parameter to `false` and specify the credentials for the external database using the `externalDatabase.*` parameters. Here is an example:\n\n```text\npostgresql.enabled=false\nexternalDatabase.host=myexternalhost\nexternalDatabase.user=myuser\nexternalDatabase.password=mypassword\nexternalDatabase.database=mydatabase\nexternalDatabase.port=5432\n```\n\n### Update credentials\n\nThe Bitnami Concourse chart, when upgrading, reuses the secret previously rendered by the chart or the one specified in `web.existingSecret`. To update credentials, use one of the following:\n\n- Run `helm upgrade` specifying a new \"user:password\" in `secrets.localUsers`\n- Run `helm upgrade` specifying a new secret in `web.existingSecret`\n\n### Gateway API\n\nThis chart provides support for exposing Concourse using the [Gateway API](https://gateway-api.sigs.k8s.io/) and its `HTTPRoute` resource. If you have a Gateway controller installed on your cluster, such as APISIX, Contour, Envoy Gateway, NGINX Gateway Fabric or Kong Ingress Controller you can utilize the Gateway controller to serve your application. To enable Gateway API integration, set `httpRoute.enabled` to `true`.\nThe Gateway to be used can be customized by setting the `httpRoute.parentRefs` parameter. By default, it will reference a Gateway named `gateway` in the same namespace as the release.\n\nYou can specify the list of hostnames to be mapped to the deployment using the `httpRoute.hostnames` parameter. Additionally, you can customize the rules used to route the traffic to the service by modifying the `httpRoute.matches` and `httpRoute.filters` parameters or adding new rules using the `httpRoute.extraRules` parameter.\n\nThis chart also supports creating a `BackendTLSPolicy` to define the SNI the Gateway should use to connect to the Concourse backend pods and how the certificate served by these pods should be verified. To do so, set the `backendTLSPolicy.enabled` parameter to `true`. Please note it's required to secure traffic using TLS as explained in the [Securing traffic using TLS](#securing-traffic-using-tls) section to be able to use this feature.\n\n### Ingress\n\nThis chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/main/bitnami/contour) you can utilize the ingress controller to serve your application. To enable Ingress integration, set `ingress.enabled` to `true`.\n\nThe most common scenario is to have one host name mapped to the deployment. In this case, the `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host.\n\nHowever, it is also possible to have more than one host. To facilitate this, the `ingress.extraHosts` parameter (if available) can be set with the host names specified as an array. The `ingress.extraTLS` parameter (if available) can also be used to add the TLS configuration for extra hosts.\n\n> NOTE: For each host specified in the `ingress.extraHosts` parameter, it is necessary to set a name, path, and any annotations that the Ingress controller should know about. Not all annotations are supported by all Ingress controllers, but [this annotation reference document](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md) lists the annotations supported by many popular Ingress controllers.\n\nAdding the TLS parameter (where available) will cause the chart to generate HTTPS URLs, and the application will be available on port 443. The actual TLS secrets do not have to be generated by this chart. However, if TLS is enabled, the Ingress record will not work until the TLS secret exists.\n\n[Learn more about Ingress controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/).\n\n### Configure TLS Secrets for use with Ingress\n\nThis chart facilitates the creation of TLS secrets for use with the Ingress controller (although this is not mandatory). There are several common use cases:\n\n- Generate certificate secrets based on chart parameters.\n- Enable externally generated certificates.\n- Manage application certificates via an external service (like [cert-manager](https://github.com/jetstack/cert-manager/)).\n- Create self-signed certificates within the chart (if supported).\n\nIn the first two cases, a certificate and a key are needed. Files are expected in `.pem` format.\n\nHere is an example of a certificate file:\n\n> NOTE: There may be more than one certificate if there is a certificate chain.\n\n```text\n-----BEGIN CERTIFICATE-----\nMIID6TCCAtGgAwIBAgIJAIaCwivkeB5EMA0GCSqGSIb3DQEBCwUAMFYxCzAJBgNV\n...\njScrvkiBO65F46KioCL9h5tDvomdU1aqpI/CBzhvZn1c0ZTf87tGQR8NK7v7\n-----END CERTIFICATE-----\n```\n\nHere is an example of a certificate key:\n\n```text\n-----BEGIN RSA PRIVATE KEY-----\nMIIEogIBAAKCAQEAvLYcyu8f3skuRyUgeeNpeDvYBCDcgq+LsWap6zbX5f8oLqp4\n...\nwrj2wDbCDCFmfqnSJ+dKI3vFLlEz44sAV8jX/kd4Y6ZTQhlLbYc=\n-----END RSA PRIVATE KEY-----\n```\n\n- If using Helm to manage the certificates based on the parameters, copy these values into the `certificate` and `key` values for a given `*.ingress.secrets` entry.\n- If managing TLS secrets separately, it is necessary to create a TLS secret with name `INGRESS_HOSTNAME-tls` (where INGRESS_HOSTNAME is a placeholder to be replaced with the hostname you set using the `*.ingress.hostname` parameter).\n- If your cluster has a [cert-manager](https://github.com/jetstack/cert-manager) add-on to automate the management and issuance of TLS certificates, add to `*.ingress.annotations` the [corresponding ones](https://cert-manager.io/docs/usage/ingress/#supported-annotations) for cert-manager.\n- If using self-signed certificates created by Helm, set both `*.ingress.tls` and `*.ingress.selfSigned` to `true`.\n\n### Securing traffic using TLS\n\nBy default, this chart assumes TLS is managed by the Ingress Controller and terminates the TLS connection in the Ingress Controller. This can be done by setting `ingress.enabled` and `ingress.tls` parameters to `true` as explained in the section above. However, it is possible to configure TLS encryption for Concourse web directly by setting `web.tls.enabled` parameter to `true`.\n\nIt is necessary to create a secret containing the TLS certificates and pass it to the chart via the `web.tls.existingSecret` parameter. The secret should contain a `tls.crt` and `tls.key` keys including the certificate and key files respectively.\n\nYou can manually create the required TLS certificates or relying on the chart auto-generation capabilities. The chart supports two different ways to auto-generate the required certificates:\n\n- Using Helm capabilities. Enable this feature by setting `web.tls.autoGenerated.enabled` to `true` and `web.tls.autoGenerated.engine` to `helm`.\n- Relying on CertManager (please note it's required to have CertManager installed in your K8s cluster). Enable this feature by setting `web.tls.autoGenerated.enabled` to `true` and `web.tls.autoGenerated.engine` to `cert-manager`. Please note it's supported to use an existing Issuer/ClusterIssuer for issuing the TLS certificates by setting the `web.tls.autoGenerated.certManager.existingIssuer` and `web.tls.autoGenerated.certManager.existingIssuerKind` parameters.\n\n### Configure extra environment variables\n\nTo add extra environment variables (useful for advanced operations like custom init scripts), use the `extraEnvVars` property.\n\n```yaml\nextraEnvVars:\n - name: LOG_LEVEL\n value: DEBUG\n```\n\nAlternatively, use a ConfigMap or a Secret with the environment variables. To do so, use the `extraEnvVarsCM` or the `extraEnvVarsSecret` values.\n\n### Configure Sidecars and Init Containers\n\nIf additional containers are needed in the same pod as Concourse (such as additional metrics or logging exporters), they can be defined using the `sidecars` parameter.\n\n```yaml\nsidecars:\n- name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nIf these sidecars export extra ports, extra port definitions can be added using the `service.extraPorts` parameter (where available), as shown in the example below:\n\n```yaml\nservice:\n extraPorts:\n - name: extraPort\n port: 11311\n targetPort: 11311\n```\n\n> NOTE: This Helm chart already includes sidecar containers for the Prometheus exporters (where applicable). These can be activated by adding the `--enable-metrics=true` parameter at deployment time. The `sidecars` parameter should therefore only be used for any extra sidecar containers.\n\nIf additional init containers are needed in the same pod, they can be defined using the `initContainers` parameter. Here is an example:\n\n```yaml\ninitContainers:\n - name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nLearn more about [sidecar containers](https://kubernetes.io/docs/concepts/workloads/pods/) and [init containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/).\n\n### Set Pod affinity\n\nThis chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).\n\nAs an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.\n\n### Backup and restore\n\nTo back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-backup-restore-deployments-velero-index.html).\n\n### FIPS parameters\n\nThe FIPS parameters only have effect if you are using images from the [Bitnami Secure Images catalog](https://go-vmware.broadcom.com/contact-us).\n\nFor more information on this new feature, please refer to the [FIPS Compliance section](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html).\n\n## Persistence\n\nThe [Bitnami Concourse](https://github.com/bitnami/containers/tree/main/bitnami/concourse) image stores the concourse data and configurations at the `/bitnami` path of the container. Persistent Volume Claims are used to keep the data across deployments.\n\n## Parameters\n\nThe following subsections list global, common, and component-specific parameters.\n\n### Global parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| `global.imageRegistry` | Global Docker image registry | `\"\"` |\n| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |\n| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `\"\"` |\n| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |\n| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `disabled` |\n| `global.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\n| `global.postgresql.auth.username` | PostgreSQL username (overrides `postgresql.auth.username`) | `\"\"` |\n| `global.postgresql.auth.password` | PostgreSQL password (overrides `postgresql.auth.password`) | `\"\"` |\n| `global.postgresql.auth.database` | PostgreSQL database (overrides `postgresql.auth.database`) | `\"\"` |\n| `global.postgresql.auth.existingSecret` | Name of existing secret to use for PostgreSQL credentials (overrides `postgresql.auth.existingSecret`) | `\"\"` |\n\n### Common parameters\n\n| Name | Description | Value |\n| ------------------------ | --------------------------------------------------------------------------------------- | --------------- |\n| `kubeVersion` | Override Kubernetes version | `\"\"` |\n| `nameOverride` | String to partially override common.names.fullname | `\"\"` |\n| `fullnameOverride` | String to fully override common.names.fullname | `\"\"` |\n| `clusterDomain` | Kubernetes Cluster Domain | `cluster.local` |\n| `commonLabels` | Labels to add to all deployed objects | `{}` |\n| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |\n| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |\n| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |\n| `diagnosticMode.command` | Command to override all containers in the deployment(s)/statefulset(s) | `[\"sleep\"]` |\n| `diagnosticMode.args` | Args to override all containers in the deployment(s)/statefulset(s) | `[\"infinity\"]` |\n\n### Common Concourse Parameters\n\n| Name | Description | Value |\n| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- |\n| `image.registry` | image registry | `REGISTRY_NAME` |\n| `image.repository` | image repository | `REPOSITORY_NAME/concourse` |\n| `image.digest` | image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `image.pullPolicy` | image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | image pull secrets | `[]` |\n| `secrets.localAuth.enabled` | the use of local authentication (basic auth). | `true` |\n| `secrets.localUsers` | List of `username:password` or `username:bcrypted_password` combinations for all your local concourse users. Auto-generated if not set | `\"\"` |\n| `secrets.teamAuthorizedKeys` | Array of team names and public keys for team external workers | `[]` |\n| `secrets.conjurAccount` | Account for Conjur auth provider. | `\"\"` |\n| `secrets.conjurAuthnLogin` | Host username for Conjur auth provider. \n\n_Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-charts-concourse-index.html_","has_starred","hub_user","immutable_tags_settings",{"_113":11,"_114":115},"enabled","rules",[116],".*","is_automated","permissions",{"_120":21,"_121":11,"_122":11},"read","write","admin","user","storage_size",21650274,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_27":28,"_63":-7,"_61":-7,"_62":-7,"_29":138,"_35":36,"_140":-7,"_141":11},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":139,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/concourse:sha256-1aa15c2f221151e577cc5d6071de0cebf77a070a93bbbe1d907634d853054f89