[{"_1":2,"_139":-5,"_140":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_133":134},"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,"_123":21,"_91":92,"_124":90,"_125":51,"_35":36,"_126":11,"_127":21,"_128":129,"_130":-5,"_131":11,"_132":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",35095401,"digest","sha256:eb006b298177e647d5232b4915844b2c9ae5d02e98c43b97216fe5c1a68d3a97","full_size",7947,"id",916851389,"images",[],"last_updated","2025-06-13T21:49:43.25667Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.index.v1+json","name","sha256-c6ba8ba89eacec6ec418ede66b72237246183a59f60ac4bd4c3f4733b51ffaf8","repository",26573949,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_70":71,"_76":77,"_79":80,"_81":82,"_83":11,"_43":84,"_85":86,"_87":88,"_50":90,"_91":92,"_93":94,"_95":-5,"_96":97,"_98":99,"_100":101,"_102":-5,"_103":97,"_104":105,"_106":11,"_107":92,"_108":109,"_114":11,"_115":116,"_120":92,"_121":122},"categories",[72],{"_50":73,"_74":75},"Databases & storage","slug","databases-and-storage","content_types",[78,32],"helm","date_registered","2025-02-26T02:09:03.725726Z","description","Bitnami Helm chart for CloudNativePG","is_private","2025-08-07T21:57:34.738324Z","last_modified","2026-03-19T16:23:02.879789Z","media_types",[89,49],"application/vnd.cncf.helm.config.v1+json","cloudnative-pg","namespace","bitnamicharts","pull_count",468085,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for CloudNativePG\n\nCloudNativePG is an open-source tool for managing PostgreSQL databases on Kubernetes, from setup to ongoing upkeep.\n\n[Overview of CloudNativePG](https://cloudnative-pg.io/)\n\nTrademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/cloudnative-pg\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 [CloudNativePG](https://github.com/bitnami/containers/tree/main/bitnami/cloudnative-pg) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n\n## Installing the Chart\n\nTo install the chart with the release name `my-release`:\n\n```console\nhelm install my-release REGISTRY_NAME/REPOSITORY_NAME/cloudnative-pg\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 CloudNativePG 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### Operator configuration\n\nThe Bitnami CloudNativePG chart allows [configuring the operator](https://cloudnative-pg.io/documentation/current/operator_conf/#available-options) using ConfigMaps and Secrets. This is done using the `operator.configuration` and `operator.secretConfiguration` parameters. Both are values are compatible, and the configuration in the `operator.secretConfiguration` section takes precedence over the `operator.configuration` section. In the example below we add extra configuration parameters to the operator:\n\n```yaml\noperator:\n configuration:\n EXPIRING_CHECK_THRESHOLD: 12\n secretConfiguration:\n CERTIFICATE_DURATION: 120\n```\n\nIt is also possible to use existing ConfigMaps and Secrets using the `operator.existingConfigMap` and `operator.existingSecret` parameters (note that these are not compatible with the `operator.configuration` and `operator.secretConfiguration` parameters).\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` (under the `operator` and `pluginBarmanCloud` sections) 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` (under the `operator` and `pluginBarmanCloud` sections) values, which automatically sets the `*.resources` (under the `operator` and `pluginBarmanCloud` sections) 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### Backup and restore\n\nThe Bitnami CloudNativePG chart includes the [plugin-barman-cloud](https://cloudnative-pg.io/plugin-barman-cloud/) for performing backup operations. This is enabled by setting `pluginBarmanCloud.enabled=true`:\n\n```yaml\npluginBarmanCloud:\n enabled: true\n```\n\nCheck the upstream [plugin-barman-cloud](https://cloudnative-pg.io/plugin-barman-cloud/docs/intro/) on how to deploy `BarmanObjectStore` objects and enabling backup operations.\n\n### Prometheus metrics\n\nThis chart can be integrated with Prometheus by setting `*.metrics.enabled` (under the `operator` and `pluginBarmanCloud` sections) to true. This will expose the cloudnative-pg native Prometheus endpoint in a `metrics` service, which can be configured under the `*.metrics.service` (under the `operator` and `pluginBarmanCloud` sections) section. It will have the necessary annotations to be automatically scraped by Prometheus.\n\nFor the PostgreSQL instances themselves, the chart deploys a monitoring queries ConfigMap or Secret with basic queries. These can be configured under the `operator.metrics.monitoringQueries` section.\n\n#### Prometheus requirements\n\nIt is necessary to have a working installation of Prometheus or Prometheus Operator for the integration to work. Install the [Bitnami Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/prometheus) or the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) to easily have a working Prometheus in your cluster.\n\n#### Integration with Prometheus Operator\n\nThe chart can deploy `ServiceMonitor` objects for integration with Prometheus Operator installations. To do so, set the value `*.metrics.serviceMonitor.enabled=true` (under the `operator` and `pluginBarmanCloud` sections). Ensure that the Prometheus Operator `CustomResourceDefinitions` are installed in the cluster or it will fail with the following error:\n\n```text\nno matches for kind \"ServiceMonitor\" in version \"monitoring.coreos.com/v1\"\n```\n\nInstall the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) for having the necessary CRDs and the Prometheus Operator.\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### Additional environment variables\n\nIn case you want to add extra environment variables (useful for advanced operations like custom init scripts), you can use the `extraEnvVars` property inside the `operator` and `pluginBarmanCloud` sections:\n\n```yaml\noperator:\n extraEnvVars:\n - name: LOG_LEVEL\n value: error\n```\n\nAlternatively, you can use a ConfigMap or a Secret with the environment variables. To do so, use the `extraEnvVarsCM` or the `extraEnvVarsSecret` values inside the `operator` and `pluginBarmanCloud` sections.\n\n### Sidecars\n\nIf additional containers are needed in the same pod as cloudnative-pg (such as additional metrics or logging exporters), they can be defined using the `sidecars` parameter inside the `operator` and `pluginBarmanCloud` sections:\n\n```yaml\noperator:\n sidecars:\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\noperator:\n service:\n extraPorts:\n - name: extraPort\n port: 11311\n targetPort: 11311\n```\n\nIf additional init containers are needed in the same pod, they can be defined using the `initContainers` parameter inside the `operator` and `pluginBarmanCloud` sections. 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### Deploying extra resources\n\nApart from the Operator, you may want to deploy PostgreSQL Cluster, ImageCatalog or other operator objects. For covering this case, the chart allows adding the full specification of other objects using the `extraDeploy` parameter. The following example would creates a PostgreSQL Cluster object with a secret containing the credentials of a role:\n\n```yaml\nextraDeploy:\n- apiVersion: v1\n kind: Secret\n metadata:\n name: my-cluster-example-user\n labels:\n cnpg.io/reload: \"true\"\n type: kubernetes.io/basic-auth\n stringData:\n username: my_user\n password: bitnami1234\n- apiVersion: postgresql.cnpg.io/v1\n kind: Cluster\n metadata:\n name: my-cluster-example\n spec:\n instances: 3\n storage:\n size: 1Gi\n managed:\n roles:\n - name: my_user\n ensure: present\n comment: MY User\n login: true\n superuser: true\n passwordSecret:\n name: my-cluster-example-user\n```\n\nCheck the [CloudNativePG official documentation](https://cloudnative-pg.io/documentation/current/) for the list of available objects.\n\n### Pod affinity\n\nThis chart allows you to set your custom affinity using the `affinity` parameter inside the `operator` and `pluginBarmanCloud` sections. 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 inside the `operator` and `pluginBarmanCloud` sections.\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 support, 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## 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.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\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) | `auto` |\n\n### Common parameters\n\n| Name | Description | Value |\n| ------------------- | ---------------------------------------------------------- | --------------- |\n| `kubeVersion` | Override Kubernetes version | `\"\"` |\n| `apiVersions` | Override Kubernetes API versions reported by .Capabilities | `[]` |\n| `nameOverride` | String to partially override common.names.name | `\"\"` |\n| `fullnameOverride` | String to fully override common.names.fullname | `\"\"` |\n| `namespaceOverride` | String to fully override common.names.namespace | `\"\"` |\n| `commonLabels` | Labels to add to all deployed objects | `{}` |\n| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |\n| `clusterDomain` | Kubernetes cluster domain name | `cluster.local` |\n| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |\n\n### cloudnative-pg operator parameters\n\n| Name | Description | Value |\n| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |\n| `operator.image.registry` | cloudnative-pg Operator image registry | `REGISTRY_NAME` |\n| `operator.image.repository` | cloudnative-pg Operator image repository | `REPOSITORY_NAME/cloudnative-pg` |\n| `operator.image.digest` | cloudnative-pg Operator image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag image tag (immutable tags are recommended) | `\"\"` |\n| `operator.image.pullPolicy` | cloudnative-pg Operator image pull policy | `IfNotPresent` |\n| `operator.image.pullSecrets` | cloudnative-pg Operator image pull secrets | `[]` |\n| `operator.image.debug` | Enable cloudnative-pg Operator image debug mode | `false` |\n| `operator.fips.openssl` | Configure OpenSSL FIPS mode: '', 'restricted', 'relaxed', 'off'. If empty (\"\"), 'global.defaultFips' would be used | `\"\"` |\n| `operator.fips.golang` | Configure Golang FIPS mode: '', 'restricted', 'relaxed', 'off'. If empty (\"\"), 'global.defaultFips' would be used | `relaxed` |\n| `operator.postgresqlImage.registry` | PostgreSQL image registry | `REGISTRY_NAME` |\n| `operator.postgresqlImage.repository` | PostgreSQL image repository | `REPOSITORY_NAME/postgresql` |\n| `operator.postgresqlImage.digest` | PostgreSQL image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `operator.replicaCount` | Number of cloudnative-pg Operator replicas to deploy | `1` |\n| `operator.containerPorts.metrics` | cloudnative-pg Operator metrics container port | `8080` |\n| `operator.containerPorts.webhook` | cloudnative-pg Operator webhook container port | `9443` |\n| `operator.livenessProbe.enabled` | Enable livenessProbe on cloudnative-pg Operator containers | `true` |\n| `operator.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `5` |\n| `operator.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `10` |\n| `operator.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `5` |\n| `operator.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `5` |\n| `operator.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` |\n| `operator.readinessProbe.enabled` | Enable readinessProbe on cloudnative-pg Operator containers | `true` |\n| `operator.readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `5` |\n| `operator.readinessProbe.periodSeconds` | Period seconds for readinessProbe | `10` |\n| `operator.readinessProbe.timeoutSeconds` | Timeout seconds for readinessProbe | `5` |\n| `operator.readinessProbe.failureThreshold` | Failure threshold for readinessProbe \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-cloudnative-pg-index.html_","has_starred","hub_user","immutable_tags_settings",{"_110":11,"_111":112},"enabled","rules",[113],".*","is_automated","permissions",{"_117":21,"_118":11,"_119":11},"read","write","admin","user","storage_size",6251813,"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":135,"_35":36,"_137":-7,"_138":11},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":136,"_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/cloudnative-pg:sha256-c6ba8ba89eacec6ec418ede66b72237246183a59f60ac4bd4c3f4733b51ffaf8