New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deflake ingress e2e updates #98430
Deflake ingress e2e updates #98430
Conversation
@liggitt: The label(s) In response to this:
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. |
@liggitt: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt 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 |
/lgtm thanks! |
thanks, picked to 1.19 and 1.20 since this flake impacts conformance test runs |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
1 similar comment
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
…0-upstream-release-1.20 Automated cherry pick of #98430: Deflake ingress updates
…0-upstream-release-1.19 Automated cherry pick of #98430: Deflake ingress updates
What type of PR is this?
/kind flake
What this PR does / why we need it:
When an Ingress controller is present, it can update the object asynchronously. The e2e test that does an update and status update must be prepared to retry on a conflict error if encountered.
Does this PR introduce a user-facing change?:
/cc @johnbelamaric @bowei
/sig network