Drain with PodDisruptionBudget blocks
Issue
- if a customer does not specify the PodDisruptionBudget correctly, a cluster administrator is not able to drain the node for the OS updates.
- some cluster providers have no control on the business pods so it means that in production clusters they will not be able to automatically drain & upgrade the node for example until an action is taken on the business side (responsible of the pod).
- having both PodDisruptionBudget and replicas as 1, will lead to the situation that the drain" is blocked
Environment
- Red Hat OpenShift Container Platform (RHOCP) 4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.