Default namespace = current kubectl context unless -n is set
Inspecting charts before install
# Show default values (essential before overriding)
helm show values jenkinsci/jenkins
helm show values jenkinsci/jenkins --version4.6.4
# Show chart metadata
helm show chart jenkinsci/jenkins
# Show rendered templates without installing
helm template my-jenkins jenkinsci/jenkins --values my-values.yaml
Inspecting installed releases
# What values are currently set on a release
helm get values my-jenkins
# All values including defaults
helm get values my-jenkins --all# Get the rendered manifest of a deployed release
helm get manifest my-jenkins
Overrides
--set key=value: CLI
--set a=b,c=d: multiple CLI values
--values values.yaml / -f: file
-n <ns> --create-namespace: target namespace
helm install api bitnami/nginx --setreplicaCount=2,service.type=ClusterIP
helm upgrade api bitnami/nginx --reuse-values --setimage.tag=1.25
helm diff upgrade api bitnami/nginx -f values.yaml # if plugin exists
Exam tips
Fresh Helm has no repos: must helm repo add first
Chart name format: <repo>/<chart> (e.g. jenkinsci/jenkins)
helm install creates many K8s objects: verify with kubectl get
Use helm show values before --set to know the correct key names
helm get values shows only user-supplied overrides; add --all for full picture
In 2026 feedback, Helm showed up mostly as values overrides and upgrades, not chart authoring