helm-ops
Skill4 starsChanged 5 months agoMITView on GitHub
Helm production operations — CLI usage for development/debug/emergency, release inspection, troubleshooting, OCI registry, hooks, values management, and GitOps integration (Flux HelmRelease, ArgoCD). **For production deploys, prefer GitOps over manual helm CLI.**
In this repository74 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlasSkill
- cert-managerSkill
- cilium-gatewaySkill
- cilium-networkSkill
- cnpgSkill
- dragonflySkill
- external-dnsSkill
- external-secretsSkill
- flaggerSkill
- fluxSkill
- gitea-apiSkill
- gitea-registrySkill
- gitea-runnerSkill
- giteaSkill
- gitea-teaSkill
- gitea-webhooksSkill
- harbor-apiSkill
- harbor-helmSkill
- harborSkill
- harbor-terraformSkill
- helm-chartSkill
- helmSkill
- higress-helmSkill
- higress-operatorSkill
- higressSkill
- kserve-helmSkill
- kserve-operatorSkill
- kserveSkill
- kubeflow-pipelinesSkill
- kubeflowSkill
- kubeflow-trainerSkill
- kubeflow-training-operatorSkill
- mariadb-helmSkill
- mariadb-operatorSkill
- mariadbSkill
- netbird-cliSkill
- netbird-operatorSkill
- netbird-serverSkill
- netbirdSkill
- netbird-terraformSkill
- nextcloud-apiSkill
- nextcloud-helmSkill
- nextcloudSkill
- nvidia-device-pluginSkill
- rook-ceph-operatorSkill
- rook-cephSkill
- rook-ceph-toolboxSkill
- sealed-secretsSkill
- stakater-reloaderSkill
- tailscaleSkill
- tailscale-talosSkill
- talosconfigSkill
- talosctlSkill
- talosSkill
- talos-terraformSkill
- tekton-operatorSkill
- tekton-pacSkill
- tekton-pipelinesSkill
- tektonSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 102
Run helm dependency update to resolve.
- Very specific: line 252
Manual Helm for production: Use Flux/ArgoCD. CLI is dev/debug/emergency only.
- Very specific: line 258
Uninstalling without
--keep-history: No way to recover release metadata.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Helm — Operations
For chart writing (templates, values, testing) see helm-chart.
⚠️ Production Reminder
helm install / helm upgrade is for dev, debug, and emergency only. Day-2 operations go through GitOps:
| Tool | Resource |
| Flux | HelmRelease (helm.toolkit.fluxcd.io/v2) |
| ArgoCD | Application with Helm source |
See GitOps Integration below.
Release Inspection & Troubleshooting
# List releases
helm list -n production # namespace
helm list -A # all namespaces
helm list -n production -a # include failed/uninstalled
helm list -n production --filter "myapp" # filter by name
helm list -n production --date --reverse # newest first
# Inspect release state
helm status myapp -n production # resources + notes
helm history myapp -n production # revision history
helm get values myapp -n production # current values
helm get values myapp -n production --revision 2 # specific revision
helm get manifest myapp -n production # rendered K8s manifests
helm get manifest myapp -n production --revision 2
helm get notes myapp -n production # install-time output
helm get hooks myapp -n production # hooks in release
helm get all myapp -n production # everything
# Compare revisions
diff <(helm get manifest myapp -n production --revision 2) \
<(helm get manifest myapp -n production --revision 3)
# Dry-run / debug
helm install myapp ./mychart --dry-run -f values-prod.yaml
helm upgrade myapp ./mychart --dry-run --server-side -f values-prod.yaml # Helm 4 SSA
helm template myapp ./mychart -f values.yaml > rendered.yaml # no cluster
helm template myapp ./mychart --show-only templates/deployment.yaml
helm install myapp ./mychart --debug -f values.yaml # full template debug output
# Inspect remote charts
helm show chart oci://ghcr.io/myorg/mychart --version 0.1.0
helm show values oci://ghcr.io/myorg/mychart --version 0.1.0
helm show readme oci://ghcr.io/myorg/mychart --version 0.1.0
helm show crds oci://ghcr.io/myorg/mychart --version 0.1.0
# Troubleshoot failed release
helm status myapp -n production # what's the status
helm history myapp -n production # find last good revision
helm get values myapp -n production --revision 5 # what values caused it
helm get manifest myapp -n production --revision 5 # what rendered
helm rollback myapp 4 -n production --cleanup-on-fail
helm lint ./mychart -f values-prod.yaml # local validationCommon statuses: deployed, failed, pending-install, pending-upgrade, pending-rollback, superseded, uninstalled.
Flux Equivalents
kubectl describe helmrelease myapp -n production
kubectl get helmrelease myapp -n production -o jsonpath='{.status.conditions}'
kubectl get secret -n production -l "name=myapp,owner=helm" # raw release data
helm status myapp -n production # works because Flux creates Helm releasesOCI Registry
Charts as OCI artifacts — no chart repo server. GA since Helm v3.12.
helm registry login ghcr.io -u <user> --password-stdin
helm package ./mychart && helm push mychart-0.1.0.tgz oci://ghcr.io/myorg
helm install myapp oci://ghcr.io/myorg/mychart --version 0.1.0
helm pull oci://ghcr.io/myorg/mychart --version 0.1.0 --untarSupported registries: GHCR, ECR, Docker Hub, Harbor, Gitea, GitLab.
Chart.yaml with OCI deps
dependencies:
- name: redis
version: "~17.0.0"
repository: oci://registry-1.docker.io/bitnamicharts
condition: redis.enabledRun helm dependency update to resolve.
Values Management
# Layered values — later files override earlier
helm template release . -f values.yaml -f values-prod.yamlLayered values merge/override. Array override replaces entirely (use --set for array element override).
Global Values
Flow down to subcharts. Parent globals override subchart globals.
global:
environment: production
imageRegistry: ghcr.io/myorg
# Accessed in subcharts: .Values.global.environmentHooks
Only during Helm-managed installs — does not work with helm template | kubectl apply or GitOps tools.
Hook Types
pre-install, post-install, pre-upgrade, post-upgrade, pre-rollback, post-rollback, pre-delete, post-delete, test.
apiVersion: batch/v1
kind: Job
metadata:
name: "{{ .Release.Name }}-migrate"
annotations:
"helm.sh/hook": pre-upgrade,pre-install
"helm.sh/hook-weight": "-5"
"helm.sh/hook-delete-policy": before-hook-creation,hook-succeeded
spec:
ttlSecondsAfterFinished: 600
template:
spec:
restartPolicy: Never
containers:
- name: migrate
image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
command: ["/app/bin/migrate"]Rules: restartPolicy: Never. Always set hook-delete-policy (prevents name collision on retry). Weight is string annotation, lower runs first.
GitOps alternative: ArgoCD sync-waves, init containers, PostRenderers.
GitOps Integration (Preferred)
Flux HelmRelease
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: myapp
namespace: production
spec:
interval: 10m
chart:
spec:
chart: mychart
version: ">=0.1.0 <1.0.0"
sourceRef:
kind: HelmRepository
name: my-charts
namespace: flux-system
values:
replicaCount: 3
image:
tag: v2.1.0
ingress:
enabled: true
hosts:
- host: app.example.com
paths:
- path: /
pathType: Prefix
upgrade:
remediation:
retries: 3
remediateLastFailure: true
rollback:
cleanupOnFail: true
driftDetection:
mode: enabledKey fields: chart.spec.version (SemVer range), values (inline, equivalent to -f), upgrade.remediation.retries, rollback.cleanupOnFail, driftDetection.mode.
ArgoCD Application
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: myapp
namespace: argocd
spec:
sources:
- repoURL: oci://ghcr.io/myorg/charts
chart: myapp
targetRevision: 0.1.0
helm:
valueFiles:
- $values/values-prod.yaml
- repoURL: https://github.com/myorg/config
targetRevision: main
ref: values
destination:
server: https://kubernetes.default.svc
namespace: production
syncPolicy:
automated:
prune: true
selfHeal: truePostRenderer (Last-Mile Patching)
For third-party charts missing values knobs:
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
spec:
chart:
spec:
chart: bitnami/nginx
postRenderers:
- kustomize:
patches:
- target:
kind: Deployment
patch:
- op: add
path: /spec/template/spec/containers/0/env/-
value:
name: EXTRA_VAR
value: "some-value"Common Ops Mistakes
- Manual Helm for production. Use Flux/ArgoCD. CLI is dev/debug/emergency only.
helm template | kubectl apply— Hooks don't run. No release tracking. No rollback.--setwith secrets in CI. Leaks in logs. Use-f secrets.yaml(encrypted via SOPS).- Helm 4 flags.
--atomic→--rollback-on-failure. Check CI scripts after upgrade. - Hook Jobs without
hook-delete-policy. Previous Job blocks retry with same name. - Array override via
--set.--setreplaces entire arrays, use-fwith YAML for precision. - Uninstalling without
--keep-history. No way to recover release metadata. Use-n <ns> --keep-historyif you might need to inspect later. - Rollback skips hooks by default.
helm rollback --recreate-podsdoesn't re-runpre/post-upgradehooks. Use--recreate-podscarefully.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

