-
Notifications
You must be signed in to change notification settings - Fork 193
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
clustermesh: Add support for kubernetes service annotations #1938
clustermesh: Add support for kubernetes service annotations #1938
Conversation
Commit 382c4fb does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
382c4fb
to
f83f4dd
Compare
f83f4dd
to
9ec75c5
Compare
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.
@joaoubaldo Thanks for the PR! LGTM
@joaoubaldo looks like you're hitting some CI failures that were fixed last month but your branch base is out of date. Could you rebase onto latest? |
Add a `--service-annotation` argument so that custom annotations can be added to the Kubernetes Service when clustermesh is being enabled. A use case for this flag is to create a private NLB in AWS instead of a public classic LB: > cilium clustermesh enable --service-type LoadBalancer --service-annotation 'service.beta.kubernetes.io/aws-load-balancer-internal=0.0.0.0/0' --service-annotation 'service.beta.kubernetes.io/aws-load-balancer-type=nlb Signed-off-by: Joao Ubaldo <me@joaoubaldo.com>
9ec75c5
to
ade7a01
Compare
@thorn3r rebased and all workflows that were executed passed now. Thanks |
@thorn3r could you please take another look? |
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.
thanks, looks great!
Add a
--service-annotation
argument so that custom annotations can be added to the Kubernetes Service when clustermesh is being enabled.A use case for this flag is to create a private NLB in AWS instead of a public classic LB: