argo-cd/argo-rollouts Helm chart · ConfigHub Workshop

What it is. argo-cd/argo-rollouts 2.40.9, as 14 Kubernetes objects in its default preset.

Install it. curl -fsSL -o try-objects.sh https://confighub.github.io/helm-expt/site/sh/argo-cd-argo-rollouts-2-40-9/default/try-objects.sh && bash try-objects.sh

OCI bundle. oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bundles/catalog-argo-cd-argo-rollouts-2-40-9-default:latest@sha256:797b57dfa0287b34b48423bd23383a6f8ae7cd8c55518c3f62210a0d8aacf2bc

Needs first. Nothing. The script applies any CRDs first.

How it works. How the model works, and Helm in the Catalog.

Pick a version and a base

Versions are listed newest first. Each row is one base, and every cell is read from that base's listing. A base marked watch has a checked result with a limit to review.

2.40.9 newest

2 bases. The installer package is published and signed. Open the page for 2.40.9.

Base	Objects	Flattening verdict	Published as OCI	Flag	Open
default default	14	flatten-with-routes	Published	None	exact objects · listing
no-crds	9	safe-to-flatten	Published	None	exact objects · listing

See what changes

Choose two versions or two bases, then press Compare. The page fetches the two retained files and checks each file's SHA-256 against the digest its listing records. It then computes the diff on demand, in your browser, with the code that cub config diff runs. Nothing is precomputed or stored.

Run the same diff yourself

These commands fetch the same two files and compare them on your machine, with no account. They follow the pair you choose above. cub plugin install confighub/cub-workshop@v0.6.61 adds cub config diff.

# fetch the first retained file
$ curl -fsSL -o argo-cd-argo-rollouts-2-40-9-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/argo-cd/argo-rollouts/2.40.9/revisions/default/r001/rendered/release-objects.yaml

# fetch the second retained file
$ curl -fsSL -o argo-cd-argo-rollouts-2-40-9-no-crds.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/argo-cd/argo-rollouts/2.40.9/revisions/no-crds/r001/rendered/release-objects.yaml

# check the bytes against the two listings
$ shasum -a 256 argo-cd-argo-rollouts-2-40-9-default.yaml argo-cd-argo-rollouts-2-40-9-no-crds.yaml
cd696130d24a1a676d5bc1abb9978ff10d6d4e6e072655c6ef275453b1e85e47  argo-cd-argo-rollouts-2-40-9-default.yaml
6facde581531cc4995b342bf9b3614f4c73f5c8d9ba057ae92895db6c3813dd7  argo-cd-argo-rollouts-2-40-9-no-crds.yaml

# count what changes
$ cub config diff argo-cd-argo-rollouts-2-40-9-default.yaml argo-cd-argo-rollouts-2-40-9-no-crds.yaml --summary

# list every changed field
$ cub config diff argo-cd-argo-rollouts-2-40-9-default.yaml argo-cd-argo-rollouts-2-40-9-no-crds.yaml

Use this entry in ConfigHub

Every Catalog entry page carries these five steps in this order. Each step says what the Catalog has run for this entry, and a step with a missing precondition gives no command.

Steps 1 and 2 need no account. Install the cub CLI before any cub command. Step 2 uses cub config diff, which cub plugin install confighub/cub-workshop@v0.6.61 adds. A live walk on 2026-10-08 ran steps 3 to 5 for bitnami-nginx-24-0-2-http-clusterip and nvidia-gpu-operator-v26-3-3-default. These commands carry the changes that walk needed. It is a dated log and no receipt, so no state on this page rests on it. These are the steps for 2.40.9, the newest version, on its default base.

What is fixed, and what you supply

Fixed when this entry was built. These went into the build, so the objects already carry them. To change one, build the entry again from its source.

chart is argo-cd/argo-rollouts
version is 2.40.9
base is default
valuesProfile is recipes/argo-cd/argo-rollouts/2.40.9/effective-values.yaml
namespace is default
releaseName is argo-rollouts
capabilityProfile is {"apiVersions":[],"kubeVersion":"1.30.0"}

Yours to supply or check. The listing records no input for the destination. The Catalog has not ruled one out for your cluster.

This entry's plan, and how to test it

These are the steps that plain objects cannot carry. ConfigHub stores them and does not carry them out. The words in italics say what the Catalog knows about each.

When you deliver. CRD ordering declaration for the 5 definition(s) this base renders. Who: selected destination actor. Written down. Not run by the Catalog.
Once the destination is known. Prune protection for the 5 object(s) carrying the keep promise. Who: selected destination actor. Written down. Not run by the Catalog.

Test the install steps yourself. This script carries them out with kubectl on a cluster you choose, with no account. Read it first and use a throwaway cluster. The Catalog has no recorded run of this script.

Test the plain objects. A second script tests the retained objects themselves with kubectl, and it needs no cub and no account. The Catalog has no recorded run of this script.

Compared with plain Helm. The Catalog installed this base beside plain Helm on two local clusters, and the two matched. Read the receipt.

Read what a plan is, and why some entries have one.

1. Get the exact objects Run for this entry

The Catalog rendered this entry and retains its 14 objects in one file.

An upload can create more Units than the objects counted here. The installer renders a Namespace, and the upload adds an installer-record Unit.

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.

# fetch the retained objects for this entry
$ curl -fsSL -o argo-cd-argo-rollouts-2-40-9-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/argo-cd/argo-rollouts/2.40.9/revisions/default/r001/rendered/release-objects.yaml

# check the bytes against the listing
$ shasum -a 256 argo-cd-argo-rollouts-2-40-9-default.yaml
cd696130d24a1a676d5bc1abb9978ff10d6d4e6e072655c6ef275453b1e85e47  argo-cd-argo-rollouts-2-40-9-default.yaml

