MCP fails to drain the node due to Pod's Disruption Budget(PDB)

Solution Verified - Updated -

Issue

  • The node is stuck or not updated with the latest machine config because it can not be drained by the MachineConfigPool.
  • The affected node is hosting PODs governed by a Pod Disruption Budget, preventing the node from being drained by the MCP.

Environment

  • Red Hat OpenShift Container Platform
    • v4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content