Partial cherry-pick of #46517 to fix flaky e2e skew tests #71631
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To prevent flakiness in kubectl e2e skew tests
k8s-ci-robot
added
do-not-merge/cherry-pick-not-approved
k8s-ci-robot
added
the
sig/testing
|
/lgtm cc @soltysh |
k8s-ci-robot
added
the
lgtm
k8s-ci-robot
added
priority/critical-urgent
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: m1kola, soltysh 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:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
feiskyer
added
cherry-pick-approved
|
/retest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind flake
What this PR does / why we need it:
Partial cherry pick of #46517 on
release-1.12.Fixes flaky skew tests for kubectl port-forward.
Special notes for your reviewer:
The original PR contains required test changes and new functionality, so it can't be cherry-picked automatically in a whole.
But would be great to have this merged because this type of flakiness in skew tests happens very often. Some recent examples:
kubernetes/kubectl#558 contains more details (start from this comment: kubernetes/kubectl#558 (comment))
Does this PR introduce a user-facing change?:
/sig cli