Kubernetes and Helm are a common pairing in a modern DevOps stack. Here is how they fit together and a practical way to wire them up.
Where Kubernetes fits
Kubernetes is a container orchestrator: you declare the desired state of your workloads in YAML and controllers continuously reconcile the cluster toward it, handling scheduling, scaling, healing and networking.
apiVersion: apps/v1
kind: Deployment
metadata: { name: web }
spec:
replicas: 3
selector: { matchLabels: { app: web } }
template:
metadata: { labels: { app: web } }
spec:
containers:
- name: web
image: ghcr.io/acme/web:1.0
ports: [{ containerPort: 3000 }]
resources:
requests: { cpu: 100m, memory: 128Mi }
limits: { cpu: 500m, memory: 256Mi }
readinessProbe:
httpGet: { path: /healthz, port: 3000 }
---
apiVersion: v1
kind: Service
metadata: { name: web }
spec:
selector: { app: web }
ports: [{ port: 80, targetPort: 3000 }]Where Helm fits
Helm packages Kubernetes manifests into versioned, parameterized 'charts' so you can install, upgrade and roll back an entire application with a single command and a values file.
# templates/deployment.yaml
spec:
replicas: {{ .Values.replicaCount }}
template:
spec:
containers:
- name: {{ .Chart.Name }}
image: "{{ .Values.image.repo }}:{{ .Values.image.tag }}"
---
# values.yaml
replicaCount: 3
image:
repo: ghcr.io/acme/web
tag: "1.0"Making them work together
- Set requests/limits and use the HorizontalPodAutoscaler for elastic workloads
- Separate config (ConfigMap) from secrets and mount them, don't bake them in
- Pin dependency versions in Chart.yaml and commit Chart.lock
- Use --atomic and --wait so failed upgrades roll back automatically
Want this pairing set up properly, with docs and handover? That is exactly the kind of work CodeWizard's embedded senior engineers do - and both Kubernetes and Helm have active community groups you can join for free.