Helm Quick Reference
Download This Cheat Sheet
Enter your email to download the PDF for free.
About This Cheat Sheet
Helm Quick Reference is a compact 1-2 page quick reference designed to live next to your keyboard or pinned to your monitor. It is intentionally dense — every line is a command, flag, or pattern you will actually reach for.
Helm Quick Reference covers Kubernetes — the de-facto standard for orchestrating containerised workloads at scale, used by every major cloud provider and most Fortune 500 engineering teams. It is written for platform engineers, SREs, DevOps practitioners, and developers deploying to managed clusters (EKS, GKE, AKS, OpenShift) who need accurate, working syntax without wading through documentation. This particular sheet zooms in on Helm — the parts of Kubernetes that come up most often in real work. A 1-page quick reference for Helm: chart management (install, upgrade, rollback), repository commands, template rendering, debugging, and Go template syntax for Kubernetes. Essential for Kubernetes teams managing application deployments. Covers chart creation, values templating, repository management, release lifecycle, hooks, and best practices for packaging and deploying applications on Kubernetes.
Every command, flag, and pattern in this sheet has been validated against current stable releases as of 2026. Where syntax differs between distributions, versions, or platforms, both forms are shown so you can copy-paste safely regardless of the environment you are working in. The PDF is print-ready in both A4 and US Letter formats and remains free to download forever.
What's Inside the PDF
- Helm — the practical commands and patterns you actually use in production Kubernetes work.
- Most-used commands grouped by task, not alphabetically, so you find what you need by intent.
- Common flag combinations with one-line comments explaining what each option actually does.
- Real-world examples that show inputs and expected outputs, not contrived hello-world snippets.
- Edge cases and gotchas that the official documentation buries on page 47.
- Print-friendly layout that works equally well on screen and on paper next to your monitor.
When to Use This Cheat Sheet
- 1Diagnosing a Pod stuck in `CrashLoopBackOff`, `ImagePullBackOff`, or `Pending` where rapid `kubectl` recall is the difference between minutes and hours of downtime.
- 2Writing production-grade YAML manifests for Deployments, Services, Ingresses, ConfigMaps, Secrets, and RBAC rules.
- 3Performing rolling updates, rollbacks, and canary deploys safely without dropping live traffic.
- 4Preparing for the CKA (Certified Kubernetes Administrator) or CKAD exam where command speed and YAML fluency are scored.
- 5Migrating workloads from VM-based or bare-metal infrastructure to a managed Kubernetes platform.
Key Concepts to Master
Pods
A Pod is the smallest deployable unit — one or more containers sharing network and storage. You almost always create Pods indirectly through a controller (Deployment, StatefulSet, DaemonSet, Job).
Services and networking
Pods are ephemeral and get new IPs on restart. A Service provides a stable virtual IP and DNS name, load-balancing across the Pods it selects.
Labels and selectors
Labels are arbitrary key=value tags on objects. Selectors let Services, Deployments, NetworkPolicies, and HPAs target groups of Pods declaratively without referencing them by name.
Namespaces and RBAC
Namespaces partition cluster resources. Combined with Roles, RoleBindings, ClusterRoles, and ServiceAccounts, they form the security boundary for multi-tenant clusters.
Declarative state
You describe the desired state in YAML; the control plane continuously reconciles actual state to match. This is why `kubectl apply -f` is preferred over imperative `create`/`edit` in production.
Pro Tips from Practitioners
- Always run `kubectl --dry-run=client -o yaml` to preview generated manifests before applying — it doubles as a fast YAML scaffolding tool.
- Set `kubectl alias k=kubectl` and source bash/zsh completion. Typing speed compounds when you run hundreds of commands daily.
- Use `kubectl explain <resource>.<field>` for schema-correct YAML. It is faster than searching documentation and always matches your cluster version.
- Prefer `kubectl rollout status` and `kubectl rollout undo` over manually deleting pods during upgrades — they preserve audit history.
- Use `--context` and `--namespace` flags or `kubectx`/`kubens` to avoid the classic mistake of running `kubectl delete` against the wrong cluster.
Related Books for Deeper Learning
More Cheat Sheets
Interactive Linux Commands Reference
Explore 232+ commands with syntax, examples, options, and pro tips.
Frequently Asked Questions
What is the Helm Quick Reference?
The Helm Quick Reference is a free, professionally designed PDF reference covering Kubernetes. It is curated by practitioners and validated against current stable releases as of 2026.
Is this enough to learn Kubernetes from scratch?
No — this is a quick reference for people who already know the basics. If you are new to Kubernetes, start with our Beginner's Complete Guide in the same series, then return here for daily lookups.
Do I need to memorise every kubectl command?
No. Memorise the verbs (`get`, `describe`, `apply`, `delete`, `logs`, `exec`, `rollout`) and let `kubectl explain` and shell completion fill in the rest. Speed comes from patterns, not memorisation.
Will these commands work on EKS, GKE, and AKS?
Yes. `kubectl` is identical across managed clusters. Cloud-specific tooling (`eksctl`, `gcloud`, `az aks`) only handles cluster lifecycle and IAM integration — workload commands are universal.
How do I avoid accidentally destroying production?
Use distinct kubeconfig contexts per environment, set a coloured prompt that shows the current context (e.g. `kube-ps1`), and gate destructive operations behind GitOps tools like Argo CD or Flux instead of direct `kubectl` access.
What is the relationship between Pods, ReplicaSets, and Deployments?
A Deployment manages a ReplicaSet, which manages Pods. You write Deployments; the controller handles ReplicaSet rollouts during updates so you get zero-downtime upgrades automatically.
Is this cheat sheet really free?
Yes, completely free. We ask for your email so we can let you know when new cheat sheets are released and to keep our spam-detection systems happy. You can unsubscribe in one click at any time.
Can I print and share this cheat sheet?
Yes — print it, pin it to your wall, share it with your team, hand it out at meetups. The only thing we ask is that you do not strip the Dargslan attribution or republish the PDF as your own work.