The Catalog holds three versions of the Helm chart bitnami/postgresql, with 6 bases across them. The newest is 18.7.0.
The Catalog files this chart under Databases and messaging. Its listings do not yet describe what it does, so read the objects before you rely on the name.
The Catalog rendered all 6 bases and retains the exact objects of each. The listings record an upload as a variant for 6 bases. They record no deployment for any base. A promoted change is partly recorded for 6 bases.
Use this entry in ConfigHub in five steps, from fetching its exact objects to promoting a change.
Pick a version · See what changes · Back to the Catalog
Guides. Make a stack from Catalog entries shows how to combine this chart with others and check them together.
What it is. bitnami/postgresql 18.7.0, as 6 Kubernetes objects in its existing-secret preset.
Install it. Use its installer package with cub installer. The five steps below give the commands.
How it works. How the model works, and Helm in the Catalog.
Versions are listed newest first. Each row is one base, and every cell is read from that base's listing. A base marked watch has a checked result with a limit to review.
2 bases. The installer package is published and signed. Open the page for 18.7.0.
| Base | Objects | Flattening verdict | Published as OCI | Flag | Open |
|---|---|---|---|---|---|
| static-passwords | 7 | unsafe-to-flatten | Not published | None | exact objects · listing |
| existing-secret default | 6 | unsafe-to-flatten | Not published | None | exact objects · listing |
2 bases. The installer package is published and signed. Open the page for 18.6.10.
| Base | Objects | Flattening verdict | Published as OCI | Flag | Open |
|---|---|---|---|---|---|
| static-passwords | 7 | unsafe-to-flatten | Not published | None | exact objects · listing |
| existing-secret default | 6 | unsafe-to-flatten | Not published | None | exact objects · listing |
2 bases. The installer package is published and signed. Open the page for 18.6.7.
| Base | Objects | Flattening verdict | Published as OCI | Flag | Open |
|---|---|---|---|---|---|
| static-passwords | 7 | unsafe-to-flatten | Not published | None | exact objects · listing |
| existing-secret default | 6 | unsafe-to-flatten | Not published | None | exact objects · listing |
Choose two versions or two bases, then press Compare. The page fetches the two retained files and checks each file's SHA-256 against the digest its listing records. It then computes the diff on demand, in your browser, with the code that cub config diff runs. Nothing is precomputed or stored.
These commands fetch the same two files and compare them on your machine, with no account. They follow the pair you choose above. cub plugin install confighub/cub-workshop@v0.6.61 adds cub config diff.
# fetch the first retained file
$ curl -fsSL -o bitnami-postgresql-18-6-10-existing-secret.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/bitnami/postgresql/18.6.10/revisions/existing-secret/r001/rendered/release-objects.yaml
# fetch the second retained file
$ curl -fsSL -o bitnami-postgresql-18-7-0-existing-secret.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/bitnami/postgresql/18.7.0/revisions/existing-secret/r001/rendered/release-objects.yaml
# check the bytes against the two listings
$ shasum -a 256 bitnami-postgresql-18-6-10-existing-secret.yaml bitnami-postgresql-18-7-0-existing-secret.yaml
dfbd333f2a1842ca8af06c501cf0b9719fd1b121fc5ee87b78a1cd3253f9497a bitnami-postgresql-18-6-10-existing-secret.yaml
bdcfa750a9553ede16f5718d0189d3616820e3ba1422eb82a8217f54c3c70dd2 bitnami-postgresql-18-7-0-existing-secret.yaml
# count what changes
$ cub config diff bitnami-postgresql-18-6-10-existing-secret.yaml bitnami-postgresql-18-7-0-existing-secret.yaml --summary
# list every changed field
$ cub config diff bitnami-postgresql-18-6-10-existing-secret.yaml bitnami-postgresql-18-7-0-existing-secret.yamlThese lines are the only diff content this page stores. Each one was computed when the site was generated, by the same code, on the default base of both versions.
Every Catalog entry page carries these five steps in this order. Each step says what the Catalog has run for this entry, and a step with a missing precondition gives no command.
Steps 1 and 2 need no account. Install the cub CLI before any cub command. Step 2 uses cub config diff, which cub plugin install confighub/cub-workshop@v0.6.61 adds. A live walk on 2026-10-08 ran steps 3 to 5 for bitnami-nginx-24-0-2-http-clusterip and nvidia-gpu-operator-v26-3-3-default. These commands carry the changes that walk needed. It is a dated log and no receipt, so no state on this page rests on it. These are the steps for 18.7.0, the newest version, on its existing-secret base.
Fixed when this entry was built. These went into the build, so the objects already carry them. To change one, build the entry again from its source.
chart is bitnami/postgresqlversion is 18.7.0base is existing-secretvaluesProfile is recipes/bitnami/postgresql/18.7.0/effective-values-existing-secret.yamlnamespace is postgresqlreleaseName is postgresqlcapabilityProfile is {"apiVersions":[],"kubeVersion":"1.30.0"}Yours to supply or check. The destination must have these before the objects are applied. The words in italics say what the Catalog knows about each.
The record lists no plan step for this entry.
Compared with plain Helm. The Catalog installed this base beside plain Helm on two local clusters, and the two matched. Read the receipt.
The Catalog rendered this entry and retains its 6 objects in one file.
An upload can create more Units than the objects counted here. The installer renders a Namespace, and the upload adds an installer-record Unit.
Here is what the command does. cub installer is an open-source plugin for the cub CLI. cub installer setup pulls a catalog package and writes its Kubernetes files locally, leaving delivery to kubectl, Argo CD or Flux. The generated scripts stop before doing any work when the plugin or kustomize is missing.
# fetch the retained objects for this entry
$ curl -fsSL -o bitnami-postgresql-18-7-0-existing-secret.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/bitnami/postgresql/18.7.0/revisions/existing-secret/r001/rendered/release-objects.yaml
# check the bytes against the listing
$ shasum -a 256 bitnami-postgresql-18-7-0-existing-secret.yaml
bdcfa750a9553ede16f5718d0189d3616820e3ba1422eb82a8217f54c3c70dd2 bitnami-postgresql-18-7-0-existing-secret.yaml
# render this base from the signed package; step 3 uploads this directory
$ cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-postgresql:18.7.0@sha256:cf2cfeae128c4ede5cfa9ac65bdf241b557d59a1badacdd107e044caadb0d353 --base existing-secret --work-dir ./bitnami-postgresql-18-7-0-existing-secret --non-interactive --namespace postgresqlThe listing records no comparison for this entry. The commands run on the retained files, with no account. This version has one other base in the Catalog, static-passwords. The Catalog holds 2 other versions, 18.6.7 and 18.6.10.
# fetch the static-passwords base of the same version
$ curl -fsSL -o bitnami-postgresql-18-7-0-static-passwords.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/bitnami/postgresql/18.7.0/revisions/static-passwords/r001/rendered/release-objects.yaml
# list what differs between the two bases
$ cub config diff bitnami-postgresql-18-7-0-existing-secret.yaml bitnami-postgresql-18-7-0-static-passwords.yaml --summary
# fetch the existing-secret base at version 18.6.10
$ curl -fsSL -o bitnami-postgresql-18-6-10-existing-secret.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/bitnami/postgresql/18.6.10/revisions/existing-secret/r001/rendered/release-objects.yaml
# list what changed from 18.6.10 to 18.7.0
$ cub config diff bitnami-postgresql-18-6-10-existing-secret.yaml bitnami-postgresql-18-7-0-existing-secret.yaml --summaryThe Catalog saved this entry in ConfigHub. The commands use its signed installer package. Read the log of the live walk on 2026-10-08 · Read the record that states this.
Replace each value in angle brackets with a name of your own. The entry id may already exist as a Space in your organization, and the package name as a Component.
In the live walk, a Space named for the nginx entry's id and a Component named bitnami-nginx already existed, so the walk chose its own names. The --component flag sets the Component label the upload writes on the Space, which is the package name when you omit it.
The cub installer plugin reads your organization from CUB_CONTEXT and ignores --context. If you use a context other than your default, export CUB_CONTEXT first, or the plugin works in your default organization.
# sign in; steps 3 to 5 write to your ConfigHub organization
$ cub auth login
# upload step 1's directory as a Space of Units, under names you choose
$ cub installer upload --work-dir ./bitnami-postgresql-18-7-0-existing-secret --space <your-space> --component <your-component>
# list the Units the upload created
$ cub unit list --space <your-space>No delivery run is recorded for this entry. Argo CD has not run, Flux has not run, and kubectl has not run. The commands name the Target workshop/target, which cub cluster up --name workshop creates on a local kind cluster with Argo CD. Use your own Target for a real destination. The listing records one input that the destination must supply, so read it before you deploy. The coverage lanes record a local Kubernetes run and a GitOps OCI run for this base. They are separate from the delivery record this step reads. Read the log of the live walk on 2026-10-08.
Use the Space name you chose in step 3. The delete command is needed because the cloned installer-record Unit carries the Target and Argo CD v3.5.4 cannot read it, a defect seen on cub v0.8.7 and server v0.8.9.
Without that line the walk deployed nothing and Argo CD showed Unknown, while every cub command exited 0. The walk ran the four commands in this order and did not try them without the first publish.
ConfigHub shows nothing when Argo CD fails to read a Release. Run kubectl -n argocd get applications.argoproj.io and read the Sync column, because Healthy alone is not a pass. Argo CD took between 18 seconds and about 5 minutes to read a Release on a cluster made without argobot.
The walk made its cluster with cub cluster up --no-argobot. That command creates two Spaces, a Worker, a Target and a Trigger, opens ports 30010 to 30019 on the machine, and installs Argo CD from an unpinned upstream manifest.
Removing the ConfigHub side does not remove the workload. In the walk, deleting the Application Unit and the Spaces left the Application and its pods running, because the root Application does not prune.
# clone the base onto a Target as a dev variant
$ cub variant create dev <your-space> --target workshop/target --space-pattern "template:<your-space>-dev"
# publish the Release that the cluster's Argo CD pulls
$ cub release publish <your-space>-dev
# delete the installer record, which Argo CD cannot read
$ cub unit delete --space <your-space>-dev installer-record
# publish again without it
$ cub release publish <your-space>-devA promotion ran for this entry and left a limit to review. It ran the preview and the promote. The delete and the publish below have no recorded run for this entry. Promotion carries a change in the base to the dev variant. The base changes when you edit a Unit or upload a newer version into the same Space. Read the log of the live walk on 2026-10-08 · Read the record that states this.
The promotion changes the dev Space and publishes nothing. It also adds the installer-record Unit back with the Target. The change reaches the cluster only after the delete and the publish.
The preview lists the whole installer record as added. In the walk, the preview of a one-label change to gpu-operator ran to 405 lines, and about 400 of them were that record.
# preview what the dev variant would take from the base
$ cub variant promote <your-space>-dev --dry-run -o mutations
# promote once you have read the preview
$ cub variant promote <your-space>-dev --change-desc "Pull the reviewed base forward"
# delete the installer record that the promotion adds back
$ cub unit delete --space <your-space>-dev installer-record
# publish the Release that carries the change
$ cub release publish <your-space>-devEvery other base carries the same five steps, with its own states and commands, on the page of its version.
One file holds everything on this page in a form a program can read.