Generated at: 2026-07-30T12:38:02.000Z UTC · source: committed helm-expt evidence for this known gaps page.
The Rule
If a path is awkward, incomplete, target-specific, or unsafe by default, the site marks it watch, blocked, refused, or n/a with a reason. That is more useful than a green-looking demo that hides the hard part.
This is how the catalog helps operations work: it turns uncertainty into a next action instead of asking users to trust a slogan.
Positive framing is allowed. Overclaiming is not. The evidence link is part of the product.
Current Watch Findings
| Finding | Status | Why it matters | Evidence |
|---|---|---|---|
| Fixed placeholder credentials | watch | Repeatable demo credentials are useful for deterministic renders, but a base must not look like it generated a production secret when it ships a fixed placeholder. | ../data/default-credential-check/summary.md |
| cub-direct no prune | watch | Plain apply does not remove objects that disappear from desired state. Argo and Flux can prune; cub-direct needs a prune/delete-set path before clean upgrades are claimed. | ../data/prune-gap-proof/summary.md |
| cub-direct CRD ordering | watch | A first install that contains both CRDs and custom resources needs CRDs established before custom resources are applied, or it needs a controller that handles ordering. | ../data/crd-ordering-gap/summary.md |
| cub-scout drift field coverage | watch | Drift detection is useful only when field coverage is stated. The current receipt catches replica/image-style drift but misses container env-var drift. | ../data/drift-detection-gap/summary.md |
| SSA conflict ergonomics | watch | Server-side apply can protect a manual live edit by reporting a conflict where Helm would silently overwrite, but the product still needs a plain keep-live / accept-desired / force-with-receipt choice. | ../data/ssa-conflict-gap/summary.md |
| Helm-to-cub migration friction | watch | cub rejects normal Helm idioms safely today, but many errors are still too opaque for a Helm-fluent user. The migration guide is the current bridge. | ../data/helm-habit-friction/summary.md |
What A User Should Do
Use the chart page first. If a row is watch or blocked, follow its reason and evidence link. Use FAQ for the short answer, Broken Chart Triage for debugging, and the generated evidence when you need exact receipts.