promote TaintBasedEvictions featuregate to beta

[Huang-Wei]

What this PR does / why we need it:

Enable TaintBasedEvictions featuregate by default.

Which issue(s) this PR fixes:

Part of #69533.

Special notes for your reviewer:

Release note:

`TaintBasedEvictions` feature is promoted to beta.

/kind feature
/sig scheduling

[Huang-Wei]

/test pull-kubernetes-integration

[Huang-Wei]

/assign @k82cn @bsalamat

[k8s-ci-robot]

@Huang-Wei: GitHub didn't allow me to assign the following users: for, approval.

Note that only kubernetes members and repo collaborators can be assigned.
For more information please see the contributor guide

In response to this:

/assign @k82cn @bsalamat for approval

/unassign @smarterclayton @dchen1107

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.

[k82cn]

/lgtm

The notes should be "Upgraded TaintBasedEvictions feature to beta" or something similar.

[Huang-Wei]

@k82cn sure.

[Huang-Wei]

/cc @bsalamat

for approval.

[yastij]

/lgtm

[bsalamat]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bsalamat, Huang-Wei

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

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/features/OWNERS [bsalamat]

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

[spiffxp]

/hold
Shouldn't this be the last item to merge out of everything listed on #69533 ?

Feel free to /hold cancel if I'm wrong, but it just seems odd to move to beta and then bump test coverage. If we had test coverage gates in place we definitely wouldn't allow this?

[Huang-Wei]

@spiffxp in theory, you're right. But there are usually other aspects not being properly covered in unit test/integration test/e2e test. Like in previous release, we met some scalability issue in last moment of promoting TaintNodeByCondition to beta.

And even for e2e test, I don't have a gce/gke/aws env, so I only run it against my local kubeadm cluster. It'd be good to see how prow job works after the featuregate is enabled.

So based on above considerations, and our understanding/test coverage on this featuregate, at this moment we're confident to enable it in master branch.

[AishSundar]

/milestone v1.13

[Huang-Wei]

@spiffxp I'd like do a hold cancel after merge of #65350 is completed.

[Huang-Wei]

/hold cancel