Helm Lifecycle

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

New to cub? Install the cub CLI first. You can pull and render public catalog packages without an account. Commands that save or change ConfigHub data require you to sign in.

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

title: Helm Lifecycle status: current last_reviewed: 2026-06-14 ---

helm-expt breaks a Helm install into visible stages. The point is not only to render YAML. The point is to show where each decision belongs and where evidence is collected.

The current model is:

  1. Identify the chart source, version, dependencies, and capability assumptions.
  2. Create a cub installer recipe/package with reviewed base variants.
  3. Render deterministically and compare the object set with regular Helm.
  4. Upload or apply the rendered objects through ConfigHub.
  5. Route lifecycle behavior such as hooks, CRDs, target facts, generated values, and webhooks.
  6. Observe live Kubernetes and GitOps outcomes where a live claim is made.
  7. Operate the result with variants, diffs, scans, changesets, approvals, and promotion.

Render parity is the baseline. It says the installer path preserved Helm's intended object set for recorded inputs. It does not prove that every target cluster is suitable or that every controller is healthy.

Authoritative Sources