How To Use This Page
Start here
Use this page to understand the words in the matrix. It explains what each quirk means, why it matters, and what the user or target must provide.
Then check a chart
Open the Helm Ops Catalog or the matrix to see whether a specific chart and base has that quirk.
Then check the route
For hooks, CRDs, webhooks, target facts, and generated facts, use the row's route, gap, and next-action fields to see what must happen before delivery.
Open Helm Ops Catalog · Open status matrix · Read the reference matrix
Quirk List
| Quirk | What it means | Charts | Rows | Example charts |
|---|---|---|---|---|
| Template evaluation | The chart uses Helm templating inside values or snippets. We preserve the rendered result and keep extension slots visible. | 55 | 157 | aws-ebs-csi-driver/aws-ebs-csi-driver, bitnami/apache, bitnami/contour, bitnami/elasticsearch |
| Kubernetes capabilities | The render depends on Kubernetes API capabilities. The recipe pins a capability profile so the render is repeatable. | 49 | 138 | aws-ebs-csi-driver/aws-ebs-csi-driver, bitnami/apache, bitnami/contour, bitnami/elasticsearch |
| Cluster RBAC | The chart creates cluster-wide permissions. The objects are visible before delivery and can be reviewed or gated. | 41 | 119 | aws-ebs-csi-driver/aws-ebs-csi-driver, bitnami/contour, bitnami/mongodb, cloudnative-pg/cloudnative-pg |
| Stateful storage | The chart creates StatefulSets, PVCs, or storage-related objects. These need target-fit and upgrade care. | 31 | 90 | bitnami/elasticsearch, bitnami/memcached, bitnami/mongodb, bitnami/mysql |
| Generated facts | The chart or recipe needs generated values such as passwords, certs, or names. We record those as facts instead of hiding them. | 29 | 85 | bitnami/apache, bitnami/contour, bitnami/elasticsearch, bitnami/memcached |
| Cluster lookups | The render can depend on live cluster data. We route that through target facts or a named limitation. | 26 | 72 | bitnami/apache, bitnami/contour, bitnami/elasticsearch, bitnami/memcached |
| CRDs | The chart includes custom resource definitions or depends on them. We track whether CRDs are installed, omitted, staged, or observed. | 18 | 56 | bitnami/contour, cloudnative-pg/cloudnative-pg, external-dns/external-dns, fairwinds-stable/goldilocks |
| Webhooks | The chart installs admission or conversion webhooks. We track certificate lifecycle, readiness, and server-side behavior separately from render parity. | 13 | 37 | cloudnative-pg/cloudnative-pg, elastic/eck-operator, fairwinds-stable/goldilocks, fairwinds-stable/vpa |
| Helm hooks | The chart uses Helm hook behavior. Hooks are routed, observed, blocked, refused, or marked target-specific. They are not silently treated as ordinary static YAML. | 5 | 13 | fluent/fluent-bit, gatekeeper/gatekeeper, kyverno/kyverno, projectcalico/tigera-operator |
Important Boundaries
Render parity is not enough
A chart can render the same objects as Helm and still need CRDs, a Secret, webhook readiness, storage, cloud identity, or a controller to be ready.
Hooks are explicit routes
A hook route tells you what must happen. It is not a claim that every hook is automatically executed by the public catalog.
Watch is useful
A watch or blocked row is not hidden failure. It is the catalog saying what remains to stage, observe, or decide.