Newly added node is stuck with `node.cloudprovider.kubernetes.io/uninitialized` taint on Azure IPI cluster

Solution Verified - Updated -

Issue

  • When machine set adds a new infra node in Azure IPI cluster, the new node which is added to the cluster is added with uninitialized taint as shown:
- effect: NoSchedule
    key: node.cloudprovider.kubernetes.io/uninitialized
    value: "true"

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.14.z
  • Azure IPI

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