-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
skip_regex.go: kube-router add back in service afinity test #16188
skip_regex.go: kube-router add back in service afinity test #16188
Conversation
Hi @aauren. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Closing this given the feedback on kubernetes/kubernetes#122440 |
Accidentally closed this one too quickly. This one can be merged now that kubernetes/kubernetes#122440 has been merged. |
/ok-to-test |
/test ? |
/test pull-kops-e2e-cni-kuberouter |
We should update this logic to only skip for k8s versions < 1.30. We wont see the impact of this skip removal until 1.30 is stable though because both the periodic and presubmit tests for kuberouter use the latest stable builds of k/k, not the CI builds. We could also switch them to use CI until then. |
/test pull-kops-e2e-cni-kuberouter |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
@hakman
Requires kubernetes/kubernetes#122440 to be merged first.
Once those two are merged, kube-router should be passing both of the service affinity tests in the e2e suite, so we can allow those to run and no longer worry about failures.