helm-charts

# Skill: Helm Charts > **Expertise:** Helm 3 chart structure, values hierarchy, multi-environment overlays, chart testing, ArgoCD integration. ## When to load When creating a new Helm chart, reviewing an existing chart, setting up multi-env values, or integrating with ArgoCD. ## Chart Structure (Standard) ``` charts/my-service/ ├── Chart.yaml ├── values.yaml ← defaults (all envs inherit) ├── values-staging.yaml ← staging overrides ├── values-prod.yaml ← production overrides ├── templates/ │ ├── _helpers.tpl ← named templates │ ├── deployment.yaml │ ├── service.yaml │ ├── ingress.yaml │ ├── hpa.yaml │ ├── pdb.yaml │ ├── serviceaccount.yaml │ ├── networkpolicy.yaml │ └── NOTES.txt └── tests/ └── test-connection.yaml ``` ## values.yaml Conventions ```yaml # Always provide a complete, renderable default set replicaCount: 2 image: repository: registry.example.com/my-service tag: "" # overridden by CI with digest digest: "" # prefer digest over tag in prod pullPolicy: IfNotPresent serviceAccount: create: true name: "" # auto-generated from chart name if empty resources: requests: { cpu: 100m, memory: 128Mi } limits: { cpu: 500m, memory: 512Mi } autoscaling: enabled: true minReplicas: 2 maxReplicas: 10 targetCPUUtilizationPercentage: 70 ingress: enabled: false className: nginx hosts: [] tls: [] podDisruptionBudget: enabled: true minAvailable: 1 ``` #...