Skip to content

Issues with Example Policy "Add Pod Disruption Budget" #1133

@abuechler

Description

@abuechler

I see several issues with that example policy:

  • 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."

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions