Manage Helm values — override precedence, multi-env configs, --set, schema validation, secrets. Use when the user mentions Helm values, env-specific configs, or values.yaml.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Manage Helm values — override precedence, multi-env configs, --set, schema validation, secrets. Use when the user mentions Helm values, env-specific configs, or values.yaml.
user-invocable
false
allowed-tools
Bash, Read, Write, Edit, Grep, Glob
Helm Values Management
Comprehensive guidance for managing Helm values across environments, understanding override precedence, and advanced configuration strategies.
When to Use This Skill
Use this skill when...
Use instead when...
Designing per-environment values files (dev/staging/prod) and override precedence
Use helm-release-management when the focus is the install/upgrade command itself rather than values shape
Reasoning about --set, --set-string, --values, and --reuse-values behaviour
Use helm-debugging when values rendering produces wrong YAML or value type errors
Adding values schema validation or secret-injection patterns
Use helm-chart-development when the values schema lives inside a chart you are authoring
When to Use
Use this skill automatically when:
User needs to configure Helm deployments with custom values
User mentions environment-specific configurations (dev/staging/prod)
User asks about value override precedence or merging
User needs to manage secrets or sensitive configuration
User wants to understand what values were deployed
User needs to validate or inspect values
Value Override Precedence
Values are merged with right-most precedence (last wins):
# Show chart default values
helm show values <chart>
# Show values from specific chart version
helm show values <chart> --version 1.2.3
# Save defaults to file
helm show values bitnami/nginx > default-values.yaml
View Deployed Values
# Get values used in deployed release
helm get values <release> --namespace <namespace>
# Get ALL values (including defaults)
helm get values <release> --namespace <namespace> --all
# Get values in different formats
helm get values <release> -n <namespace> -o json
# Get values from specific revision
helm get values <release> -n <namespace> --revision 2
Set Values During Install/Upgrade
# Using values file
helm install myapp ./chart \
--namespace prod \
--values values.yaml
# Using multiple values files (right-most wins)
helm install myapp ./chart \
--namespace prod \
-f values/base.yaml \
-f values/production.yaml
# Using --set for individual values
helm install myapp ./chart \
--namespace prod \
--set replicaCount=3 \
--set image.tag=v2.0.0
# Using --set-string to force string type
helm install myapp ./chart \
--namespace prod \
--set-string version="1.0"# Using --set-json for complex structures
helm install myapp ./chart \
--namespace prod \
--set-json 'nodeSelector={"disktype":"ssd","region":"us-west"}'# Using --set-file to read value from file
helm install myapp ./chart \
--namespace prod \
--set-file tlsCert=./certs/tls.crt
# Shared configuration across all environmentsapp:name:myapplabels:team:platformcomponent:apiservice:type:ClusterIPport:8080ingress:enabled:trueclassName:nginxannotations:cert-manager.io/cluster-issuer:letsencryptresources:requests:cpu:100mmemory:128Mi
# Stringname:myapptag:"v1.0.0"# Quote to ensure string# NumberreplicaCount:3port:8080# Booleanenabled:truedebug:false# Nulldatabase:null
Nested Values
# Nested objectsimage:repository:nginxtag:"1.21.0"pullPolicy:IfNotPresent# Access in template: {{ .Values.image.repository }}
Lists/Arrays
# Simple listtags:-api-web-production# List of objectsenv:-name:DATABASE_URLvalue:postgres://db:5432/myapp-name:REDIS_URLvalue:redis://cache:6379
Setting Values via CLI
# Simple value
--set name=myapp
# Nested value (use dot notation)
--set image.tag=v2.0.0
--set ingress.annotations."cert-manager\.io/cluster-issuer"=letsencrypt
# List values (use array index or {})
--set tags={api,web,prod}
# Complex JSON structures
--set-json 'nodeSelector={"disk":"ssd","region":"us-west"}'# Force string (prevents numeric conversion)
--set-string version="1.0"# Read value from file
--set-file cert=./tls.crt
Value Validation & Testing
Template with Values
# Render templates with values
helm template myapp ./chart --values values.yaml
# Validate against Kubernetes API
helm install myapp ./chart \
--values values.yaml \
--dry-run --validate
Check Computed Values
# See what values will be used (before install)
helm template myapp ./chart \
--values values.yaml \
--debug 2>&1 | grep -A 100 "COMPUTED VALUES"# See what values were used (after install)
helm get values myapp --namespace prod --all
Test Different Value Combinations
# Test with minimal values
helm template myapp ./chart --set image.tag=test# Test with full production values
helm template myapp ./chart \
-f values/common.yaml \
-f values/production.yaml
For detailed environment value examples, schema validation JSON, secret management options, template value handling patterns, best practices, and troubleshooting, see REFERENCE.md.
