Kubernetes Rolling Updates: Zero Downtime Deployment Quiz Quiz

1. Rolling Update Strategy

   Which Kubernetes Deployment strategy minimizes downtime during application updates by incrementally replacing old pods with new ones?

   1. A: Recreate
   2. B: RollingUpdate
   3. C: Canary
   4. D: BlueGreen
   5. E: The 'Update' strategy

2. Readiness Probe Importance

   Why is configuring a Readiness Probe essential for achieving zero-downtime deployments with Rolling Updates?

   1. A: It determines the number of replica sets to create.
   2. B: It ensures the Deployment uses the correct image.
   3. C: It verifies that a pod is ready to serve traffic before it's added to the service.
   4. D: It automatically scales the Deployment based on CPU usage.
   5. E: It restarts pods that fail liveness checks.

3. maxSurge Parameter

   What does the 'maxSurge' parameter in a Kubernetes Deployment's RollingUpdate strategy control?

   1. A: The maximum number of pods that can be unavailable during the update.
   2. B: The maximum time a new pod can take to become ready.
   3. C: The maximum number of pods that can be created beyond the desired number of replicas.
   4. D: The maximum number of old pods that can remain running during the update.
   5. E: The maximum percentage of old pods to keep during update

4. maxUnavailable Parameter

   What does the 'maxUnavailable' parameter in a Kubernetes Deployment's RollingUpdate strategy specify?

   1. A: The maximum number of new pods that must be available before scaling down old pods.
   2. B: The maximum percentage of time a pod is allowed to be unavailable.
   3. C: The maximum number of pods that can be unavailable during the update.
   4. D: The maximum number of unhealthy pods before the update is paused.
   5. E: The maximum number of pods that can be in the terminating state

5. Rolling Update Progress

   How can you monitor the progress of a Rolling Update in Kubernetes?

   1. A: By examining the Deployment's event logs using 'kubectl get events'.
   2. B: By directly checking the status of each pod with 'kubectl get pods'.
   3. C: By using 'kubectl rollout status deployment/u003Cdeployment-nameu003E'.
   4. D: All of the above.
   5. E: By tailing the logs of the kube-controller-manager.

6. Rolling Back Updates

   What command is used to rollback a failed Rolling Update to the previous revision in Kubernetes?

   1. A: kubectl undo deployment/u003Cdeployment-nameu003E
   2. B: kubectl revert deployment/u003Cdeployment-nameu003E
   3. C: kubectl rollback deployment/u003Cdeployment-nameu003E
   4. D: kubectl update deployment/u003Cdeployment-nameu003E --from-revision=PREVIOUS
   5. E: kubectl apply -f u003Cprevious-deployment-yamlu003E

7. Liveness Probe Impact

   How does a misconfigured Liveness Probe affect Rolling Updates?

   1. A: It can cause unnecessary pod restarts, slowing down the update.
   2. B: It prevents the deployment from scaling up.
   3. C: It has no impact on Rolling Updates.
   4. D: It directly influences the 'maxSurge' value.
   5. E: It causes the update to immediately fail.

8. Service Selectors During Update

   What happens to the Service's selector during a Rolling Update?

   1. A: The Service selector is updated to point to the new pods only after the update is complete.
   2. B: The Service selector is automatically updated to include both old and new pods as they become ready.
   3. C: The Service is temporarily unavailable during the update.
   4. D: A new Service is created for the updated pods, and the old Service is deleted.
   5. E: The Service selector is manually updated using 'kubectl edit service' during the Rolling Update.

9. Controlling Update Speed

   How can you fine-tune the speed and aggressiveness of a Rolling Update in Kubernetes?

   1. A: By adjusting the 'minReadySeconds' parameter in the Deployment spec.
   2. B: By modifying the 'maxSurge' and 'maxUnavailable' parameters in the Deployment spec.
   3. C: By using the 'kubectl scale' command to manually scale the Deployment during the update.
   4. D: Both A and B.
   5. E: The update speed cannot be controlled.

10. Interrupted Rolling Updates

    What happens if a Rolling Update is interrupted (e.g., due to a node failure)?

    1. A: The Rolling Update is automatically rolled back to the previous version.
    2. B: The Rolling Update pauses, and Kubernetes attempts to resume it when possible.
    3. C: The Deployment enters a failed state and must be manually restarted.
    4. D: All pods are immediately terminated and need to be re-created
    5. E: The deployment proceeds as if nothing happened