What it is. bitnami/postgresql 18.7.0, as 6 Kubernetes objects in its existing-secret preset. The Catalog holds 2 presets of this version.
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.
What this page gives you
This is a human-readable detail page for one retained package version. It keeps the package, base names, exact OCI identity, and publication receipt reachable without pretending this retained-only version has the richer readiness evidence attached to the bold version in the component row.
Where its settings and observations live
Each packaged configuration records Helm-derived files and installer metadata. Later ConfigHub changes belong in governed variants. Target prerequisites and live observations remain separate facts; this publication receipt does not turn them into passes.
Four Separate Questions
Inspecting a source, producing objects, checking a destination, and checking a live result are different jobs. A Catalog match is useful for comparison but is not required. A missing destination or deployment is shown as not run or blocked, not as a failed configuration.
| Question | Current answer | What it needs | Status |
|---|---|---|---|
| What do I have? | Inspect the helm source, choices, locks, and any existing output before selecting a destination. | Destination access: no Selected configuration deployed: no | Available to inspect evidence recorded |
| What will it produce? | Run the recorded Helm render step to produce the exact Kubernetes objects for this configuration. | Destination access: no Selected configuration deployed: no | Checked: passed evidence recorded |
| Can this destination accept it? | The destination has not been checked for this exact configuration. A recorded source or render result is not a destination pass. | Destination access: yes Selected configuration deployed: no | Not run no run recorded |
| Did it work? | No post-deployment result is recorded for this exact configuration. Publication, upload, or rendering is not proof that it ran correctly. | Destination access: yes Selected configuration deployed: yes | Not run no run recorded |
Open the complete assessment, source, lifecycle, and evidence record.
Try This Chart
Inspect the exact package first, then choose one of the packaged configurations. The version remains readable in the reference, and the manifest digest prevents the registry from returning different package bytes. The setup command renders files locally; it does not apply them to Kubernetes.
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.
cub installer inspect oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-postgresql:18.7.0@sha256:cf2cfeae128c4ede5cfa9ac65bdf241b557d59a1badacdd107e044caadb0d353 --json
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-interactiveRun shared local configuration checks after the package has written its Kubernetes YAML:
cub plugin install confighub/homebrew-tap@cub-scan-v0.7.3 --name scan
cub check --format json --output cub-check.json <work-dir>/out/manifestsThe check is advisory and does not apply anything.
Version tag: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-postgresql:18.7.0
Exact package: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-postgresql:18.7.0@sha256:cf2cfeae128c4ede5cfa9ac65bdf241b557d59a1badacdd107e044caadb0d353
The manifest digest comes from the committed publication receipt. cub installer refuses the pull if that exact manifest is not available.
Verify the package publisher
Run this command with cosign. It checks the expected publisher, the exact manifest digest, and the package annotations.
cosign verify --certificate-identity helm-expt-package-signer@nth-fort-499605-q5.iam.gserviceaccount.com --certificate-oidc-issuer https://accounts.google.com --annotations confighub.com/package-path=packages/bitnami/postgresql/18.7.0 --annotations confighub.com/package-sha256=30ac053e6c9b76656926b6af3659f9d8057c3686d5f77af05f540a4f981ce5f9 europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-postgresql:18.7.0@sha256:cf2cfeae128c4ede5cfa9ac65bdf241b557d59a1badacdd107e044caadb0d353A valid signature identifies who signed these package bytes. It does not show that the configuration is suitable for your cluster; use this page's checks and setup instructions for that decision.
Signature receipt · Sigstore bundle · How signature verification works
Use this entry in ConfigHub
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. This page covers 2 entries, so open the one you want. 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.
Helm chart, base existing-secret, version 18.7.0
What is fixed, and what you supply
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.
chartisbitnami/postgresqlversionis18.7.0baseisexisting-secretvaluesProfileisrecipes/bitnami/postgresql/18.7.0/effective-values-existing-secret.yamlnamespaceispostgresqlreleaseNameispostgresqlcapabilityProfileis{"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.
- PostgreSQL administrator password Declared. Not checked on any destination.
This entry's plan, and how to test it
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.
1. Get the exact objects Run for this entry
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.
# 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 postgresql2. Compare with another version or base Not run for this entry
The 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 --summary3. Upload it as a variant Run for this entry
The 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>4. Deploy it Not run for this entry
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>-dev5. Promote a change Partly run for this entry
A 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>-devHelm chart, base static-passwords, version 18.7.0
What is fixed, and what you supply
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.
chartisbitnami/postgresqlversionis18.7.0baseisstatic-passwordsvaluesProfileisrecipes/bitnami/postgresql/18.7.0/effective-values.yamlnamespaceispostgresqlreleaseNameispostgresqlcapabilityProfileis{"apiVersions":[],"kubeVersion":"1.30.0"}
Yours to supply or check. The listing records no input for the destination. The Catalog has not ruled one out for your cluster.
This entry's plan, and how to test it
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.
1. Get the exact objects Run for this entry
The Catalog rendered this entry and retains its 7 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.
# fetch the retained objects for this entry
$ 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
# check the bytes against the listing
$ shasum -a 256 bitnami-postgresql-18-7-0-static-passwords.yaml
e640101bb1c3c9ee519e04bfb6e28254f7a894c6f49b394e73756b351e5b57d1 bitnami-postgresql-18-7-0-static-passwords.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 static-passwords --work-dir ./bitnami-postgresql-18-7-0-static-passwords --non-interactive --namespace postgresql2. Compare with another version or base Not run for this entry
The 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, existing-secret. The Catalog holds 2 other versions, 18.6.7 and 18.6.10.
# fetch the existing-secret base of the same version
$ 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
# list what differs between the two bases
$ cub config diff bitnami-postgresql-18-7-0-static-passwords.yaml bitnami-postgresql-18-7-0-existing-secret.yaml --summary
# fetch the static-passwords base at version 18.6.10
$ curl -fsSL -o bitnami-postgresql-18-6-10-static-passwords.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/bitnami/postgresql/18.6.10/revisions/static-passwords/r001/rendered/release-objects.yaml
# list what changed from 18.6.10 to 18.7.0
$ cub config diff bitnami-postgresql-18-6-10-static-passwords.yaml bitnami-postgresql-18-7-0-static-passwords.yaml --summary3. Upload it as a variant Run for this entry
The 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-static-passwords --space <your-space> --component <your-component>
# list the Units the upload created
$ cub unit list --space <your-space>4. Deploy it Not run for this entry
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 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>-dev5. Promote a change Partly run for this entry
A 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>-devAvailable Configurations
static-passwordsexisting-secret- package default
The section below says what these configurations expect you to provide.
Local Configuration Checks
We ran cub check v0.7.3 against the exact rendered objects for every configuration below. The result is advisory: read each finding and decide whether it matters for your target.
Scanner and ruleset identity
Pattern bundle: v0.7.3
Bundle manifest: sha256:0405f6ffe21e567adf5d6a732d181c7f228194920456d046b4338baeb14de1a8
Risk catalog: sha256:7ff79a126ad99bba2505fec8b2b7711c03f50eb362141128ec1c83e27a5036ba
| Configuration | Advisory result | Exact input | Checked | Evidence |
|---|---|---|---|---|
existing-secret | 1 advisory finding 1 warning Helm-managed StatefulSet may orphan PVCs on release lifecycle operations | 6 objectssha256:8bc3e1bd155bd7dcd6b1734ae00fe481e887ae3a822943da892123ef25439bb1 | 2026-09-16 | Full cub check resultExact YAML Separate Catalog review |
static-passwords | 1 advisory finding 1 warning Helm-managed StatefulSet may orphan PVCs on release lifecycle operations | 7 objectssha256:a1d68c8d814f8612bd3a796d032e4f0747e5f85d96a9f764a76410937b384e2f | 2026-09-16 | Full cub check resultExact YAML Separate Catalog review |
What this does not check: hook execution, CRD readiness, target Secrets and cloud services, admission behavior, workload health, or rollback. The linked Catalog review covers chart-specific source and operating questions. ConfigHub validation and approval are separate managed controls.
Read all shared check results and the mapping to Catalog rules.
What This Chart Contains
Shipping a chart as plain rendered YAML is faster and simpler, and it silently drops anything Helm was going to do afterwards. This section reports what a scan of the packaged chart found, across 65 files.
| Construct | Found | Why it matters when a chart ships as plain YAML |
|---|---|---|
| Keep policy | 1 | A reconciler prunes what Helm promised to keep. |
| Cluster lookups | 3 | The chart reads the cluster while rendering, so a render without one is valid but wrong. |
| Capability branching | 5 | The chart chooses apiVersions from the cluster it renders against. |
| Generated credentials | 10 | Every render mints new values, and a shared artifact would freeze one draw. |
A flattening-safety verdict has decided this version: existing-secret:unsafe-to-flatten; static-passwords:unsafe-to-flatten. The verdict records one disposition per construct and names any companion artifact a flattened bundle must ship. What the flattening verdict means.
A construct being present does not make a chart unflattenable. Most are switched on or off by values, and a verdict records which ones the base you choose actually reaches. Read the catalog-wide evidence for how common each one is.
Images This Chart Pulls
Every reference below is read from the committed package bases, so what you see is what the packaged manifests name.
| Packaged base | Image references |
|---|---|
| static-passwords | registry-1.docker.io/bitnami/postgresql@sha256:2d3c068e58f89e0e29c6d41ffa3d00ff253e87a9426662c3ef11d2a0942ee653 |
| existing-secret | registry-1.docker.io/bitnami/postgresql@sha256:2d3c068e58f89e0e29c6d41ffa3d00ff253e87a9426662c3ef11d2a0942ee653 |
What Has Been Tested
Choose the question you care about. Not checked means this catalog has no version-specific result; it is not a pass.
| Question | Status | Evidence |
|---|---|---|
| Can I pull these exact package bytes again? | Checked | Package receipt |
| What does this chart contain? | Not checked | No linked result |
| Does the recorded render match Helm? | Not checked | No linked result |
| Did the supplied values change the render? | Not checked | No linked result |
| Were hooks, CRDs, or setup steps checked? | Not checked | No linked result |
| Did this version run on a local Kubernetes cluster? | Not checked | No linked result |
| Did an OCI delivery through GitOps run? | Not checked | No linked result |
| Did Helm and ConfigHub reach the same live result? | Not checked | No linked result |
| Was the result compared on separate clusters? | Not checked | No linked result |
| Was a ConfigHub promotion tested? | Not checked | No linked result |
| Did this version string point at changed upstream bytes? | Not checked | No linked result |
The committed publication receipt binds this package path and OCI ref to layer sha256:30ac053e6c9b76656926b6af3659f9d8057c3686d5f77af05f540a4f981ce5f9 and manifest sha256:cf2cfeae128c4ede5cfa9ac65bdf241b557d59a1badacdd107e044caadb0d353, and records an inspect-result digest.
You can check a pull yourself: the inspect command under Try This Chart prints the package's manifest and layer digests, and they must equal the receipted values above. If they differ, do not use the pulled package.
No version-specific runtime result is claimed here. The component row's readiness, caveats, and live evidence describe only its bold version. For that separate evidence, open the 18.6.7 evidence page.
What You Must Provide
The installer metadata records 1 external-requirement reference across these configurations. Inspect the package before choosing a base.
Choose a namespace and target deliberately, supply any listed Secret, CRD, storage, API, or cloud prerequisite, and inspect the rendered YAML before delivery.
Before Production
Run target-specific policy, lifecycle, upgrade, and workload checks. A successful package publication and inspect result does not establish production support or live convergence.
Source And Evidence Files
| Record | Open |
|---|---|
| Retained package source | packages/bitnami/postgresql/18.7.0 |
| Machine-readable listing (static-passwords) | site/listings/bitnami-postgresql-18-7-0-static-passwords.json |
| Machine-readable listing (existing-secret) | site/listings/bitnami-postgresql-18-7-0-existing-secret.json |
| Installer metadata | packages/bitnami/postgresql/18.7.0/installer.yaml |
| Publication receipt | runs/installer-oci/bitnami-postgresql/18.7.0/installer-package-publication-receipt.yaml |
| Publisher signature | runs/installer-oci-signatures/bitnami-postgresql/18.7.0/signature-receipt.yaml |
| Sigstore bundle | runs/installer-oci-signatures/bitnami-postgresql/18.7.0/signature.sigstore.json |
| Version tag | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-postgresql:18.7.0 |
| Exact OCI ref | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-postgresql:18.7.0@sha256:cf2cfeae128c4ede5cfa9ac65bdf241b557d59a1badacdd107e044caadb0d353 |
| Layer digest | sha256:30ac053e6c9b76656926b6af3659f9d8057c3686d5f77af05f540a4f981ce5f9 |
| Manifest digest | sha256:cf2cfeae128c4ede5cfa9ac65bdf241b557d59a1badacdd107e044caadb0d353 |
Technical notes and disclaimers
- The Catalog publishes no plain objects for this entry, because its verdict is unsafe-to-flatten. It has no plain-objects test.