argo-cd/argo-cd@9.5.15 Production Packet

What this command does. cub installer is a released, open-source plugin for the cub CLI. cub installer setup pulls a catalog package and writes its Kubernetes files locally. It does not apply those files to a cluster; use kubectl, Argo CD, or Flux for delivery. The generated scripts stop before doing any work when the plugin or kustomize is missing.

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.

This generated packet summarizes the current support story for a hard chart. It is a navigation surface over existing evidence, not a new support decision.

Current Answer

Field	Value
Supported base	`default`
Support decision	`supported`
Production disposition	`production-review-ready`
Target scope	cub-lk-kind-vanilla; namespace=argocd; delivery=confighub-oci; controller=argo
Delivery path	`confighub-oci`
Evidence count	16
Strongest user-facing evidence	live-helm-vs-confighub-parity
Live summary	local:1/2 gitops:2/2 live-parity:2/2 two-cluster:1/2

Why This Chart Is Hard

GitOps control plane with CRDs, repository credentials, optional self-management, SSO, backup/restore, and bootstrap-order concerns.

What A User Can Safely Do Today

Use default for the declared proof scope. Hardened, self-managed, repository-credential, SSO, or backup/restore paths need separate support decisions.

What Remains Before Broader Production Use

Keep the target-scoped evidence fresh before using this supported scope as a production-support example; create separate hardened, self-managed, repository-credential, SSO, or backup/restore bases for real customer GitOps control planes.

Bases

Base	User readiness	Lane summary	Target facts	Command
`default`	start-here	render=pass; confighub=pass; local=pass; gitops=pass; live-parity=pass; two-cluster=pass	required Secret argocd/argocd-redis keys auth	`cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-cd:9.5.15 --base default --work-dir <tmp> --non-interactive --namespace argocd`
`no-crds`	render-only	render=pass; confighub=pass; local=blocked; gitops=pass; live-parity=pass; two-cluster=missing	required Secret argocd/argocd-redis keys auth; required CRD applications.argoproj.io; required CRD applicationsets.argoproj.io; required CRD appprojects.argoproj.io	`cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-cd:9.5.15 --base no-crds --work-dir <tmp> --non-interactive --namespace argocd`

Quirks And Inputs

Field	Value
Quirks surfaced	crds;existing-secret;extension-slots
User must provide	an existing Secret for some bases (buildable - not yet run); a CRD ownership choice (crds vs no-crds base)
ConfigHub / installer absorbs	exact rendered objects with render parity and receipts; CRD handling split into explicit bases; extension slots routed to reviewed bases
Extension slot route	none recorded

Decision Details

Decision	State
Image policy	`mutable-image-exception-accepted-for-target-scope`
Scan policy	`resource-policy-accepted-for-target-scope`
Lifecycle policy	`lifecycle-observed-for-proof-scope`
Target facts	`no-unresolved-target-prerequisite-in-candidate-base`
Live evidence	`fresh-target-evidence-passed`

Evidence Links

Regenerate:

npm run hard-charts:packets
npm run hard-charts:packets:verify