Exam Professional Cloud Developer topic 1 question 324 discussion

Pod Disruption Budgets (PDBs) are designed to control voluntary disruptions like node drains. Setting minAvailable: 10% ensures that at least 10% of Pods remain available during the drain process. This guarantees that after the drain, the application still has a minimum serving capacity of 10% — exactly what the question asks for. When you drain a node or perform a rolling update: Kubernetes checks the PDB before evicting Pods. If evicting a Pod would violate the PDB, the operation is paused until enough Pods are healthy. This is especially useful for stateless services like web frontends, where you want to maintain a minimum serving capacity. https://kubernetes.io/docs/tasks/run-application/configure-pdb/

A Pod Disruption Budget (PDB) is designed to maintain high availability during voluntary disruptions, like draining nodes for upgrades. By setting the minAvailable to 10%, you're specifying that at least 10% of your Pods must remain available during disruptions. This directly solves the issue of maintaining service availability while some Pods are being drained. So, C is the best option for addressing the specific requirement of ensuring high availability during node draining in a GKE cluster.

A Pod Disruption Budget (PDB) allows you to specify the minimum number or percentage of Pods that must be available during voluntary disruptions such as node drains during upgrades. By configuring a PDB with a minAvailable value of 10%, Kubernetes ensures that at least 10% of your application’s Pods remain available when nodes are being drained, thereby meeting your high-availability requirement.