Exam Professional Cloud Developer topic 1 question 224 discussion

By performing a rolling update with a PDB of 80%, you can ensure that at least 80% of the Pods are always available during the deployment. This will minimize the risk of downtime in case there are issues with the new revision.

https://kubernetes.io/docs/tasks/run-application/configure-pdb/#identify-an-application-to-protect

A rolling update with a PodDisruptionBudget (PDB) of 80% helps to minimize the risk of issues after deploying a new revision to a production environment in GKE. The PDB specifies the number of pods in a deployment that must remain available during an update, ensuring that there is sufficient capacity to handle any increase in traffic or demand. By setting a PDB of 80%, you ensure that at least 80% of the pods are available during the update, reducing the risk of disruption to your application. This is a recommended best practice by Google for deploying updates to production environments in GKE.

https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/ https://cloud.google.com/blog/products/containers-kubernetes/ensuring-reliability-and-uptime-for-your-gke-cluster Answer A

A is the answer. https://cloud.google.com/blog/products/containers-kubernetes/ensuring-reliability-and-uptime-for-your-gke-cluster Setting PodDisruptionBudget ensures that your workloads have a sufficient number of replicas, even during maintenance. Using the PDB, you can define a number (or percentage) of pods that can be terminated, even if terminating them brings the current replica count below the desired value. With PDB configured, Kubernetes will drain a node following the configured disruption schedule. New pods will be deployed on other available nodes. This approach ensures Kubernetes schedules workloads in an optimal way while controlling the disruption based on the PDB configuration.

https://blog.knoldus.com/how-to-avoid-outages-in-your-kubernetes-cluster-using-pdb/