Kubernetes Deployments — Animate | AI Wisdom

← Back to topic
🎞 ANIMATE · Mode 3 of 5 · +100 XP— Kubernetes Deployments
📋Spec
⚙️RollingUpdate
🔄Resources
✅Probes
🎯 Next: Test →
Step 1 / 4
Speed
Deployment Spec
Deployment manages 3 replica pods — self-healing if any pod crashes💡 Analogy
Like a restaurant with a "always have 3 cooks" policy — if one leaves, immediately hire another.
Deployment ensures N replicas are always running. If a pod crashes, Kubernetes creates a replacement. selector.matchLabels tells Deployment which pods it owns.
Console Output
> Deployment: 3 replicas desired
> ReplicaSet: managing 3 pods
> Pod crash → new pod created in ~5s
●deployment.yaml
Deployment SpecL7–15
1apiVersion: apps/v1
2kind: Deployment
3metadata:
4  name: myapp
5  labels:
6    app: myapp
7spec:
8  replicas: 3
9  selector:
10    matchLabels:
11      app: myapp
12  strategy:
13    type: RollingUpdate
14    rollingUpdate:
15      maxUnavailable: 1      # at most 1 pod down at a time
16      maxSurge: 1            # at most 1 extra pod during update
17  template:
18    metadata:
19      labels:
20        app: myapp
21    spec:
22      containers:
23        - name: myapp
24          image: ghcr.io/myorg/myapp:1.5.0
25          ports:
26            - containerPort: 3000
27          resources:
28            requests: { cpu: 100m, memory: 128Mi }
29            limits:   { cpu: 500m, memory: 512Mi }
30          readinessProbe:
31            httpGet: { path: /health, port: 3000 }
32            initialDelaySeconds: 5
33            periodSeconds: 10
34          livenessProbe:
35            httpGet: { path: /health, port: 3000 }
36            failureThreshold: 3
37            periodSeconds: 30
37 lines
Timeline — 4 Steps
Deployment Spec
Deployment manages 3 replica pods — self-healing if any pod crashes💡 Analogy
Like a restaurant with a "always have 3 cooks" policy — if one leaves, immediately hire another.
Deployment ensures N replicas are always running. If a pod crashes, Kubernetes creates a replacement. selector.matchLabels tells Deployment which pods it owns.
Console Output
> Deployment: 3 replicas desired
> ReplicaSet: managing 3 pods
> Pod crash → new pod created in ~5s

Was this page helpful?

Discussion

Deployment manages 3 replica pods — self-healing if any pod crashes

💡 Analogy

Like a restaurant with a "always have 3 cooks" policy — if one leaves, immediately hire another.

Deployment ensures N replicas are always running. If a pod crashes, Kubernetes creates a replacement. selector.matchLabels tells Deployment which pods it owns.

Console Output

> Deployment: 3 replicas desired
> ReplicaSet: managing 3 pods
> Pod crash → new pod created in ~5s

Deployment manages 3 replica pods — self-healing if any pod crashes

💡 Analogy

Like a restaurant with a "always have 3 cooks" policy — if one leaves, immediately hire another.

Deployment ensures N replicas are always running. If a pod crashes, Kubernetes creates a replacement. selector.matchLabels tells Deployment which pods it owns.

Console Output

> Deployment: 3 replicas desired
> ReplicaSet: managing 3 pods
> Pod crash → new pod created in ~5s