Added TaintEffectNoExecute support to the scheduled TaintToleration p…

[learner0810]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:

xref #878

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[karmada-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign kevin-wangzefeng after the PR has been reviewed.
You can assign the PR to them by writing /assign @kevin-wangzefeng in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Garrybest]

/assign @mrlihanbo, I'm not sure the former intention.

[mrlihanbo]

I'm not sure the former intention.

Hi, @Garrybest , 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.

[Garrybest]

It makes sense. This PR needs more discussion.

[Garrybest]

/hold

[RainbowMango]

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

[karmada-bot]

@RainbowMango: Closed this PR.

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.