| name | helm-chart-vendor |
| description | Pull a Helm chart from a repo (or OCI) at a specific version and save it under helm/<group>/ with a versioned directory name. Use when adding or upgrading a vendored Helm chart, when the user asks to vendor a chart, or when following the repo's "add chart to helm/" workflow. |
Helm Chart Vendor
Language: Always communicate with the user in their language. If the user writes in Korean, respond in Korean; if in English, respond in English.
Pull a Helm chart from an external repo (or OCI) at a specific version and store it under helm/<group>/<chart-name>-<version>/. Used to pin versions for reproducible deployments.
Group folder
- Path:
helm/<group>/
- Group name: 1st priority = name used in this repo (e.g. app/family name); 2nd = official Helm repo name.
- A group can contain charts from multiple providers (e.g.
cert-manager: controller from jetstack, issuers from adfinis). Group and provider are tracked separately; they may be the same (one provider per group) or different (one group, multiple providers).
- Example: ARC charts from
actions-runner-controller repo are grouped as github-actions-runner-controller (repo app name).
Chart directory name
- Format:
<original-chart-name>-<version> (no group prefix; the group folder already identifies the family).
- Examples:
gha-runner-scale-set-controller-0.13.1, open-webui-12.5.0.
Workflow
-
Update repos (optional, when you need the latest index)
helm repo update
-
Determine group and provider
Group = folder under helm/ (e.g. app/family name; can aggregate multiple providers). Provider = Helm repo name for helm pull. See helm/README.md in this repo for the canonical list of groups and providers (Group | Provider | URL). Create helm/<group>/ if it does not exist.
-
List available versions
- Helm repo:
helm search repo <repo-name>/<chart-name> --versions
- OCI:
helm show chart oci://<registry>/<path> or check registry/release notes for versions.
-
Download and untar
-
Rename and place under group
mv <chart-name>/ <chart-name>-<version>/
mv <chart-name>-<version>/ helm/<group>/
Run from project root. If already in helm/, use mv <chart-name>-<version>/ ../<group>/ or equivalent.
-
Patch for extraResources
Immediately after placing the chart, execute the helm-extraresources-patcher skill on the new chart directory to ensure it supports custom resource injection.
-
Diff values.yaml and confirm with user (upgrade only)
When upgrading from a previous version (old chart dir exists), compare values.yaml between the two versions and present a structured report before touching any ArgoCD Application manifest.
7a. Diff command
Compare meaningful lines (strip comments and blanks for signal-to-noise):
diff <(grep -v "^#\|^$" helm/<group>/<old-chart>/values.yaml) \
<(grep -v "^#\|^$" helm/<group>/<new-chart>/values.yaml)
Also diff Chart.yaml for dependency version changes.
7b. Categorize changes
Classify every diff line into one of these categories:
| Category | What it means | Action |
|---|
| Removed field | Key existed in old, gone in new | Check if ArgoCD app sets this key — if yes, flag as ⚠️ breaking |
| Default changed | Key exists in both, value differs | Note old→new; check if our override supersedes it |
| New field | Key added in new chart | Note with its default; usually safe |
| Dependency bump | charts/ subchart version changed | Note version delta; rarely breaking |
7c. Cross-reference with ArgoCD Application overrides
Read the relevant clusters/*/apps/<app>.yaml and extract all keys under valuesObject. For each changed or removed field, determine:
- Overridden by us → our value takes precedence, upstream default change is irrelevant
- Not overridden → upstream default change applies to our deployment
7d. Present report and ask for confirmation
Present a concise table to the user before editing any ArgoCD manifest:
## Chart upgrade: <app> <old-version> → <new-version>
### ⚠️ Removed fields
| Field | Our override? | Impact |
...
### 🔄 Default changes
| Field | Old default | New default | Our override | Impact |
...
### ✨ New fields
| Field | Default | Notes |
...
Then ask the user to confirm they have reviewed the changes and whether to proceed with updating the ArgoCD Application manifest.
Do not proceed to update the ArgoCD Application manifest until the user explicitly confirms.
Convention summary
- Storage path:
helm/<group>/<chart-name>-<version>/
- Group: folder name (app/family); can be shared by multiple providers (see
helm/README.md).
- Provider: Helm repo used for
helm pull; same as group when one repo per family, or distinct (e.g. cert-manager: jetstack + adfinis).
- Chart dir: original chart name +
-<version> only.
Example (Helm repo)
cd helm
helm repo update
helm search repo open-webui/open-webui --versions
helm pull open-webui/open-webui --untar --version 12.5.0
mv open-webui/ open-webui-12.5.0
mkdir -p open-webui
mv open-webui-12.5.0 open-webui/
App path: helm/open-webui/open-webui-12.5.0
Example (grouped + OCI)
cd helm
mkdir -p github-actions-runner-controller
helm pull oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set-controller --untar --version 0.13.1
mv gha-runner-scale-set-controller gha-runner-scale-set-controller-0.13.1
mv gha-runner-scale-set-controller-0.13.1 github-actions-runner-controller/
App path: helm/github-actions-runner-controller/gha-runner-scale-set-controller-0.13.1
Argo CD or Helm apps reference helm/<group>/<chart-name>-<version> as the chart path.
Group and provider
The canonical list of Group | Provider | URL is maintained in helm/README.md in this repo. When determining group/provider or adding a new chart, refer to that file.
