Outcome Coverage

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 report joins the main proof surfaces into one reader-facing map: what outcomes the project claims, which tests prove them, and where to inspect the status per chart, base variant, derived variant, and Helm feature.

Aggregate Status

charts with model support:           108/110
variant-rich charts:                 77/110
chart/base rows:                     199
complete core lane rows:             126/199
render parity rows:                  199/199
in-ConfigHub proof rows:             198/199
local live rows:                     148/199
GitOps/OCI live pass rows:           139/199
GitOps/OCI non-pass receipts:        60
live Helm-vs-ConfigHub pass rows:    139/199
live Helm-vs-ConfigHub non-pass receipts: 60
lifecycle observation rows:          20/20
selected live parity receipts:       139 pass, 52 watch, 8 blocked
two-cluster kind parity receipts:    130 pass, 3 watch, 46 blocked
derived intended-state pass rows:    10
target-bound derived pass rows:      5
target-bound derived blocked rows:   1
maintained hook queue rows:          5
hook route receipts present:         5/5
hook lifecycle observations present: 5/5
hook partial lifecycle observations: 0/5
hook routes awaiting observation:    0/5
hook rows still needing route:       0/5
related lifecycle observations:      20/20

Outcome Promises And Proving Tests

Outcome users care aboutTest / evidenceCommand
The chart model is understandable and honestly scoped.model-completeness report, chart facts, pain reports, weirdness notesnpm run completeness:verify
A base variant renders the same object set as Helm under recorded inputs.render_parity in base-outcomes.csvnpm run outcomes:verify
The rendered objects can be uploaded and operated in ConfigHub.confighub_upload_variant_scan_safe_ops lanenpm run top20:verify-confighub-proof
The rendered objects work in Kubernetes for tested rows.local_kind_kubectl_apply lanenpm run top20:verify-local-e2e
A chart with CRDs, webhooks, or controller-owned fields works after its recorded lifecycle route or prerequisites are applied.lifecycle_observation in base-outcomes.csvnpm run lifecycle:cert-manager-eso:verify; npm run lifecycle:boundary:verify
ConfigHub OCI can be reconciled by GitOps for tested rows.confighub_oci_argo_live lanenpm run runtime-gitops:wave:verify
Plain Helm and ConfigHub delivery reach equivalent live outcomes for tested rows.live_helm_vs_confighub_dual_compare, two-cluster parity receiptsnpm run live-parity:verify && npm run kind-parity:verify
Derived ConfigHub variants preserve reviewed bases and expose post-render changes.derived variant execution and target-bound receiptsnpm run derived-variants:verify && npm run derived-variants:target-bound:verify
Hooks and hook-like lifecycle behavior are not hidden in render proof.hook route receipts, hook lifecycle queue, and lifecycle observationsnpm run hooks:lifecycle:verify && npm run lifecycle:boundary:verify && npm run lifecycle:cert-manager-eso:verify
Images, Secrets, CRDs, webhooks, target facts, and other chart-specific features are visible.chart facts, attack-plan workdown, image-digest workdownnpm run chart-facts:verify && npm run attack-plan:verify && npm run image-digests:workdown:verify

Files

FileWhat it shows
chart-outcomes.csvOne row per chart: model support, production readiness, variant count, lane counts, feature summary, hard gaps.
base-outcomes.csvOne row per chart/base variant: render parity, in-ConfigHub proof, local live, lifecycle observation, GitOps/OCI live, live parity, and two-cluster kind parity.
derived-variant-outcomes.csvOne row per executed derived ConfigHub variant: intended-state proof and target-bound live status.
feature-outcomes.csvOne row per chart/feature: hooks, generated secrets, CRDs, webhooks, required values, schemas, extension slots, gaps.

Catalog-Supported Chart Snapshot

ChartVariantsModelIn-ConfigHubLocal liveLifecycleGitOps liveLive parityTwo-cluster parityHard gap
argo-cd/argo-cd@9.5.15default;no-crdsyes2/21/20/22/22/21/2ha (curated proof lane - bespoke teaching needed)
bitnami/mongodb@19.0.7static-passwords;existing-secret-replicasetyes2/22/20/22/22/20/2-
bitnami/mysql@14.0.3static-passwords;existing-secretyes2/22/20/22/22/22/2ha (curated proof lane - bespoke teaching needed)
bitnami/nginx@24.0.2http-clusterip;existing-tls-ingressyes2/22/20/22/22/20/2existing-secret (chart ships no Secret toggle)
bitnami/postgresql@18.6.7static-passwords;existing-secretyes2/22/20/22/22/20/2ha (curated proof lane - bespoke teaching needed)
bitnami/rabbitmq@16.0.14static-passwords;existing-secretyes2/22/20/22/22/22/2ha (curated proof lane - bespoke teaching needed)
bitnami/redis@25.5.3default;reuse-existing-secretyes2/22/20/22/22/20/2-
external-secrets/external-secrets@2.5.0default;no-crdsno2/22/22/22/22/22/2-
grafana/grafana@10.5.15static-passwords;existing-secret-ingressyes2/22/20/22/22/22/2-
grafana/loki@7.0.0single-binary-filesystem;simple-scalable-minioyes2/22/20/22/22/22/2-
grafana/tempo@1.24.4local-persistent;s3-query-observabilityyes2/21/20/21/21/22/2ha (tempo single-binary chart; HA is the separate tempo-distributed chart)
hashicorp/consul@2.0.0default-control-plane;secure-mesh-existing-secretsyes2/21/20/21/21/22/2ha (curated proof lane - bespoke teaching needed)
hashicorp/vault@0.32.0dev-mode;default;ha-raft-uiyes3/32/30/32/32/33/3-
ingress-nginx/ingress-nginx@4.15.1default;admission-disabled;internal-clusteripyes3/33/31/33/33/33/3-
jetstack/cert-manager@v1.20.2default;crds-enabledno2/22/22/22/22/22/2-
longhorn/longhorn@1.11.2default;ui-ingressyes2/22/20/22/22/22/2-
metrics-server/metrics-server@3.13.0default;external-tls-cayes2/22/20/22/22/22/2existing-secret (chart ships no Secret toggle)
prometheus-community/kube-prometheus-stack@85.3.3default;no-crdsyes2/22/22/22/22/20/2existing-secret (chart ships no Secret toggle)
prometheus-community/prometheus@29.8.0default;server-only-ephemeralyes2/22/20/22/22/20/2ha (curated proof lane - bespoke teaching needed)
secrets-store-csi-driver/secrets-store-csi-driver@1.6.0default;sync-secret-rotationyes2/22/20/22/22/22/2-

How To Read This

pass means a committed receipt exists and the verifier checks it. missing means the lane has not been proven for that exact chart/base row. fail, watch, or blocked means the repo has evidence that the row did not pass as-is on the tested target.

Use the narrowest true claim: model-supported, render parity, in-ConfigHub, local live, two-cluster kind parity, GitOps live, live parity, hook route selected, lifecycle observed, or production-ready.