Try one catalog package

Render one reviewed Redis configuration. Read the Kubernetes objects before you decide where they go.

This exercise does not contact ConfigHub Server or Kubernetes. You do not need a ConfigHub account or a Google registry login.

1. Install cub and the package plugin

Install the ConfigHub CLI. Then install the plugin that reads catalog packages.

$ curl -fsSL https://hub.confighub.com/cub/install.sh | bash
$ export PATH="$HOME/.confighub/bin:$PATH"
$ cub plugin install confighub/installer
$ cub installer version
$ kustomize version

The plugin release contains the program for your operating system. You do not need Go.

If kustomize version fails, follow the official Kustomize installation instructions.

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.

2. Render the Redis package

The public package contains named Redis configurations. Select the configuration that uses a Secret supplied by the target.

$ cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/bitnami-redis:25.5.3 \
    --base reuse-existing-secret \
    --work-dir ./redis \
    --namespace redis \
    --non-interactive \
    --output-oci ./redis-25.oci

cub installer writes 14 Kubernetes objects and no Secret. It also writes a local OCI image layout.

The command reads the OCI output back and compares its object-set digest. It reports pull-back: verified when the comparison passes.

3. Inspect the result

Read the selected configuration and its objects. Nothing has been applied to a cluster.

$ cat ./redis/out/spec/selection.yaml
$ ls ./redis/out/manifests
$ grep -R "^kind:" ./redis/out/manifests

The catalog keeps the source inputs beside the result. It also records the required Secret and the checks for this configuration.

Read the full Kubernetes YAML · Read the recorded inputs and requirements · Read the anonymous run result

Choose what happens next

Local: no server

Pull public packages without signing in. Keep the files or OCI on your machine. Test them locally or in CI.

Read the no-server guide

Hosted: no sign-in

Inspect and test public configuration through a hosted service. This anonymous service is planned and is not released.

Read the current status

ConfigHub: sign in

Use ConfigHub when you want saved changes, releases, environments, and promotion.

Continue with the official tutorial

Public package and OCI pulls already work without registry login. The anonymous CI result records that local path.

Start with your own configuration

The same ConfigHub journey can start from other sources. Each path first gives you exact Kubernetes objects to inspect.

Helm chart and values

Render your chart and values without applying them. Compare the result with known catalog configurations.

Review Helm values

AICR

Inspect the selected components, allowed install settings, and generated Argo CD Applications.

Open the AICR example

OCI or Kubernetes YAML

Inspect the existing objects and record their source before you save or change them.

Choose an existing-config path

Need the complete Redis example?

The detailed walkthrough adds Helm parity, a live cluster, a major upgrade, ConfigHub promotion, two-cluster delivery, and rollback.

Open the detailed Redis walkthrough