Checkpoint: Running in Production

Question 1 of 5

• All Pods restart repeatedly until Postgres returns.
• Kubernetes reschedules the Pods to other nodes.
• All Pods become not ready and leave the Service’s endpoints; they rejoin without restarting when Postgres is back.
• Nothing, because probes are paused when a dependency is down.

Question 2 of 5

• It’s scheduled there, because actual usage is low.
• It’s scheduled there and other Pods are throttled to make room.
• It’s scheduled with a reduced request of 200m.
• It isn’t scheduled on that node, because only 200m of requestable CPU is left; it goes elsewhere or stays Pending.

Question 3 of 5

• Users are getting errors from the 1.6.0 Pod.
• The old 1.5.x Pods are still serving at full capacity; the rollout is stuck and needs an undo or a fix.
• Kubernetes has already rolled back to the previous version.
• The Deployment has scaled to zero.

Question 4 of 5

• The Gateway’s listener allowedRoutes doesn’t permit routes from the notes namespace.
• The notes-api Service has no endpoints.
• The HTTPRoute uses apiVersion: gateway.networking.k8s.io/v1.
• The Pods are missing a readiness probe.

Question 5 of 5

• kubectl logs <pod> --previous
• kubectl port-forward pod/<pod> 3000:3000 followed by kubectl events
• kubectl debug -it <pod> --image=busybox:1.37 --target=api, then wget -qO- localhost:3000/healthz
• kubectl describe node