You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
what if there is already an existing PDB? => precondition for the rule
what if the user creates a deployment and then afterwards creates a PDB, the default one should be deleted => the policy should also listen on PDB creation/deletion/etc
what if the number of replicas is set to 1, then the minAvailable: 1 will block pod eviction for no reason => precondition for the rule
Also notable is that draining nodes with pods that are covered by more than one PDB will give you (at least on GKE) following error: "This pod has more than one PodDisruptionBudget, which the eviction subresource does not support."
The text was updated successfully, but these errors were encountered:
I see several issues with that example policy:
Also notable is that draining nodes with pods that are covered by more than one PDB will give you (at least on GKE) following error: "This pod has more than one PodDisruptionBudget, which the eviction subresource does not support."
The text was updated successfully, but these errors were encountered: