hashicorp/vault
Runs on your laptop
Choose a tested starting configuration for hashicorp/vault@0.32.0. Read its exact Kubernetes objects, required setup, and current evidence before you deploy it.
Start with default. The page also shows other recorded choices. The page does not claim every possible values combination.
Evidence labels: Pass has a linked result. Watch names a limit to check. Blocked means do not use that path yet.
Upstream: find this chart on Artifact Hub · Helm documentation. This page adds checked configurations and test results.
Catalog readiness: Ready to try.
Licenses: chart MPL-2.0 (the chart's own Chart.yaml license metadata, read 2026-08-08). One source states it differently; the committed record keeps both statements. This describes the chart templates, not the packaged application images.
Check this chart and version Try the package Plan an upgrade or promotion
Already reviewed the result? Keep it in ConfigHub when you need history, variants, approvals, or delivery.
What this page gives you
Every chart page follows the same order. Choose a configuration, inspect its objects and setup work, then read the tests that have run. Open the worked examples.
The package fixes and checks almost everything at build time. What you set is small and typed.
Open the saved results for the Helm comparison, live install, and delivery checks.
The page names the work and says which delivery path has actually run.
What To Use
default configuration: 12 rendered objects · 2 images · 0 target prerequisites · 0 hook or setup routes · 6/6 checks passing. These counts come from the linked test records.
defaultRecommended first base variant
3Supported base variants
Recommended first pathFirst-configuration status
Ready for a target-specific production reviewProduction status
Use the public catalog entry, then check the exact configuration and its tests before making a production claim.
| Question | Answer |
|---|
| Catalog readiness | Ready to try |
| Chart version | 0.32.0 |
| Exact installer package | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292 |
| OCI publication status | publication receipt recorded |
| Publisher signature | publisher signature recorded and verified |
| Latest upstream seen | 0.32.0 |
| Supported base variants | dev-mode;default;ha-raft-ui |
| Not yet available | No specific missing capability is recorded. The first configuration still needs review. |
| Namespace | vault |
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? | No destination answer is available yet because target facts or lifecycle handling are incomplete. | Destination access: yes
Selected configuration deployed: no | Answer pending
evidence pending |
| 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.
Where This Chart's Settings Come From
| Base variant | Helm values | ConfigHub changes | Install work |
|---|
| default | effective-values.yaml | None in the catalog base. Later edits appear in ConfigHub Unit revision history or a derived variant. | No separate work is recorded; read the prerequisite and lifecycle status before assuming none is needed. |
| dev-mode | effective-values-dev-mode.yaml | None in the catalog base. Later edits appear in ConfigHub Unit revision history or a derived variant. | No separate work is recorded; read the prerequisite and lifecycle status before assuming none is needed. |
| ha-raft-ui | effective-values-ha-raft-ui.yaml | None in the catalog base. Later edits appear in ConfigHub Unit revision history or a derived variant. | 1 prerequisite recorded. |
Upgrade rule: if a new Helm render and a ConfigHub revision both change the same field, review the overlap before promotion. The values profile shows the Helm side; Unit revision history shows the ConfigHub side.
Read the full values-versus-ConfigHub rule. For the staging commands behind each prerequisite, open the prerequisite action packets.
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 49 files.
| Construct | Found | Why it matters when a chart ships as plain YAML |
|---|
| Helm hooks | 1 | Hook Jobs never fire, or fire under a different hook dialect. |
| Webhook configuration | 1 | An empty certificate bundle makes admission fail closed. |
| Capability branching | 10 | The chart chooses apiVersions from the cluster it renders against. |
| Test hooks | 1 | Test resources would ship to a cluster that never asked for them. |
A flattening-safety verdict has decided this version: default:safe-to-flatten; dev-mode:flatten-with-routes; ha-raft-ui:flatten-with-routes. The verdict records one disposition per construct and names any companion artifact a flattened bundle must ship.
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.
What The Starting Configuration Records
A base variant is a starting configuration we have already rendered and checked. Pick the one whose trade-off you want; the table below shows what each one changes. How the values for each are chosen.
The default base-variant record connects those Helm inputs to the Kubernetes objects, remaining requirements, hooks, CRDs, checks, and OCI status. Open it when you need the complete starting record rather than only the rendered YAML.
Open the full rendered YAML to read the actual manifest output. The render record and setup section explain the inputs, tests, CRDs, hooks, and other work around it.
If new Helm values create a useful starting configuration, record another base variant with its own inputs and checks. If one environment changes a field after rendering, record that change in a ConfigHub variant.
| Key | Where to look first | What it means |
|---|
| Package users pull | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292 | The exact installer package for this chart version. The version tag is readable, and the manifest digest makes a published pull immutable. Public catalog package refs are published in Google Artifact Registry with anonymous read access. No ConfigHub account or Google registry login is needed for the local setup path. |
| Required before apply | None recorded for the recommended base variant.
No separate setup command recorded. | External resources the recommended base variant expects, such as an existing Secret, namespace, CRD, or target fact. |
| Kubernetes objects | full rendered YAML | The full YAML captured from this base variant. It is the output of the render. |
| Render record | default render intent | The Helm inputs and evidence links that explain how the output was produced. |
| Complete starting record | default base-variant record | The record that connects the Helm inputs, Kubernetes objects, remaining requirements, setup work, checks, and OCI status. |
| Hooks, CRDs, and setup work | this page's setup section | Instructions and decisions for hooks, CRDs, generated Secrets, setup jobs, cluster requirements, or blockers. |
Choose base variant
Pick the supported Helm configuration for this chart: default, no-CRDs, existing Secret, HA, server-only, or another listed option.
Record inputs
Keep the values, namespace, release name, source lock, default render intent, full YAML output, package base, test results, and setup instructions together.
Handle chart extras
CRDs, hooks, setup jobs, external Secrets, target facts, and webhook certificates are recorded as chart-specific choices. Some are included in a base variant, some need a setup step, and some are blocked until there is a safe path.
How render intents work · All generated render intents · All base variant records
Try This Chart
Start with default. If a card says review or preparation is needed, treat that as a real limit rather than a ready install.
Package image
Exact package: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292
publication receipt recorded · open the exact publication receipt
Readable version tag: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0. The package is pinned so a republished tag cannot change what you get. The command below uses the exact manifest digest, so cub installer refuses different package bytes.
Check the package identity
New to cub? Install the cub CLI first. Public catalog packages pull and render anonymously, and you sign in only once a command saves or changes ConfigHub data.
cub installer inspect oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292 --json
Read how each configuration was made
cub installer pull 'oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292' --work-dir ./package-review
less ./package-review/package/records/README.md
The package's records/ directory connects every base to its source choices, Helm render intent, Kubernetes objects, prerequisites, lifecycle work, and checks. These are supporting records, not Kubernetes objects.
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/hashicorp/vault/0.32.0 --annotations confighub.com/package-sha256=add21acd201b5c747711f91fdabe3d66bc712cd563f2c279961a5c47b3b91c09 europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292
A 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
Public catalog package refs are published in Google Artifact Registry with anonymous read access. No ConfigHub account or Google registry login is needed for the local setup path.
Recommended first command
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292 --base default --work-dir ./hashicorp-vault-0-32-0-default --non-interactive --namespace vault
Advanced: apply it or upload it
Run the whole sequence as one script, prerequisites included: try.sh renders and applies to Kubernetes without an account; confighub.sh renders and uploads to your ConfigHub Space.
Before you run try.sh: it changes your current kubectl context. It runs the named prerequisites and applies the rendered objects. Read it first and use a disposable test cluster. confighub.sh does not apply anything to Kubernetes.
This preset is also shown in the live helm-catalog demo org. Read the demo README to see why that Space exists, what problem it demonstrates, and what to inspect first.
You should see something like this
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 setup ...
rendered manifests written under <work-dir>
use the chart option cards below to check pass, watch, blocked, and prerequisites
Current status: Available in the catalog · Reason: Promotion was tested and recorded in ConfigHub.
After You Render It
The first command writes files and does not apply them. Read the objects and setup requirements, then choose the next job.
| Job | Next step |
|---|
| Render and inspect without applying | Run the recommended cub installer setup command above. |
| Run shared local configuration checks | cub plugin install confighub/homebrew-tap@cub-scan-v0.7.3 --name scan
cub check --format json --output cub-check.json <work-dir>/out/manifests. The check is advisory and does not apply anything. |
| Apply the rendered manifests with kubectl, or publish reviewed objects as OCI | Publish reviewed objects as OCI or apply the manifests with kubectl. |
| Save the reviewed result for a team | Save and upload the reviewed result to ConfigHub for shared history, exact diffs, and approvals. |
| Compare development and production, audit an exact diff, promote, or roll back | Build a promotion review or read the bounded rollback example. |
| Assign the configuration to clusters and operate a small fleet | Choose targets, preview a wave, and inspect every result. |
| Check delivery limits | Read the current limits before choosing kubectl, Argo CD, or Flux. |
| Handle CRDs on the first install | Read the CRD ordering risk and first-install guide, then check this chart's recorded owner and route. |
Available Configurations
Each card is one available way to use this chart in the catalog. Some cards are runnable base variants. Others are candidate paths, derived variants, or review notes that explain what still has to be prepared.
Checks: Each card names what was checked and says whether it passed, needs review, was blocked, was not run, or was not needed.
7 matrix rows for hashicorp/vault@0.32.0 · open the full matrix
F1 · Source chart
(source)
Source
Pinned upstream chart and version
- Status
- Available in the catalog
- How to run
- This is the upstream chart source. Choose a base card below before running the installer.
- Evidence
- Pinned chart source and dependency lock
- Hooks/actions
- No separate hook or action for this row.
- Who runs actions?
- No separate action runner for this row.
- Next
- Choose a chart configuration before rendering or deploying
- Reason
- This is the chart source. Choose a configuration before checking deployment or promotion
Helm outputNot neededSaved in ConfigHubNot neededLocal clusterNot neededSetup routeNot neededGitOps and OCINot neededLive Helm comparisonNot neededTwo clustersNot neededPromotionNot needed
catalog · source repo
F2a · Chart default
default
Base
Runnable base variant made from the chart defaults
- Status
- Available in the catalog
- Helm values
- effective-values.yaml
- ConfigHub changes
- None in this catalog base. After upload, read Unit revision history or the derived variant.
- How to run
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292 --base default --work-dir ./hashicorp-vault-0-32-0-default --non-interactive --namespace vault- Scripts
- try.sh renders, settles the prerequisites in order, and applies with kubectl; confighub.sh renders and uploads to your ConfigHub Space.
- Evidence
- Live helm vs confighub parity
- Hooks/actions
- No separate hook or action for this row.
- Who runs actions?
- No separate action runner for this row.
- Lifecycle record
- The current review found no separate hook or setup route for this base. Open the full record.
- Prerequisites
- This base has not yet been reviewed for required Secrets, CRDs, namespaces, values, storage services, external APIs, or target topology. Record what it needs, or record that nothing extra is required.
- Next
- Resolve image digests for each affected variant before production OCI support
- Reason
- Promotion was tested and recorded in ConfigHub.
Helm outputPassedSaved in ConfigHubPassedLocal clusterPassedSetup routeNot runGitOps and OCIPassedLive Helm comparisonPassedTwo clustersPassedPromotionPassed
Demo README · catalog · variant · full YAML · render intent · base record · package base · receipt · source repo
F2b · Helm-rendered base
dev-mode
Base
Runnable base variant made with different Helm values
- Status
- Available in the catalog
- Helm values
- effective-values-dev-mode.yaml
- ConfigHub changes
- None in this catalog base. After upload, read Unit revision history or the derived variant.
- How to run
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292 --base dev-mode --work-dir ./hashicorp-vault-0-32-0-dev-mode --non-interactive --namespace vault- Scripts
- try.sh renders, settles the prerequisites in order, and applies with kubectl; confighub.sh renders and uploads to your ConfigHub Space.
- Evidence
- Live helm vs confighub parity
- Hooks/actions
- No separate hook or action for this row.
- Who runs actions?
- No separate action runner for this row.
- Lifecycle record
- The current review found no separate hook or setup route for this base. Open the full record.
- Prerequisites
- This base has not yet been reviewed for required Secrets, CRDs, namespaces, values, storage services, external APIs, or target topology. Record what it needs, or record that nothing extra is required.
- Next
- Resolve image digests for each affected variant before production OCI support
- Reason
- Promotion was tested and recorded in ConfigHub.
Helm outputPassedSaved in ConfigHubPassedLocal clusterPassedSetup routeNot runGitOps and OCIPassedLive Helm comparisonPassedTwo clustersPassedPromotionPassed
Demo README · catalog · variant · full YAML · render intent · base record · package base · receipt · source repo
F2b · Helm-rendered base
ha-raft-ui
Base
Runnable base variant made with different Helm values
- Status
- Available in the catalog
- Helm values
- effective-values-ha-raft-ui.yaml
- ConfigHub changes
- None in this catalog base. After upload, read Unit revision history or the derived variant.
- How to run
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292 --base ha-raft-ui --work-dir ./hashicorp-vault-0-32-0-ha-raft-ui --non-interactive --namespace vault- Scripts
- try.sh renders, settles the prerequisites in order, and applies with kubectl; confighub.sh renders and uploads to your ConfigHub Space.
- Evidence
- Live helm vs confighub parity
- Hooks/actions
- No separate hook or action for this row.
- Who runs actions?
- No separate action runner for this row.
- Lifecycle record
- The current review found no separate hook or setup route for this base. Open the full record.
- Prerequisites
- 1 prerequisite is declared for this base, with 1 follow-up action record from live tests. Each prerequisite says whether it must be checked before render or before apply.
- Next
- Operating policy
- Reason
- Operate policy: Vault init/unseal readiness (parity passed)
Helm outputPassedSaved in ConfigHubPassedLocal clusterBlockedSetup routeNot runGitOps and OCIReviewLive Helm comparisonReviewTwo clustersPassedPromotionPassed
Demo README · catalog · variant · full YAML · render intent · base record · package base · receipt · source repo
F3 · Required setup
ha-raft-ui + review
Candidate
A prerequisite or target value needed before deployment; review needed
- Status
- Candidate path; human review needed
- How to run
- Not ready to run yet. First: An operator decision recorded for this base/target; Then a fresh G/P parity receipt for this base.
- Evidence
- Planning evidence only
- Hooks/actions
- No separate hook or action for this row.
- Who runs actions?
- No separate action runner for this row.
- Next
- Complete the operator review; Npm run live parity:run recipe recipes/hashicorp/vault/0.32.0 base ha raft ui
- Reason
- This is a planned option. Promotion has not been tested for it.
Helm outputNot neededSaved in ConfigHubNot neededLocal clusterNot neededSetup routeNot neededGitOps and OCINot neededLive Helm comparisonNot neededTwo clustersNot neededPromotionNot needed
catalog · receipt · source repo
F4a · ConfigHub variant
regulated-prod-us-east
Variant
ConfigHub variant derived from a catalog base
- Status
- Needs more work before this is a ready path
- How to run
- A ConfigHub variant based on default for Vault-regulated-prod-us-east. Upload the base first, then create or promote this variant in ConfigHub.
- Evidence
- ConfigHub variant clone evidence
- Hooks/actions
- No separate hook or action for this row.
- Who runs actions?
- No separate action runner for this row.
- Next
- Create this as a ConfigHub variant after the base has been uploaded.
- Reason
- No target was attached; This is a ConfigHub intended state proof; Not a live cluster deployment.
Helm outputNot neededSaved in ConfigHubPassedLocal clusterNot neededSetup routeNot neededGitOps and OCINot runLive Helm comparisonNot neededTwo clustersNot neededPromotionNot needed
catalog · variant · full YAML · package base · receipt · source repo
F4a · ConfigHub variant
staging-us-east
Variant
ConfigHub variant derived from a catalog base
- Status
- Needs more work before this is a ready path
- How to run
- A ConfigHub variant based on default for Vault-staging-us-east. Upload the base first, then create or promote this variant in ConfigHub.
- Evidence
- ConfigHub variant clone evidence
- Hooks/actions
- No separate hook or action for this row.
- Who runs actions?
- No separate action runner for this row.
- Next
- Create this as a ConfigHub variant after the base has been uploaded.
- Reason
- No target was attached; This is a ConfigHub intended state proof; Not a live cluster deployment.
Helm outputNot neededSaved in ConfigHubPassedLocal clusterNot neededSetup routeNot neededGitOps and OCINot runLive Helm comparisonNot neededTwo clustersNot neededPromotionNot needed
catalog · variant · full YAML · package base · receipt · source repo
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 |
|---|
default | 10 advisory findings
9 warning, 1 info
Webhook timeout value too high blocks cluster upgrades
Deployment containers omit resource limits
Deployment containers omit resource requests | 12 objects
sha256:3601152857dc31f730544f2191e300feaaf0cfe5ca8e6a48ddad7eb910fe788b | 2026-08-24 | Full cub check result
Exact YAML
Separate Catalog review |
dev-mode | 9 advisory findings
8 warning, 1 info
Webhook timeout value too high blocks cluster upgrades
Deployment containers omit resource limits
Deployment containers omit resource requests | 11 objects
sha256:46605a137a11f53e7b5a799d70b4f61a83f47544efc4f2182da94a3c9a3b45c3 | 2026-08-24 | Full cub check result
Exact YAML
Separate Catalog review |
ha-raft-ui | 12 advisory findings
11 warning, 1 info
Service selector matches no Deployment or StatefulSet in namespace vault
Webhook timeout value too high blocks cluster upgrades
Deployment containers omit resource limits | 18 objects
sha256:38c0f61bbba6125eaf9f60ebc977dcc2fe9f2307d171a49b7f4e93179c7db155 | 2026-08-24 | Full cub check result
Exact 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.
Images This Chart Pulls
Every reference below comes from the reviewed rendered output. What you see is what the cluster pulls. These references are data: you can change a registry or pin a digest with a recorded edit, and prove the change landed in every environment.
| Base variant | Images |
|---|
| default | hashicorp/vault-k8s:1.7.2
hashicorp/vault:1.21.2 |
| dev-mode | hashicorp/vault-k8s:1.7.2
hashicorp/vault:1.21.2 |
| ha-raft-ui | hashicorp/vault-k8s:1.7.2
hashicorp/vault:1.21.2 |
First-Run Caveats
Some chart paths need a small preparation step before the cub path feels as smooth as Helm. We show those steps here so the first run does not surprise you.
| Caveat | What to do |
|---|
| Universal caveats | Use declared inputs or bases instead of Helm --set. For direct delivery, define pruning and field-conflict behavior. Use Argo CD or Flux when that controller path and its pruning settings are recorded for the selected preset. |
| Shared placeholder password | No shared placeholder password caveat recorded for this chart. |
| CRD first-ordering | No CRD first-ordering caveat recorded for this chart. |
Open the all-chart adoption caveats · Helm to cub migration · cub deployment path
Advice And Current Status
Use this section to see which chart-specific guides apply, what you must provide, and what work remains.
| Question | Current answer |
|---|
| User status | Ready to try |
| Can I use it? | Use the public catalog entry, then check the exact configuration and its tests. |
| First base | default |
| Exact installer package | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/hashicorp-vault:0.32.0@sha256:7216f8cbbb3e2dafe3ed987f1e4b6fa962de60b2bf5ba7d2d0b7eb45eb138292 |
| Tests completed | Catalog supported with live evidence (render parity 3/3; Local live 2/3; Live parity 2/3) |
| Coverage | Covered |
| You must provide | a StorageClass / storage decision; webhook/cert readiness at delivery time; mandatory chart inputs |
| What the tools record | exact rendered objects with render parity and receipts; optional chart inputs handled by reviewed base configurations |
| Next action | resolve image digests for each affected variant before production OCI support |
The source data lives in chart skills and chart evidence router.
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.
How much is proven, and what more testing would add: Fully proven: Render parity, ConfigHub proof, Two-cluster kind. Proven on some bases: Local live, GitOps/OCI live, Live Helm-vs-ConfigHub.
| Base | Readiness | Render | ConfigHub | Local live | GitOps/OCI | Live parity | Two-cluster kind |
|---|
| default | start-here | pass | pass | pass | pass | pass | pass |
| dev-mode | start-here | pass | pass | pass | pass | pass | pass |
| ha-raft-ui | runtime-watch | pass | pass | blocked | watch | watch | pass |
What You Must Provide
exact rendered objects with render parity and receipts; optional chart inputs handled by reviewed base configurations
| Field | Value |
|---|
| Known quirks | Webhooks; optional chart inputs; Required values; Tpl; Capabilities; Rbac; Storage |
| You must provide | a StorageClass / storage decision; webhook/cert readiness at delivery time; mandatory chart inputs |
| What ConfigHub records | exact rendered objects with render parity and receipts; optional chart inputs handled by reviewed base configurations |
| Optional chart inputs | Sidecars; Volumes/mounts; Secret/env injection |
| How optional inputs are handled | Keep empty in supported bases; Or make a reviewed installer base when populated |
Hooks, CRDs, And Setup Work
Some Helm charts need work before, during, or after apply: CRDs, hooks, setup jobs, webhook certificates, migrations, generated Secrets, or checks. For each chart, the catalog should make the choice clear: include it in the base variant, split it into a separate base variant, run a setup step, use a GitOps action where evidence exists, require an existing target resource, or block it when there is no safe default.
What each base needs before apply
These requirements come from the same base definition as the rendered objects. The render intent keeps the chart inputs, required Secrets or CRDs, lifecycle routes, and evidence together.
| Base variant | Required resource | How to provide it | Full record |
|---|
| ha-raft-ui | minimum schedulable nodes 3 | use a target with at least 3 schedulable nodes before applying this base | full render intent |
If no route is shown, that does not prove the upstream chart has no hooks. It means the public catalog has no chart-specific action to show yet; check the matrix or send a problem chart if hook behavior should be modeled. Direct apply, Argo CD, Flux, and upgrade implementations are tracked separately. One passing implementation does not prove the others.
Before Production
A green render or local live result is not a production support claim. Production support is target-scoped and uses the support-decision artifact when present.
| Field | Value |
|---|
| Production review status | Ready for a target-specific production review |
| Target-scoped support decision | rejected |
| Supported base | default |
| Target scope | kind-vanilla; namespace=vault; delivery=confighub-oci; controller=argo |
| Accepted limits | cluster RBAC review; optional input sources and scan policy; warning review and apply-gate policy; storage backup, restore, and rollback policy; cluster requirement checks before deployment; webhook readiness and failure policy |
| Open policy decisions | None recorded for this policy checklist |
| Next action | Keep the default base as a ready-to-try parity example. Create a separate TLS-enabled, digest-pinned, persistent-storage base with explicit init, unseal, recovery, backup, and upgrade procedures before reconsidering production support. |
Source And Evidence Files