Test framework should support custom taints during testing

[johnSchnake]

What would you like to be added:
A flag/config option for the framework which allows you to specify taints which should be supported by workloads.

What we would do is create a mutating webhook which would ensure pods tolerate a given list of taints. After the tests are completed, the webhook would be removed.

Why is this needed:
This helps users who run in heavily tainted environments continue to run the test suite.

This is a follow-up issue based on the discussion here: #81043 (comment)

/area conformance
/area e2e-framework
/sig testing
/priority important-soon

[k8s-ci-robot]

@johnSchnake: The label(s) area/e2e-framework cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

What would you like to be added:
A flag/config option for the framework which allows you to specify taints which should be supported by workloads.

What we would do is create a mutating webhook which would ensure pods tolerate a given list of taints. After the tests are completed, the webhook would be removed.

Why is this needed:
This helps users who run in heavily tainted environments continue to run the test suite.

This is a follow-up issue based on the discussion here: #81043 (comment)

/area conformance
/area e2e-framework
/sig testing
/priority important-soon

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.

[johnSchnake]

/area e2e-test-framework

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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/test-infra repository.

[valumar]

/reopen

[k8s-ci-robot]

@valumar: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.

[kumiDa]

@johnSchnake, this issue is still relevant to run e2e tests on a live cluster with taints enabled.

How to get the respective SIG to take note of this issue?