Skip to content
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

Closed
weinong opened this issue Aug 3, 2017 · 9 comments
Closed
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@weinong
Copy link
Contributor

weinong commented Aug 3, 2017

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 dns foo.westus.cloudapp.azure.com
likewise, if we have

azure.io.nsg:
   name: foo
   access: allow
   sourceAddressPrefix: *
   targetPortRange: 80

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:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration**: Azure
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 3, 2017
@k8s-github-robot k8s-github-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 3, 2017
@weinong
Copy link
Contributor Author

weinong commented Aug 3, 2017

/sig azure

@k8s-github-robot k8s-github-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 3, 2017
@weinong
Copy link
Contributor Author

weinong commented Aug 3, 2017

@jdumars
Copy link
Member

jdumars commented Aug 16, 2017

/cc @brendandburns

@jdumars jdumars self-assigned this Aug 16, 2017
@jdumars
Copy link
Member

jdumars commented Dec 26, 2017

@weinong does this need to go into the SIG-Azure 1.10 backlog?

@khenidak
Copy link
Contributor

khenidak commented Jan 24, 2018

So if the use case to have one service exposed with LB then

  1. add type: Load Balancer to the service annotation
  2. add service.beta.kubernetes.io/azure-dns-label-name with your dns label to the service

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 external-dns.alpha.kubernetes.io/hostname which a sub domain on your Azure DNS service.

Can you confirm that this covers the use cases you are looking for? @weinong @dtzar

@dtzar
Copy link

dtzar commented Jan 25, 2018

@khenidak - Scenario 1 worked for me on a 1.9.1 K8s cluster. Thanks!

@khenidak
Copy link
Contributor

khenidak commented Jan 25, 2018 via email

@jdumars
Copy link
Member

jdumars commented Jan 25, 2018

Closing, please feel free to re-open if this occurs again.

@jdumars jdumars closed this as completed Jan 25, 2018
@dtzar
Copy link

dtzar commented Jan 26, 2018

For reference, I created this post which walks people through the scenario: http://ow.ly/Fqge30i1O0U

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

6 participants