This page makes the artifact chain explicit:
chart -> recipe -> variants -> variant revisions -> package bases -> receiptsStatus
| Field | Value |
|---|---|
| Chart | bitnami/redis@27.0.0 |
| Catalog status | catalog-candidate |
| Support level | promotion-review-needed |
| Supported scopes | none |
| Production readiness | not-reviewed-for-production |
| Supported variants | none |
| Candidate variants | default, reuse-existing-secret |
| Control points | capability-profile, dependency-lock, generated-facts, hook-policy, image-digest, installer-support-object, secret-handling, source-lock, target-facts |
Feature And Proof Summary
This is the chart-level summary. Use the variant table and receipt links below for exact base-variant evidence.
| Field | Value |
|---|---|
| Adoption bucket | - |
| User status | - |
| Strongest evidence | - |
| Proof lanes | render parity 2/2; ConfigHub 2/2; local live 2/2; GitOps live 2/2; live parity 2/2 |
| Feature summary | none-recorded |
| Hard gap | - |
| Next action | - |
Artifact Chain
| Stage | Artifact |
|---|---|
| Source chart lock | recipes/bitnami/redis/27.0.0/source-lock.yaml |
| Dependency lock | recipes/bitnami/redis/27.0.0/dependency-lock.yaml |
| Recipe | recipes/bitnami/redis/27.0.0/recipe.yaml |
| Helm plan | recipes/bitnami/redis/27.0.0/helm-plan.yaml |
| Chart dossier | recipes/bitnami/redis/27.0.0/chart-dossier.yaml |
| Control points | recipes/bitnami/redis/27.0.0/control-points.yaml |
| Value model | recipes/bitnami/redis/27.0.0/value-model.yaml |
| Value source map | recipes/bitnami/redis/27.0.0/value-source-map.yaml |
| Catalog status | recipes/bitnami/redis/27.0.0/catalog-status.yaml |
| Helm pain report | recipes/bitnami/redis/27.0.0/helm-pain-report.yaml |
| Installer package OCI | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-redis:27.0.0 |
| Installer package source | packages/bitnami/redis/27.0.0 |
| Installer package receipt | recipes/bitnami/redis/27.0.0/publication/installer-package-receipt.yaml |
| Machine index | recipes/bitnami/redis/27.0.0/artifact-index.yaml |
Variants
| Variant | Variant file | Package base | Revision | Helm objects | cub installer objects | Match | Helm equivalence | Scan | Gate | Target facts |
|---|---|---|---|---|---|---|---|---|---|---|
| default | recipes/bitnami/redis/27.0.0/variants/default/variant.yaml | packages/bitnami/redis/27.0.0/bases/default | recipes/bitnami/redis/27.0.0/revisions/default/r001/variant-revision.yaml | 14 | 15 | 14/14 | pass | warn | warn | none |
| reuse-existing-secret | recipes/bitnami/redis/27.0.0/variants/reuse-existing-secret/variant.yaml | packages/bitnami/redis/27.0.0/bases/reuse-existing-secret | recipes/bitnami/redis/27.0.0/revisions/reuse-existing-secret/r001/variant-revision.yaml | 13 | 14 | 13/13 | pass | warn | warn | required Secret redis/redis-existing-secret keys redis-password |
Package Bases
| Base | Path | Default | Description |
|---|---|---|---|
| default | packages/bitnami/redis/27.0.0/bases/default | no | Redis static password demo variant rendered from bitnami/redis@27.0.0 |
| reuse-existing-secret | packages/bitnami/redis/27.0.0/bases/reuse-existing-secret | yes | Redis existing Secret default variant rendered from bitnami/redis@27.0.0 |
Receipts
Current Install Shape
New to cub? Install the cub CLI first. You can pull and render public catalog packages without an account. Commands that save or change ConfigHub data require you to sign in.
What this command does. cub installer is a released, open-source plugin for the cub CLI. cub installer setup pulls a catalog package and writes its Kubernetes files locally. It does not apply those files to a cluster; use kubectl, Argo CD, or Flux for delivery. The generated scripts stop before doing any work when the plugin or kustomize is missing.
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-redis:27.0.0 --base <variant> --work-dir <tmp> --non-interactive --namespace <namespace>Use the variant table above to choose the package base. The oci:// ref is the public package users pull; the packages/... path is the repo source path used by maintainers and proof scripts. The proof path compares regular Helm output with real cub installer setup output and explains every intentional difference, such as the Namespace support object or separated Secrets.