argo-cd/argo-workflows
Runs on your laptop
Review a recorded configuration for argo-cd/argo-workflows@1.0.14. Read its exact Kubernetes objects, required setup, and current evidence before you deploy it.
The first recorded configuration is default. Read its status before use; it is not yet a polished public example. The page does not claim every possible values combination.
Evidence labels: Pass has a linked result. Watch names a limit to check. Blocked means do not use that path yet.
Upstream: find this chart on Artifact Hub · Helm documentation. This page adds checked configurations and test results.
Catalog readiness: Review before use.
Licenses: chart Apache-2.0 (the chart source repository's LICENSE, read 2026-08-08). This describes the chart templates, not the packaged application images.
Check this chart and version Try the package Plan an upgrade or promotion
Already reviewed the result? Keep it in ConfigHub when you need history, variants, approvals, or delivery.
What this page gives you
Every chart page follows the same order. Choose a configuration, inspect its objects and setup work, then read the tests that have run. Open the worked examples.
The package fixes and checks almost everything at build time. What you set is small and typed.
Open the saved results for the Helm comparison, live install, and delivery checks.
The page names the work and says which delivery path has actually run.
What To Use
default configuration: 19 rendered objects · 2 images · 8 target prerequisites · 1 hook or setup route · 6/7 checks passing. These counts come from the linked test records.
defaultFirst recorded base variant
3Candidate base variants
Review before useFirst-configuration status
Not reviewed for productionProduction status
The recipe/package proof exists and useful variants exist, but this chart has not been promoted into the public catalog.
| Question | Answer |
|---|
| Catalog readiness | Review before use |
| Chart version | 1.0.14 |
| Exact installer package | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f |
| OCI publication status | publication receipt recorded |
| Publisher signature | publisher signature recorded and verified |
| Latest upstream seen | not checked |
| Candidate base variants | default;controller-default-reviewed;minimal-crds |
| Not yet available | No specific missing capability is recorded. The first configuration still needs review. |
| Namespace | default |
Four Separate Questions
Inspecting a source, producing objects, checking a destination, and checking a live result are different jobs. A Catalog match is useful for comparison but is not required. A missing destination or deployment is shown as not run or blocked, not as a failed configuration.
| Question | Current answer | What it needs | Status |
|---|
| What do I have? | Inspect the helm source, choices, locks, and any existing output before selecting a destination. | Destination access: no
Selected configuration deployed: no | Available to inspect
evidence recorded |
| What will it produce? | Run the recorded Helm render step to produce the exact Kubernetes objects for this configuration. | Destination access: no
Selected configuration deployed: no | Checked: passed
evidence recorded |
| Can this destination accept it? | The destination has not been checked for this exact configuration. A recorded source or render result is not a destination pass. | Destination access: yes
Selected configuration deployed: no | Not run
no run recorded |
| Did it work? | No post-deployment result is recorded for this exact configuration. Publication, upload, or rendering is not proof that it ran correctly. | Destination access: yes
Selected configuration deployed: yes | Not run
no run recorded |
Open the complete assessment, source, lifecycle, and evidence record.
Where This Chart's Settings Come From
| Base variant | Helm values | ConfigHub changes | Install work |
|---|
| default | effective-values.yaml | None in the catalog base. Later edits appear in ConfigHub Unit revision history or a derived variant. | 8 prerequisites and 1 hook or setup route recorded. |
| controller-default-reviewed | effective-values.yaml | None in the catalog base. Later edits appear in ConfigHub Unit revision history or a derived variant. | 8 prerequisites and 1 hook or setup route recorded. |
| minimal-crds | effective-values-minimal-crds.yaml | None in the catalog base. Later edits appear in ConfigHub Unit revision history or a derived variant. | 1 hook or setup route recorded. |
Upgrade rule: if a new Helm render and a ConfigHub revision both change the same field, review the overlap before promotion. The values profile shows the Helm side; Unit revision history shows the ConfigHub side.
Read the full values-versus-ConfigHub rule. For the staging commands behind each prerequisite, open the prerequisite action packets.
What This Chart Contains
Shipping a chart as plain rendered YAML is faster and simpler, and it silently drops anything Helm was going to do afterwards. This section reports what a scan of the packaged chart found, across 45 files.
| Construct | Found | Why it matters when a chart ships as plain YAML |
|---|
| Helm hooks | 4 | Hook Jobs never fire, or fire under a different hook dialect. |
| Keep policy | 9 | A reconciler prunes what Helm promised to keep. |
| Capability branching | 3 | The chart chooses apiVersions from the cluster it renders against. |
| Custom resource definitions | 8 | Per-file delivery can race the definitions the resources depend on. |
A flattening-safety verdict has decided this version: controller-default-reviewed:flatten-with-routes; default:flatten-with-routes; minimal-crds:flatten-with-routes. The verdict records one disposition per construct and names any companion artifact a flattened bundle must ship.
A construct being present does not make a chart unflattenable. Most are switched on or off by values, and a verdict records which ones the base you choose actually reaches. Read the catalog-wide evidence for how common each one is.
What The Starting Configuration Records
A base variant is a starting configuration we have already rendered and checked. Pick the one whose trade-off you want; the table below shows what each one changes. How the values for each are chosen.
The default base-variant record connects those Helm inputs to the Kubernetes objects, remaining requirements, hooks, CRDs, checks, and OCI status. Open it when you need the complete starting record rather than only the rendered YAML.
Open the full rendered YAML to read the actual manifest output. The render record and setup section explain the inputs, tests, CRDs, hooks, and other work around it.
If new Helm values create a useful starting configuration, record another base variant with its own inputs and checks. If one environment changes a field after rendering, record that change in a ConfigHub variant.
| Key | Where to look first | What it means |
|---|
| Package users pull | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f | The exact installer package for this chart version. The version tag is readable, and the manifest digest makes a published pull immutable. Public catalog package refs are published in Google Artifact Registry with anonymous read access. No ConfigHub account or Google registry login is needed for the local setup path. |
| Required before apply | 8 CRDs
Included in the OCI package as prerequisites/target-facts/default-crds.yaml. It refreshes the locked CRDs with the chart's server-side, force-conflicts apply mode. The generated try script runs this step before the workload and waits for every CRD to become established. | External resources the recommended base variant expects, such as an existing Secret, namespace, CRD, or target fact. |
| Kubernetes objects | full rendered YAML | The full YAML captured from this base variant. It is the output of the render. |
| Render record | default render intent | The Helm inputs and evidence links that explain how the output was produced. |
| Complete starting record | default base-variant record | The record that connects the Helm inputs, Kubernetes objects, remaining requirements, setup work, checks, and OCI status. |
| Hooks, CRDs, and setup work | this page's setup section | Instructions and decisions for hooks, CRDs, generated Secrets, setup jobs, cluster requirements, or blockers. |
Choose base variant
Pick the supported Helm configuration for this chart: default, no-CRDs, existing Secret, HA, server-only, or another listed option.
Record inputs
Keep the values, namespace, release name, source lock, default render intent, full YAML output, package base, test results, and setup instructions together.
Handle chart extras
CRDs, hooks, setup jobs, external Secrets, target facts, and webhook certificates are recorded as chart-specific choices. Some are included in a base variant, some need a setup step, and some are blocked until there is a safe path.
How render intents work · All generated render intents · All base variant records
Try This Chart
Review default before use. If a card says review or preparation is needed, treat that as a real limit rather than a ready install.
Package image
Exact package: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f
publication receipt recorded · open the exact publication receipt
Readable version tag: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14. The package is pinned so a republished tag cannot change what you get. The command below uses the exact manifest digest, so cub installer refuses different package bytes.
Check the package identity
New to cub? Install the cub CLI first. Public catalog packages pull and render anonymously, and you sign in only once a command saves or changes ConfigHub data.
cub installer inspect oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f --json
Read how each configuration was made
cub installer pull 'oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f' --work-dir ./package-review
less ./package-review/package/records/README.md
The package's records/ directory connects every base to its source choices, Helm render intent, Kubernetes objects, prerequisites, lifecycle work, and checks. These are supporting records, not Kubernetes objects.
Verify the package publisher
Run this command with cosign. It checks the expected publisher, the exact manifest digest, and the package annotations.
cosign verify --certificate-identity helm-expt-package-signer@nth-fort-499605-q5.iam.gserviceaccount.com --certificate-oidc-issuer https://accounts.google.com --annotations confighub.com/package-path=packages/argo-cd/argo-workflows/1.0.14 --annotations confighub.com/package-sha256=901c531b5cecf84ca8aa80a3a5c45608b6d0f18d8856196871fb70360ba75459 europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f
A valid signature identifies who signed these package bytes. It does not show that the configuration is suitable for your cluster; use this page's checks and setup instructions for that decision.
Signature receipt · Sigstore bundle · How signature verification works
Public catalog package refs are published in Google Artifact Registry with anonymous read access. No ConfigHub account or Google registry login is needed for the local setup path.
First recorded command
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f --base default --work-dir ./argo-cd-argo-workflows-1-0-14-default --non-interactive --namespace default
Advanced: apply it or upload it
Run the whole sequence as one script, prerequisites included: try.sh renders and applies to Kubernetes without an account; confighub.sh renders and uploads to your ConfigHub Space.
Before you run try.sh: it changes your current kubectl context. It runs the named prerequisites and applies the rendered objects. Read it first and use a disposable test cluster. confighub.sh does not apply anything to Kubernetes.
You should see something like this
Here is what the command does. cub installer is an open-source plugin for the cub CLI. cub installer setup pulls a catalog package and writes its Kubernetes files locally, leaving delivery to kubectl, Argo CD or Flux. The generated scripts stop before doing any work when the plugin or kustomize is missing.
cub installer setup ...
rendered manifests written under <work-dir>
use the chart option cards below to check pass, watch, blocked, and prerequisites
Current status: Available in the catalog · Reason: Promotion was tested and recorded in ConfigHub.
After You Render It
The first command writes files and does not apply them. Read the objects and setup requirements, then choose the next job.
| Job | Next step |
|---|
| Render and inspect without applying | Run the recommended cub installer setup command above. |
| Run shared local configuration checks | cub plugin install confighub/homebrew-tap@cub-scan-v0.7.3 --name scan
cub check --format json --output cub-check.json <work-dir>/out/manifests. The check is advisory and does not apply anything. |
| Apply the rendered manifests with kubectl, or publish reviewed objects as OCI | Publish reviewed objects as OCI or apply the manifests with kubectl. |
| Save the reviewed result for a team | Save and upload the reviewed result to ConfigHub for shared history, exact diffs, and approvals. |
| Compare development and production, audit an exact diff, promote, or roll back | Build a promotion review or read the bounded rollback example. |
| Assign the configuration to clusters and operate a small fleet | Choose targets, preview a wave, and inspect every result. |
| Check delivery limits | Read the current limits before choosing kubectl, Argo CD, or Flux. |
| Handle CRDs on the first install | Read the CRD ordering risk and first-install guide, then check this chart's recorded owner and route. |
Argo Workflows CRDs
The normal Helm install runs a hook that downloads eight full CRD files from GitHub and applies them before the controller and server. Those CRDs are not in the ordinary rendered release, so another delivery path has to replace that step deliberately.
The catalog package contains the exact eight files used by this chart version. Their source URLs and digests are recorded. The no-account script applies them with the same server-side, force-conflicts mode as the Helm hook, waits for them to become established, and then applies the ordinary objects.
| Choice | What happens |
|---|
default | Uses the full upstream CRD schemas. The package applies the locked CRD bundle before the workloads. |
minimal-crds | Renders eight smaller CRDs as ordinary objects. This avoids the hook but uses looser schemas that preserve unknown fields. |
| Argo CD or Flux | Ordering still needs its own controller-specific proof. The direct package result does not claim either controller ran this step automatically. |
Two clean kind clusters checked the direct path: Helm ran its real hook in one, the catalog package ran its CRD action in the other, all eight live CRD specifications matched, the 19 ordinary objects matched, and both workloads became ready.
Read the plain-English guide and repeat the test · Open the receipt
Available Configurations
Each card is one available way to use this chart in the catalog. Some cards are runnable base variants. Others are candidate paths, derived variants, or review notes that explain what still has to be prepared.
Checks: Each card names what was checked and says whether it passed, needs review, was blocked, was not run, or was not needed.
4 matrix rows for argo-cd/argo-workflows@1.0.14 · open the full matrix
F1 · Source chart
(source)
Source
Pinned upstream chart and version
- Status
- Available in the catalog
- How to run
- This is the upstream chart source. Choose a base card below before running the installer.
- Evidence
- Pinned chart source and dependency lock
- Hooks/actions
- 1 source hook; hook route: observed; live action receipt: yes
- Who runs actions?
- read the route receipt before delivery
- Next
- Choose a chart configuration before rendering or deploying
- Reason
- This is the chart source. Choose a configuration before checking deployment or promotion
Helm outputNot neededSaved in ConfigHubNot neededLocal clusterNot neededSetup routeNot neededGitOps and OCINot neededLive Helm comparisonNot neededTwo clustersNot neededPromotionNot needed
catalog · source repo
F2a · Chart default
default
Base
Runnable base variant made from the chart defaults
- Status
- Available in the catalog
- Helm values
- effective-values.yaml
- ConfigHub changes
- None in this catalog base. After upload, read Unit revision history or the derived variant.
- How to run
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f --base default --work-dir ./argo-cd-argo-workflows-1-0-14-default --non-interactive --namespace default- Scripts
- try.sh renders, settles the prerequisites in order, and applies with kubectl; confighub.sh renders and uploads to your ConfigHub Space.
- Evidence
- Live helm vs confighub parity
- Hooks/actions
- 1 source hook; hook route: observed; live action receipt: yes; 1 recorded lifecycle route
- Who runs actions?
- You or your delivery pipeline (1); the full record shows which delivery paths have receipts
- Lifecycle record
- 1 chart-specific lifecycle route is recorded. The full record separates direct, Argo CD, and Flux handling and says which paths have actually run. Open the full record.
- Prerequisites
- 8 prerequisites are declared for this base. Each prerequisite says whether it must be checked before render or before apply.
- Next
- Run catalog promotion review
- Reason
- Promotion was tested and recorded in ConfigHub.
Helm outputPassedSaved in ConfigHubPassedLocal clusterBlockedSetup routePassedGitOps and OCIPassedLive Helm comparisonPassedTwo clustersPassedPromotionPassed
catalog · variant · full YAML · render intent · base record · package base · receipt · source repo
F2b · Helm-rendered base
controller-default-reviewed
Base
Runnable base variant made with different Helm values
- Status
- Available in the catalog
- Helm values
- effective-values.yaml
- ConfigHub changes
- None in this catalog base. After upload, read Unit revision history or the derived variant.
- How to run
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f --base controller-default-reviewed --work-dir ./argo-cd-argo-workflows-1-0-14-controller-default-reviewed --non-interactive --namespace default- Scripts
- try.sh renders, settles the prerequisites in order, and applies with kubectl; confighub.sh renders and uploads to your ConfigHub Space.
- Evidence
- Live helm vs confighub parity
- Hooks/actions
- 1 source hook; hook route: candidate-route; live action receipt: todo; 1 recorded lifecycle route
- Who runs actions?
- Not automated yet (1); the full record shows which delivery paths have receipts
- Lifecycle record
- 1 chart-specific lifecycle route is recorded. The full record separates direct, Argo CD, and Flux handling and says which paths have actually run. Open the full record.
- Prerequisites
- 8 prerequisites are declared for this base. Each prerequisite says whether it must be checked before render or before apply.
- Next
- Run catalog promotion review
- Reason
- Promotion was tested and recorded in ConfigHub.
Helm outputPassedSaved in ConfigHubPassedLocal clusterBlockedSetup routeNot runGitOps and OCIPassedLive Helm comparisonPassedTwo clustersPassedPromotionPassed
catalog · variant · full YAML · render intent · base record · package base · receipt · source repo
F2b · Helm-rendered base
minimal-crds
Base
Runnable base variant made with different Helm values
- Status
- Available in the catalog
- Helm values
- effective-values-minimal-crds.yaml
- ConfigHub changes
- None in this catalog base. After upload, read Unit revision history or the derived variant.
- How to run
cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f --base minimal-crds --work-dir ./argo-cd-argo-workflows-1-0-14-minimal-crds --non-interactive --namespace default- Scripts
- try.sh renders, settles the prerequisites in order, and applies with kubectl; confighub.sh renders and uploads to your ConfigHub Space.
- Evidence
- Live helm vs confighub parity
- Hooks/actions
- 1 source hook; hook route: observed; live action receipt: yes; 1 recorded lifecycle route
- Who runs actions?
- Kubernetes or the delivery controller (1); the full record shows which delivery paths have receipts
- Lifecycle record
- 1 chart-specific lifecycle route is recorded. The full record separates direct, Argo CD, and Flux handling and says which paths have actually run. Open the full record.
- Prerequisites
- This base has not yet been reviewed for required Secrets, CRDs, namespaces, values, storage services, external APIs, or target topology. Record what it needs, or record that nothing extra is required.
- Next
- Run catalog promotion review
- Reason
- Promotion was tested and recorded in ConfigHub.
Helm outputPassedSaved in ConfigHubPassedLocal clusterPassedSetup routePassedGitOps and OCIPassedLive Helm comparisonPassedTwo clustersPassedPromotionPassed
catalog · variant · full YAML · render intent · base record · package base · receipt · source repo
Local Configuration Checks
We ran cub check v0.7.3 against the exact rendered objects for every configuration below. The result is advisory: read each finding and decide whether it matters for your target.
Scanner and ruleset identity
Pattern bundle: v0.7.3
Bundle manifest: sha256:0405f6ffe21e567adf5d6a732d181c7f228194920456d046b4338baeb14de1a8
Risk catalog: sha256:7ff79a126ad99bba2505fec8b2b7711c03f50eb362141128ec1c83e27a5036ba
| Configuration | Advisory result | Exact input | Checked | Evidence |
|---|
controller-default-reviewed | 14 advisory findings
3 critical, 8 warning, 3 info
ClusterRole grants secrets read permissions
ClusterRole grants pods/exec create
Deployment containers omit resource limits | 19 objects
sha256:dc19626f2c2690dd05f50e898645a6ba4e68cf5ca16876b1fbe66f96e1b1b6e0 | 2026-08-24 | Full cub check result
Exact YAML
Separate Catalog review |
default | 14 advisory findings
3 critical, 8 warning, 3 info
ClusterRole grants secrets read permissions
ClusterRole grants pods/exec create
Deployment containers omit resource limits | 19 objects
sha256:dc19626f2c2690dd05f50e898645a6ba4e68cf5ca16876b1fbe66f96e1b1b6e0 | 2026-08-24 | Full cub check result
Exact YAML
Separate Catalog review |
minimal-crds | 14 advisory findings
3 critical, 8 warning, 3 info
ClusterRole grants secrets read permissions
ClusterRole grants pods/exec create
Deployment containers omit resource limits | 27 objects
sha256:af6fbedcce57f01458d7c8a8f50927f012732a9305ad2bce8413814f79fe1633 | 2026-08-24 | Full cub check result
Exact YAML
Separate Catalog review |
What this does not check: hook execution, CRD readiness, target Secrets and cloud services, admission behavior, workload health, or rollback. The linked Catalog review covers chart-specific source and operating questions. ConfigHub validation and approval are separate managed controls.
Read all shared check results and the mapping to Catalog rules.
Images This Chart Pulls
Every reference below comes from the reviewed rendered output. What you see is what the cluster pulls. These references are data: you can change a registry or pin a digest with a recorded edit, and prove the change landed in every environment.
| Base variant | Images |
|---|
| default | quay.io/argoproj/argocli:v4.0.5
quay.io/argoproj/workflow-controller:v4.0.5 |
| controller-default-reviewed | quay.io/argoproj/argocli:v4.0.5
quay.io/argoproj/workflow-controller:v4.0.5 |
| minimal-crds | properties:
quay.io/argoproj/argocli:v4.0.5
quay.io/argoproj/workflow-controller:v4.0.5
type: string |
First-Run Caveats
Some chart paths need a small preparation step before the cub path feels as smooth as Helm. We show those steps here so the first run does not surprise you.
| Caveat | What to do |
|---|
| Universal caveats | Use declared inputs or bases instead of Helm --set. For direct delivery, define pruning and field-conflict behavior. Use Argo CD or Flux when that controller path and its pruning settings are recorded for the selected preset. |
| Shared placeholder password | No shared placeholder password caveat recorded for this chart. |
| CRD first-ordering | Yes. 8 CRDs must exist first. The public package contains the bootstrap, and its generated try.sh applies it and waits for the CRDs before installing the main objects. |
Open the all-chart adoption caveats · Helm to cub migration · cub deployment path
Advice And Current Status
Use this section to see which chart-specific guides apply, what you must provide, and what work remains.
| Question | Current answer |
|---|
| User status | Works with operator review |
| Can I use it? | Tests and useful configurations exist, but the catalog review is not finished. |
| First base | minimal-crds |
| Exact installer package | oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-workflows:1.0.14@sha256:abbebaeccc07e0583c7ccc5ad0c9d315057e6b4c0a766bd72c167ee92d3f160f |
| Tests completed | Tests complete; ready for catalog review (render parity 3/3; Local live 1/3; Live parity 3/3) |
| Coverage | Partial |
| You must provide | nothing beyond a cluster and namespace |
| What the tools record | exact rendered objects with render parity and receipts; optional chart inputs handled by reviewed base configurations |
| Next action | run catalog promotion review |
The source data lives in chart skills and chart evidence router.
What Has Been Tested
Choose the question you care about. Not checked means this catalog has no version-specific result; it is not a pass.
How much is proven, and what more testing would add: Fully proven: Render parity, ConfigHub proof, GitOps/OCI live, Live Helm-vs-ConfigHub, Two-cluster kind. Proven on some bases: Local live.
| Base | Readiness | Render | ConfigHub | Local live | GitOps/OCI | Live parity | Two-cluster kind |
|---|
| default | real | yes | yes | no | yes | yes | yes |
| controller-default-reviewed | real | yes | yes | no | yes | yes | yes |
| minimal-crds | real | yes | yes | yes | yes | yes | yes |
What You Must Provide
exact rendered objects with render parity and receipts; optional chart inputs handled by reviewed base configurations
| Field | Value |
|---|
| Known quirks | optional chart inputs |
| You must provide | nothing beyond a cluster and namespace |
| What ConfigHub records | exact rendered objects with render parity and receipts; optional chart inputs handled by reviewed base configurations |
| Optional chart inputs | Tpl powered values |
| How optional inputs are handled | Keep empty in supported bases; Or make a reviewed installer base when populated |
Hooks, CRDs, And Setup Work
Some Helm charts need work before, during, or after apply: CRDs, hooks, setup jobs, webhook certificates, migrations, generated Secrets, or checks. For each chart, the catalog should make the choice clear: include it in the base variant, split it into a separate base variant, run a setup step, use a GitOps action where evidence exists, require an existing target resource, or block it when there is no safe default.
What each base needs before apply
These requirements come from the same base definition as the rendered objects. The render intent keeps the chart inputs, required Secrets or CRDs, lifecycle routes, and evidence together.
| Base variant | Required resource | How to provide it | Full record |
|---|
| default | 8 CRDs | Included in the OCI package as prerequisites/target-facts/default-crds.yaml. It refreshes the locked CRDs with the chart's server-side, force-conflicts apply mode. The generated try script runs this step before the workload and waits for every CRD to become established. | full render intent |
| controller-default-reviewed | 8 CRDs | Included in the OCI package as prerequisites/target-facts/controller-default-reviewed-crds.yaml. It refreshes the locked CRDs with the chart's server-side, force-conflicts apply mode. The generated try script runs this step before the workload and waits for every CRD to become established. | full render intent |
If no route is shown, that does not prove the upstream chart has no hooks. It means the public catalog has no chart-specific action to show yet; check the matrix or send a problem chart if hook behavior should be modeled. Direct apply, Argo CD, Flux, and upgrade implementations are tracked separately. One passing implementation does not prove the others.
controller-default-reviewed: package applies 8 CRDs first
| Hook or setup step | Who handles it? | Argo CD mapping | Flux mapping | Change for this variant |
|---|
crd-install (preflight-or-presync-crd-apply)
full CRDs required before workflow-controller and server can start; hook uses server-side apply because full CRDs exceed client-side apply annotation limits | Prerequisite - run the generated package script before the workloads | PreSync · sync-wave -2 · ServerSideApply | HelmRelease .spec.install.crds=Create (or apply CRDs first) | packaged-action - the package carries the 8 CRDs and its generated script applies them before the workload; this base still needs its own live route receipt |
Evidence: data/hook-route-candidates/candidates.csv
Next: direct full-CRD package route is proven; next prove controller-run ordering under Argo CD and Flux and test a cross-version CRD upgrade
default: package applies 8 CRDs first
| Hook or setup step | Who handles it? | Argo CD mapping | Flux mapping | Change for this variant |
|---|
crd-install (preflight-or-presync-crd-apply)
The controller and server require the Argo Workflows APIs. Helm normally downloads and applies the full CRDs in a hook before those workloads start. | Handled - the generated package script applies the CRDs first | PreSync · sync-wave -2 · ServerSideApply | HelmRelease .spec.install.crds=Create (or apply CRDs first) | resolved - the package carries and applies the 8 CRDs before the workload (observed live) |
Evidence: data/hook-route-candidates/selected-routes/argo-cd-argo-workflows-default.yaml
docs/demo/hooks-crds/argo-workflows.md
data/hook-route-candidates/argo-cd-argo-workflows.yaml
recipes/argo-cd/argo-workflows/1.0.14/variants/default/variant.yaml
recipes/argo-cd/argo-workflows/1.0.14/upstream/full-crds/argoproj.io_workflows.yaml
packages/argo-cd/argo-workflows/1.0.14/prerequisites/target-facts/default-crds.yaml
runs/live-kind-parity/argo-cd-argo-workflows-default/receipt.yaml
runs/live-helm-confighub-compare/argo-cd-argo-workflows-default/receipt.yaml
minimal-crds
| Hook or setup step | Who handles it? | Argo CD mapping | Flux mapping | Change for this variant |
|---|
crd-install (self-contained-crd-base)
Argo Workflows default full CRDs are installed through a Helm hook using server-side apply; this base chooses the self-contained minimal-CRD route instead. | Your applier - must apply CRDs before dependent objects | no extra hook - keep CRDs before dependent objects | no extra hook - make sure CRDs are applied before workloads | resolved - this base installs the required CRDs (observed live) |
Evidence: data/hook-route-candidates/selected-routes/argo-cd-argo-workflows-minimal-crds.yaml
data/hook-route-candidates/argo-cd-argo-workflows.yaml
recipes/argo-cd/argo-workflows/1.0.14/variants/minimal-crds/variant.yaml
recipes/argo-cd/argo-workflows/1.0.14/revisions/minimal-crds/r001/receipts/install-gate.yaml
runs/next80-local-kind/argo-cd-argo-workflows-1.0.14-minimal-crds/observation-receipt.yaml
runs/argo-workflows-minimal-crds-confighub-proof/latest/confighub-proof-receipt.yaml
runs/live-helm-confighub-compare/argo-cd-argo-workflows-minimal-crds/receipt.yaml
runs/live-kind-parity/argo-cd-argo-workflows-minimal-crds/receipt.yaml
Before Production
A green render or local live result is not a production support claim. Production support is target-scoped and uses the support-decision artifact when present.
| Field | Value |
|---|
| Production review status | Not reviewed for production |
| Target-scoped support decision | not recorded |
| Supported base | |
| Target scope | |
| Accepted limits | None recorded |
| Open policy decisions | None recorded for this policy checklist |
| Next action | run catalog promotion review |
Source And Evidence Files