-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
feat: support for enabling proxy protocol on specified ports only #3732
base: main
Are you sure you want to change the base?
Conversation
Welcome @arnaud-dezandee! |
Hi @arnaud-dezandee. Thanks for your PR. I'm waiting for a kubernetes-sigs 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-sigs/prow repository. |
bump |
/lgtm |
rawAttributes[tgAttrsProxyProtocolV2Enabled] = "true" | ||
break | ||
} | ||
if proxySelector == strconv.Itoa(int(port.Port)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iiuc, if one port in the TG is in the annotation to enable proxy protocol, this TG will have proxy protocol v2 enabled? Maybe need to call out in the doc too.
Also, I'm just thinking about some edge cases, do we need to add a nil check for port.Port
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll check that yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just checked, nil check is not required here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added more details in the doc
New changes are detected. LGTM label has been removed. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: arnaud-dezandee The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
b81ab69
to
4403f91
Compare
a5e01b7
to
f1e2d8b
Compare
bump |
@arnaud-dezandee: 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-sigs/prow repository. I understand the commands that are listed here. |
PR needs rebase. 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-sigs/prow repository. |
Hi, it would be really nice to have this feature :) Are there any updates on this? |
Issue
Hi! I am using the LBC with Istio gateway ingress and the proxy protocol activated on the k8s service, but the health check port 15021 on the Istio side does not support this protocol.
Description
Keeping the default behavior with a
*
value for theservice.beta.kubernetes.io/aws-load-balancer-proxy-protocol
, this change allows you to specify a list of ports (i.e., target groups) on which the proxy protocol will be activated.Example for Istio:
Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