supprot NoExecute taint

[learner0810]

Please provide an in-depth description of the question you have:

What do you think about this question?:

I think add t.Effect == corev1.TaintEffectNoExecute, this function is ok. why add todo,please give me some hints

Environment:

• Karmada version:
• Kubernetes version:
• Others:

[Garrybest]

/assign @mrlihanbo

[mrlihanbo]

Hi, @learner0810, the available taints in kubernetes are:
NoSchedule: Pods that do not tolerate this taint are not scheduled on the node.
NoExecute: Pod is evicted from the node if it is already running on the node, and is not scheduled onto the node if it is not yet running on the node.
In other words, the difference between NoSchedule and NoExecute is that with the first one it won't schedule a pod, but if it is already running, it won't kill it. With the last one, it will kill the pod and re-schedule on another node.
Karmada are not support evict ability now, so I mark it as todo.

[RainbowMango]

/close
As the NoExecute taint was introduced by #1945.

[karmada-bot]

@RainbowMango: Closing this issue.

In response to this:

/close
As the NoExecute taint was introduced by #1945.

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/test-infra repository.