Checkpoint: Kubernetes Core

Question 1 of 5

• The Deployment controller creates a new ReplicaSet for the same template, which creates 3 Pods again.
• The Deployment is deleted too, because it owned the ReplicaSet.
• The Pods keep running without an owner forever.
• Nothing, because ReplicaSets can’t be deleted directly.

Question 2 of 5

• http://notes-api (port 80)
• http://notes-api.notes (port 80), or the full notes-api.notes.svc.cluster.local
• http://notes:3000
• http://localhost:80 with a NodePort

Question 3 of 5

• The image tag was bumped.
• The Service type changed from ClusterIP to LoadBalancer.
• The Pod template’s labels changed and no longer match the Service’s selector.
• The ConfigMap was updated.

Question 4 of 5

• Secrets are cached for 24 hours; wait for the cache to expire.
• The Secret must be deleted and recreated, not updated.
• The Deployment’s selector must be changed to pick up the new Secret.
• Environment variables are read at container start, so running Pods still use the old value; run kubectl rollout restart deployment/notes-api.

Question 5 of 5

• To see exactly which fields on the live cluster will change, catching surprises such as resetting an emergency scale-up.
• Because apply fails unless diff ran first.
• To validate YAML syntax only.
• To download the current manifests into the k8s/ folder.