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
Bug 1942630: UPSTREAM: 96789: Choosing the right source VIP for local endpoints #639
Bug 1942630: UPSTREAM: 96789: Choosing the right source VIP for local endpoints #639
Conversation
@sebsoto: This pull request references Bugzilla bug 1942630, which is invalid:
Comment 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. |
@sebsoto: the contents of this pull request could be automatically validated. The following commits are valid:
|
/bugzilla refresh |
@sebsoto: This pull request references Bugzilla bug 1942630, which is invalid:
Comment 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. |
/cc @dcbw @JacobTanenbaum |
/bugzilla refresh |
@sebsoto: An error was encountered querying GitHub for users with public email (sgao@redhat.com) for bug 1942630 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
non-200 OK status code: 403 Forbidden body: "{\n \"documentation_url\": \"https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#abuse-rate-limits\",\n \"message\": \"You have triggered an abuse detection mechanism. Please wait a few minutes before you try again.\"\n}\n"
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
/retest |
/bugzilla refresh |
@sebsoto: This pull request references Bugzilla bug 1942630, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: 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. |
/lgtm |
/hold this branch is not intended for kube-proxy. |
As agreed on Slack, WMCO will move away in 4.8 from vendoring the master and release branches of this repository. They are not meant to be consumed by other components and might break at any time for their use-case. For 4.6, we will accept this carry to keep the builds working. /hold cancel |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dcbw, sebsoto, sttts 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 |
Jira story here: https://issues.redhat.com/browse/WINC-593 |
@sebsoto: All pull requests linked via external trackers have merged: Bugzilla bug 1942630 has been moved to the MODIFIED state. 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. |
Updates the kubernetes submodule to openshift/kubernetes#639 Done with `git submodule update --remote kubernetes`
This fixes an issue where LoadBalancers would stop directing traffic to Windows pods, when multiple pods were behind the LoadBalancer.