-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Azure: configure the properties of load balancer endpoint through annotations #50062
Comments
/sig azure |
/cc @brendandburns |
@weinong does this need to go into the SIG-Azure 1.10 backlog? |
So if the use case to have one service exposed with LB then
if the use case is to have ingress controller with a DNS label, then the service that exposes the ingress controller to the LB should have the above. if the use case is to have multiple ingress resources each have a DNS label then use external DNS project. The idea is each ingress resources carries an annotation for DNS label Can you confirm that this covers the use cases you are looking for? @weinong @dtzar |
@khenidak - Scenario 1 worked for me on a 1.9.1 K8s cluster. Thanks! |
Closing, please feel free to re-open if this occurs again. |
For reference, I created this post which walks people through the scenario: http://ow.ly/Fqge30i1O0U |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
What you expected to happen:
Right now, it's a manual process to update the exposed load balancer endpoint with DNS, NSG, and etc. It could be automated by cloud provider through annotations on service resource, for instance:
azure.io.domainHost: foo
which will assign dnsfoo.westus.cloudapp.azure.com
likewise, if we have
Then the nsg of the exposed IP will be configured properly.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: