Variant Backlog - what each chart still needs

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.

Derived from each chart's real control-points.yaml using the per-chart-recipes.md method: a standard variant is recommended only where a detected behavior calls for it (no padding), minus the variants the chart already ships. This scopes the wave-based variant build; it does not author the variants (those are bespoke per chart - see data/catalog-promotion-wave2/variant-work-orders.yaml for the worked shape).

Headline

charts: 107
charts needing variant work: 65
charts already variant-complete: 42
total variants to build: 78

Build volume by dimension (highest-leverage first)

Per-chart backlog (charts needing work)

ChartHasBuild next
aqua/trivy-operator@0.32.12existing-secret
argo-cd/argo-cd@9.5.152existing-secret, ha
argo-cd/argo-cd@9.5.172existing-secret, ha
argo-cd/argocd-image-updater@1.2.21existing-secret, no-crds
autoscaler/vertical-pod-autoscaler@0.9.02existing-secret
bitnami/apache@11.4.291existing-secret
bitnami/contour@21.1.42existing-secret
bitnami/elasticsearch@22.1.62existing-secret
bitnami/memcached@8.5.51existing-secret
bitnami/mysql@14.0.32ha
bitnami/nginx@24.0.22existing-secret
bitnami/nginx@24.0.42existing-secret
bitnami/opensearch@2.0.102existing-secret
bitnami/phpmyadmin@20.0.01existing-secret
bitnami/postgresql@18.6.102ha
bitnami/postgresql@18.6.72ha
bitnami/rabbitmq@16.0.142ha
bitnami/spark@10.0.32existing-secret
bitnami/zookeeper@13.8.72existing-secret
cloudnative-pg/cloudnative-pg@0.28.22existing-secret
coredns/coredns@1.45.21existing-secret
crossplane-stable/crossplane@2.3.11existing-secret
dex/dex@0.24.01existing-secret
elastic/eck-operator@3.4.03existing-secret
external-dns/external-dns@1.21.13existing-secret
external-secrets/external-secrets@2.5.02existing-secret
fairwinds-stable/goldilocks@10.3.01existing-secret
falcosecurity/falco@9.0.01existing-secret
falcosecurity/falcosidekick@0.13.11existing-secret
gatekeeper/gatekeeper@3.22.22existing-secret
gitlab/gitlab-runner@0.89.01existing-secret
grafana/promtail@6.17.11existing-secret
grafana/pyroscope@2.0.23existing-secret
grafana/tempo@1.24.42no-crds, ha, ingress-tls
haproxytech/kubernetes-ingress@1.52.01existing-secret
hashicorp/consul@2.0.02no-crds, ha, ingress-tls
hashicorp/vault@0.32.03ingress-tls, tls
istio/istiod@1.30.01existing-secret
jaegertracing/jaeger@4.8.01existing-secret
jetstack/trust-manager@v0.22.12existing-secret
kyverno/kyverno@3.8.12existing-secret
linkerd/linkerd-crds@1.8.01existing-secret, no-crds
longhorn/longhorn@1.11.22no-crds, ha
metrics-server/metrics-server@3.13.02existing-secret
minio-operator/operator@7.1.11no-crds
minio-operator/tenant@7.1.11existing-secret
nats/nack@0.34.02existing-secret
nats/nats@2.14.02existing-secret
open-telemetry/opentelemetry-operator@0.114.02existing-secret
prometheus-community/kube-prometheus-stack@85.3.32existing-secret
prometheus-community/kube-prometheus-stack@86.1.02existing-secret
prometheus-community/kube-state-metrics@7.4.01existing-secret
prometheus-community/prometheus-node-exporter@4.55.01existing-secret
prometheus-community/prometheus-operator-crds@29.0.01existing-secret, no-crds
prometheus-community/prometheus@29.8.02ha
prometheus-community/prometheus@29.9.02ha
rook-release/rook-ceph-cluster@v1.19.51existing-secret
rook-release/rook-ceph@v1.19.51no-crds
runix/pgadmin4@1.62.01existing-secret, ha
sealed-secrets/sealed-secrets@2.18.62existing-secret
secrets-store-csi-driver/secrets-store-csi-driver@1.6.02no-crds
traefik/traefik@40.2.02existing-secret
velero/velero@12.0.12existing-secret
vm/victoria-logs-single@0.12.51existing-secret, ha
vm/victoria-metrics-single@0.39.01ha

How to use this

  1. Take a wave of charts from the top of the build-volume dimensions (existing-secret, ha are broadest).
  2. For each, author the variant like the wave-2 work orders (real values delta that changes the object set), render it, prove Helm-equivalence, write the revision + scan/gate receipts, and declare its scope.
  3. Re-run npm run completeness:generate - the chart flips to variant_complete and, once it has a pain report + scope, to model-complete.