Course outline▾
Week 1 · Bare-Metal Infrastructure & Advanced Containerization
- Day 1The AI Infrastructure Shift — Why the Model is Only 10% of the Production System
- Day 2Advanced Docker for AI — Multi-Stage Builds for Heavy Python Runtimes
- Day 3Hardware Acceleration in Docker — GPU Passthrough and Limits for Constrained Hardware
- Day 4Optimizing Model Weights — Quantization Basics (GGUF, AWQ) for Efficient Inference
- Day 5Local AI Runtimes — Deploying Ollama and vLLM for Bare-Metal Execution
- Day 6Containerizing AI Microservices — Building and Packaging APIs with FastAPI
- Day 7Docker Compose — Architecting a Multi-Container Database and Inference Stack Locally
Week 2 · Kubernetes Foundation for MLOps
- Day 8K3d and Lightweight Kubernetes — Running Multi-Node Clusters on 16 GB of RAM
- Day 9Kubernetes Core for Machine Learning — Pods, Deployments and Headless Services
- Day 10Persistent Volumes (PV/PVC) — Managing Heavy Model Weights and Vector Stores
- Day 11StatefulSets for Vector Databases — Deploying Milvus or Qdrant in Kubernetes
- Day 12Auto-Scaling AI Inference — Using Horizontal Pod Autoscalers for Spiky API Traffic
- Day 13Helm Charts — Packaging, Versioning and Updating AI Deployments
- Day 14Week 2 Capstone: Deploying a Highly Available Local AI Application on K3d
Week 3 · High-Performance Networking & Security Mesh
- Day 15AI Network Bottlenecks: Transitioning from iptables to eBPF
- Day 16Cilium & eBPF: Sub-Millisecond Routing for Heavy AI Microservices
- Day 17Service Mesh 101: Installing Istio over Your Local Cluster
- Day 18Envoy Proxy as an AI Gateway: Load Balancing and Terminating LLM Prompts
- Day 19Zero-Trust mTLS: Encrypting Traffic Between Autonomous Agents
- Day 20API Rate Limiting & Egress Control: Preventing Agents from Exfiltrating Data
- Day 21Distributed Tracing: Debugging Agent Workflows with Jaeger and OpenTelemetry
Week 4 · Enterprise Agents & CI/CD Workflows
- Day 22Introduction to MLOps: Bridging AI Development with Continuous Integration
- Day 23GitOps with ArgoCD: Automated, Self-Healing AI Deployments
- Day 24Building Ephemeral AI Sandboxes: Secure Execution Environments for Agent Code
- Day 25Multi-Agent Orchestration Frameworks: Exploring Mastra, LangGraph, and CrewAI
- Day 26Tool-Calling in Production: Connecting Agents Securely to Internal Databases
- Day 27MLOps Guardrails: Evaluating Agents and Preventing Hallucinations in Real-Time
- Day 28Continuous Training Pipelines: Connecting Data Ingestion to Automated Model Retraining
- Day 29Managing Technical Debt and Infrastructure Drift in Enterprise AI
- Day 30The AI-Native Platform: Scaling from a Sandbox Environment to Global Cloud Architecture
Day 13: Helm Charts — Packaging, Versioning and Updating AI Deployments
2026-11-19 · 7 min read
A real AI stack has dozens of manifests across development, staging and production. Copied by hand, they drift: someone fixes staging, forgets production, and nobody knows which version is the truth. Helm bundles the manifests into a versioned, parameterised chart, so you roll out and roll back with a single command.
Chart layout
Chart.yamlholds the chart name and a SemVer version.values.yamlholds defaults for every setting.values-staging.yamlandvalues-prod.yamloverride only what differs, such as RAM or replica counts.templates/holds the Kubernetes manifests, written as templates.
Values and templates
# values.yaml
global:
environment: production
namespace: ai-platform
inferenceEngine:
modelName: gemma-2-2b-it-awq
image: vllm/vllm-openai:v0.5.0
replicas: 2
quantization: awq
contextLength: 4096
gpuMemoryUtilization: 0.85
resources:
requests: { cpu: "2", memory: 4Gi }
limits: { cpu: "4", memory: 8Gi }
vectorDatabase:
image: qdrant/qdrant:v1.9.0
replicas: 3
storageSize: 20Gi
storageClass: local-storage
autoscaling:
enabled: true
minReplicas: 1
maxReplicas: 4
targetQueueDepth: 10
# templates/deployment-llm.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ .Release.Name }}-llm
namespace: {{ .Values.global.namespace }}
spec:
replicas: {{ .Values.inferenceEngine.replicas }}
selector:
matchLabels: { app: {{ .Release.Name }}-llm }
template:
metadata:
labels: { app: {{ .Release.Name }}-llm }
spec:
containers:
- name: vllm
image: {{ .Values.inferenceEngine.image }}
args:
- --model=/models/{{ .Values.inferenceEngine.modelName }}
- --quantization={{ .Values.inferenceEngine.quantization }}
- --max-model-len={{ .Values.inferenceEngine.contextLength }}
resources:
{{- toYaml .Values.inferenceEngine.resources | nindent 12 }}
Helm merges your values into the templates to produce plain Kubernetes YAML. Preview the result before you apply it with helm template, or --dry-run --debug.
Releases and rollbacks
helm lint ./helm-ai-stack
helm install local-ai ./helm-ai-stack --dry-run --debug
helm upgrade --install local-ai ./helm-ai-stack -f ./helm-ai-stack/values-staging.yaml
helm history local-ai
helm rollback local-ai 1
Each install or upgrade creates a numbered revision, and helm rollback returns to an earlier one in a single step. Version the chart in Git, keep image tags pinned and use one values file per environment, and your deployments become reviewable, repeatable and reversible.
Run it yourself
This is the exact example from the video. Real helm lint and helm template on a small chart. The template is trimmed from the lesson's version to fit.
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ .Release.Name }}-llm
spec:
replicas: {{ .Values.inferenceEngine.replicas }}
selector:
matchLabels: { app: {{ .Release.Name }}-llm }
template:
metadata:
labels: { app: {{ .Release.Name }}-llm }
spec:
containers:
- name: vllm
image: {{ .Values.inferenceEngine.image }}
args:
- --quantization={{ .Values.inferenceEngine.quantization }}
Helper file Chart.yaml, used by the run:
apiVersion: v2
name: helm-ai-stack
version: 0.1.0
Helper file values.yaml, used by the run:
inferenceEngine:
image: vllm/vllm-openai:v0.5.0
replicas: 2
quantization: awq
Helper file values-staging.yaml, used by the run:
inferenceEngine:
replicas: 1
Run it:
helm template local-ai . -f values-staging.yaml
Output I got while recording the video:
1 chart(s) linted, 0 chart(s) failed
name: local-ai-llm
replicas: 1
image: vllm/vllm-openai:v0.5.0
- --quantization=awq
Coming Up Next
Day 14: Week 2 capstone: deploying a highly available local AI application on K3d.
#Helm #Kubernetes #InfrastructureAsCode #DevOps #CICD #PlatformEngineering #ReleaseManagement