Top-20 Base Variant Readiness

A repository document, rendered for the site. View source markdown.

Generated at: 2026-07-30T12:38:02.000Z UTC · source: committed helm-expt evidence for this rendered repository document.

This generated table answers the practical catalog question:

For each top-20 chart base variant, can a user start with it now, or does it
need a target prerequisite, runtime review, hook lifecycle route, or more proof?

It is intentionally base-variant level. Chart-level summaries can hide the fact that one base is a clean first path while another base still needs prerequisites or runtime review.

Summary

base variants: 42
start-here: 26
try-with-proof: 0
runtime-watch: 3
runtime-review-needed: 0
operating-policy-needed: 0
target-fit-needed: 0
target-prerequisite-needed: 0
hook-lifecycle-review-needed: 0
lifecycle-observed: 0
prerequisite-observed: 0
render-only: 13

Live rerun readiness for non-pass rows:

ready-to-collect: 0
model-or-stage-first: 1
review-target-first: 2
inspect-diff-first: 0
rerun-now-after-cleanup: 0

How To Read User Readiness

ReadinessMeaning
start-hereBest current demo/catalog path: render parity, ConfigHub proof, local live, GitOps/OCI, selected live parity, and two-cluster parity are all passing.
try-with-proofRender parity and two-cluster parity pass, but one or more broader ConfigHub/live lanes are still missing for this base.
runtime-watchObject parity passed, but the live target did not fully settle during the run.
runtime-review-neededObject parity passed, but runtime state needs investigation before this base is presented as easy.
operating-policy-neededObject parity passed, but the app needs a post-render operating procedure before it can be called ready.
target-fit-neededObject parity passed, but the selected target does not provide the platform shape this base declares.
target-prerequisite-neededThe base expects CRDs, APIs, Secrets, storage, or another target prerequisite to exist or be staged.
hook-lifecycle-review-neededHelm hook or hook-like lifecycle behavior needs an explicit route and receipt.
lifecycle-observedStrict parity remains blocked or watch, but the hook-like lifecycle route has a passing observation receipt.
prerequisite-observedThe base needs an external prerequisite, and a related observation receipt proves the staged-prerequisite path.
render-onlyRender parity exists, but live/user proof lanes are not present for this base.

Rows

ChartBaseFirstReadinessRerun readinessWhyNext actionSupport artifact
argo-cd/argo-cd@9.5.15defaultyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
argo-cd/argo-cd@9.5.15no-crdsnorender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
bitnami/mongodb@19.0.7existing-secret-replicasetyesrender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
bitnami/mongodb@19.0.7static-passwordsnorender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
bitnami/mysql@14.0.3existing-secretyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
bitnami/mysql@14.0.3static-passwordsnostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
bitnami/nginx@24.0.2http-clusteripyesrender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
bitnami/nginx@24.0.2existing-tls-ingressnorender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
bitnami/postgresql@18.6.7existing-secretyesrender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
bitnami/postgresql@18.6.7static-passwordsnorender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
bitnami/rabbitmq@16.0.14existing-secretyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
bitnami/rabbitmq@16.0.14static-passwordsnostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
bitnami/redis@25.5.3reuse-existing-secretyesrender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
bitnami/redis@25.5.3defaultnorender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
external-secrets/external-secrets@2.5.0defaultyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
external-secrets/external-secrets@2.5.0no-crdsnostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
grafana/grafana@10.5.15existing-secret-ingressyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
grafana/grafana@10.5.15static-passwordsnostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
grafana/loki@7.0.0single-binary-filesystemyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
grafana/loki@7.0.0simple-scalable-minionostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
grafana/tempo@1.24.4local-persistentyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
grafana/tempo@1.24.4s3-query-observabilitynoruntime-watchreview-target-firstobject parity passed, but a live GitOps/controller condition needs reviewinspect the live parity receipt before rerunning; decide whether this is target behavior, controller timing, or a support boundary-
hashicorp/consul@2.0.0default-control-planeyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
hashicorp/consul@2.0.0secure-mesh-existing-secretsnoruntime-watchreview-target-firstobject parity passed, but a live GitOps/controller condition needs reviewinspect the live parity receipt before rerunning; decide whether this is target behavior, controller timing, or a support boundary-
hashicorp/vault@0.32.0defaultyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
hashicorp/vault@0.32.0dev-modenostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
hashicorp/vault@0.32.0ha-raft-uinoruntime-watchmodel-or-stage-firstobject parity passed, but a live GitOps/controller condition needs reviewinspect the live parity receipt before rerunning; decide whether this is target behavior, controller timing, or a support boundary-
ingress-nginx/ingress-nginx@4.15.1internal-clusteripyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
ingress-nginx/ingress-nginx@4.15.1admission-disablednostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
ingress-nginx/ingress-nginx@4.15.1defaultnostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
jetstack/cert-manager@v1.20.2crds-enabledyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
jetstack/cert-manager@v1.20.2defaultnostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
longhorn/longhorn@1.11.2defaultyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
longhorn/longhorn@1.11.2ui-ingressnostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
metrics-server/metrics-server@3.13.0defaultyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
metrics-server/metrics-server@3.13.0external-tls-canostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
prometheus-community/kube-prometheus-stack@85.3.3defaultyesrender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
prometheus-community/kube-prometheus-stack@85.3.3no-crdsnorender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
prometheus-community/prometheus@29.8.0server-only-ephemeralyesrender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
prometheus-community/prometheus@29.8.0defaultnorender-only-render parity exists, but two-cluster live parity has no committed receipt for this baserun two-cluster kind parity and then add ConfigHub/live lanes as needed-
secrets-store-csi-driver/secrets-store-csi-driver@1.6.0defaultyesstart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-
secrets-store-csi-driver/secrets-store-csi-driver@1.6.0sync-secret-rotationnostart-here-all core lanes plus two-cluster parity pass for this baseuse as the first catalog path; check production disposition before production use-

Files

FilePurpose
data/top20-base-readiness/base-readiness.csvSpreadsheet-ready one-row-per-base readiness table.
data/top20-base-readiness/start-here.mdShort guide to the clean first catalog paths.
data/outcome-coverage/base-outcomes.csvUnderlying lane data used by this report.
data/live-kind-parity/summary.mdTwo-cluster Helm-vs-installer parity receipts and non-pass reasons.
data/live-parity-rerun-plan/rerun-plan.csvRerun readiness, next step, and exact rerun command for non-pass live rows.
CATALOG.mdTop-level chart and variant catalog.

Rows marked ready-to-collect in the CSV already have render parity and two-cluster parity. Use their live_rerun_command value to collect the missing live Helm-vs-ConfigHub receipt for that specific base.

Regenerate:

npm run top20:base-readiness
npm run top20:base-readiness:verify