Resolving the 0/10 nodes are available - node(s) had untolerated taint error

Issue descriptionIssue description

When launching a pod in your Managed Service for Kubernetes cluster, you see this error:

0/10 nodes are available: X node(s) had untolerated taint

Where X is the number of Managed Service for Kubernetes cluster's affected nodes.

SolutionSolution

This error occurs when a node in the cluster is labeled as taint, which is incompatible with the requirements of the apps scheduled to run on it. A taint is a node label that means that certain pods cannot be scheduled on that node unless they meet specific conditions.

To resolve this issue, you can either modify the node label so that the pods are allowed to run on it, or update the pod settings to match the node label.

Additionally, we recommend reviewing the pod's tolerations and verifying the node's nodeSelector or nodeAffinity settings. Also, check your Managed Service for Kubernetes quotas and resource limits to make sure your nodes have sufficient resources available.

If the issue persistsIf the issue persists

If the above actions did not help, create a support ticket. When creating a ticket, provide the following information:

1. Managed Service for Kubernetes cluster ID.
2. Managed Service for Kubernetes cluster event log: kubectl get events output.
3. Cluster node specification: kubectl describe node $NODE_NAME output, where $NODE_NAME is the affected node name.
4. Specifications of all affected pods in your cluster: kubectl describe node $POD_NAME output for each of those pods, where $POD_NAME is the pod name.