# render this base from the signed package; step 3 uploads this directory
$ cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/argo-cd-argo-rollouts:2.40.9@sha256:e77d2622b0c73818226779e719ecd8841bc282c710b5cc193940ff5cb8ee00ab --base default --work-dir ./argo-cd-argo-rollouts-2-40-9-default --non-interactive --namespace default

2. Compare with another version or base Not run for this entry

The listing records no comparison for this entry. The commands run on the retained files, with no account. This version has one other base in the Catalog, no-crds.

# fetch the no-crds base of the same version
$ curl -fsSL -o argo-cd-argo-rollouts-2-40-9-no-crds.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/argo-cd/argo-rollouts/2.40.9/revisions/no-crds/r001/rendered/release-objects.yaml

# list what differs between the two bases
$ cub config diff argo-cd-argo-rollouts-2-40-9-default.yaml argo-cd-argo-rollouts-2-40-9-no-crds.yaml --summary

3. Upload it as a variant Run for this entry

The Catalog saved this entry in ConfigHub. The commands use its signed installer package. Read the log of the live walk on 2026-10-08 · Read the record that states this.

Replace each value in angle brackets with a name of your own. The entry id may already exist as a Space in your organization, and the package name as a Component.

In the live walk, a Space named for the nginx entry's id and a Component named bitnami-nginx already existed, so the walk chose its own names. The --component flag sets the Component label the upload writes on the Space, which is the package name when you omit it.

The cub installer plugin reads your organization from CUB_CONTEXT and ignores --context. If you use a context other than your default, export CUB_CONTEXT first, or the plugin works in your default organization.

# sign in; steps 3 to 5 write to your ConfigHub organization
$ cub auth login

# upload step 1's directory as a Space of Units, under names you choose
$ cub installer upload --work-dir ./argo-cd-argo-rollouts-2-40-9-default --space <your-space> --component <your-component>

# list the Units the upload created
$ cub unit list --space <your-space>

4. Deploy it Not run for this entry

No delivery run is recorded for this entry. Argo CD has not run, Flux has not run, and kubectl has not run. The commands name the Target workshop/target, which cub cluster up --name workshop creates on a local kind cluster with Argo CD. Use your own Target for a real destination. The coverage lanes record a local Kubernetes run and a GitOps OCI run for this base. They are separate from the delivery record this step reads. Read the log of the live walk on 2026-10-08.

Use the Space name you chose in step 3. The delete command is needed because the cloned installer-record Unit carries the Target and Argo CD v3.5.4 cannot read it, a defect seen on cub v0.8.7 and server v0.8.9.

Without that line the walk deployed nothing and Argo CD showed Unknown, while every cub command exited 0. The walk ran the four commands in this order and did not try them without the first publish.

ConfigHub shows nothing when Argo CD fails to read a Release. Run kubectl -n argocd get applications.argoproj.io and read the Sync column, because Healthy alone is not a pass. Argo CD took between 18 seconds and about 5 minutes to read a Release on a cluster made without argobot.

The walk made its cluster with cub cluster up --no-argobot. That command creates two Spaces, a Worker, a Target and a Trigger, opens ports 30010 to 30019 on the machine, and installs Argo CD from an unpinned upstream manifest.

Removing the ConfigHub side does not remove the workload. In the walk, deleting the Application Unit and the Spaces left the Application and its pods running, because the root Application does not prune.

# clone the base onto a Target as a dev variant
$ cub variant create dev <your-space> --target workshop/target --space-pattern "template:<your-space>-dev"

# publish the Release that the cluster's Argo CD pulls
$ cub release publish <your-space>-dev

# delete the installer record, which Argo CD cannot read
$ cub unit delete --space <your-space>-dev installer-record

# publish again without it
$ cub release publish <your-space>-dev

5. Promote a change Partly run for this entry

A promotion ran for this entry. It ran the preview and the promote. The delete and the publish below have no recorded run for this entry. Promotion carries a change in the base to the dev variant. The base changes when you edit a Unit or upload a newer version into the same Space. Read the log of the live walk on 2026-10-08 · Read the record that states this.

The promotion changes the dev Space and publishes nothing. It also adds the installer-record Unit back with the Target. The change reaches the cluster only after the delete and the publish.

The preview lists the whole installer record as added. In the walk, the preview of a one-label change to gpu-operator ran to 405 lines, and about 400 of them were that record.

# preview what the dev variant would take from the base
$ cub variant promote <your-space>-dev --dry-run -o mutations

# promote once you have read the preview
$ cub variant promote <your-space>-dev --change-desc "Pull the reviewed base forward"

# delete the installer record that the promotion adds back
$ cub unit delete --space <your-space>-dev installer-record

# publish the Release that carries the change
$ cub release publish <your-space>-dev

For agentsThese steps are the nextSteps array of argo-cd-argo-rollouts-2-40-9-default.json. Each state was read from flattened.retainedObjects, flattened.inventory, source.ociRef, oci.bundles, oci.runtimes, lifecycle.promotion, lifecycle.coverage and variants.known in the same listing. A command marked needsAccount there contacts ConfigHub. A step's notes hold its cautions, carries lists the CRDs the base brings, and liveWalk links the dated log that ran its commands.

Use another version or base

Every other base carries the same five steps, with its own states and commands, on the page of its version.

The same five steps on the page for 2.40.9 cover the base no-crds.

Read this page as data

One file holds everything on this page in a form a program can read.

Technical notes and disclaimers

The plain-objects script applies the objects and ends. It does not wait for the workloads to start. Neither script runs the steps the plan names for an upgrade or a delete.