Skip to content
In this Guide

In this Guide

Deep Dives

AI: Claude and Codex patterns

ConfigHub: Deploy and manage

A Guide

Send a missing or broken public chart

The Catalog grows from the charts people ask for. If a public chart is missing, or its output differs from what Helm renders, send the chart and values that show it.

Prefer to do this with your AI agent?

1. Look for it in the Catalog

Search Configs for the chart. Each entry lists the versions it was tested at. If the entry is there and its output looks right, you have your answer.

2. Render it yourself, and note what differs

Render the chart as Helm does, with the values that show the problem. Then see what it installs. Use public values only, because the issue you send is public.

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.

# render the chart as Helm does
$ helm template <release> <chart> --version <version> --namespace <namespace> -f <values>.yaml > helm.yaml

# see what it would install
$ cub config check helm.yaml

# compare it with the objects you expected
$ cub config diff expected.yaml helm.yaml

3. Send the chart and values

Open the problem chart issue template. It asks for the public source, the exact version or digest, the values and choices you used, the result you expected, and the result you saw.

4. See what happens to it

Each case becomes a checked answer, a named refusal, or a documented limit. What happens to a public question explains how that is decided. Until then, the other paths for a chart the Catalog does not have still work.