Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Match unreachable taint key without comparing effect
Problem: Till k8s 1.18.10, the k8s node lifecycle controller sets these two taints on an unreachable node (or a node with Ready=Unknown): `node.kubernetes.io/unreachable:NoSchedule` and `node.kubernetes.io/unreachable:NoExecute`. In k8s 1.19.3, the node controller is only setting the taint with NoSchedule effect for such a node. The nodepool controller checks for the presence of a taint with key `node.kubernetes.io/unreachable` and effect `NoExecute` when determining if a node is unreachable and needs to be replaced. Since the node in 1.19 does not get this taint, nodepool controller does not consider it as unreachable. Solution: Modify the check in nodepool controller to consider a node unreachable even if only the taint key matches `node.kubernetes.io/unreachable`. The taint effect should not impact how nodepool processes this node.
- Loading branch information