-
Notifications
You must be signed in to change notification settings - Fork 211
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
don't process unsupported loadbalancers with mixed protocols #475
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea 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 |
/assign @cezarygerard @bowei @thockin |
/hold wait for kubernetes/kubernetes#115966 to sync both patches |
/assign @andrewsykim |
kubernetes/kubernetes#115966 already merged /assign @jprzychodzen |
@cezarygerard we need to get this merge to avoid confusion on users |
(Thanks for the PR) |
The external cloud provider controller for loadbaancers does not support Services with different protocols and most probably it will never support them, since most of the functionality and development for loadbalancers is being done in the ingress-gce project. Ref: kubernetes/enhancements#1435 Change-Id: Iaec2ee17ccdc7c55c613189d8a3708b5a62d5076
@aojea: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
@cezarygerard please review again and lgtm once you are ok |
/lgtm |
The external cloud provider controller for loadbalancers does not support Services with different protocols and most probably it will never support them, since most of the functionality and development for loadbalancers is being done in the ingress-gce project.
Current code assumes that is not possible to have multiple protocols in multiple places
cloud-provider-gcp/providers/gce/gce_loadbalancer_external.go
Lines 1043 to 1050 in a874896
cloud-provider-gcp/providers/gce/gce_loadbalancer_internal.go
Lines 857 to 858 in a874896
Code borrowed from the cloud-provider-aws, thanks
Ref: https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/1435-mixed-protocol-lb
Change-Id: Iaec2ee17ccdc7c55c613189d8a3708b5a62d5076