How to Process Pod Eviction and Rebuilding Caused by Node NotReady in a More Refined Manner about kubernetes

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[maxin93]

/sig node

[maxin93]

I have an idea that kube-controller-manager checks whether there is a normal worker node before evicting the pod when determining that the node is NotReady. If there is no normal worker node, the eviction operation is not performed. Of course, the number of active nodes can be configured, and the node type can also be set, for example, including nodes with specified labels.

[AnishShah]

sig-node meeting triage:

• This does not seem to be related to sig/node. We have a support forum - http://discuss.kubernetes.io where you can ask this question. You can explore service mesh to mitigate such issues.

/remove-sig node

[AnishShah]

sig-node triage:

/remove-kind bug
/kind support
/close

[k8s-ci-robot]

@AnishShah: Closing this issue.

In response to this:

sig-node triage:

/remove-kind bug
/kind support
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.