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

Kubernetes frontend services should allow to manage Cloud DNS entries #11760

Closed
pkern opened this Issue Jul 23, 2015 · 6 comments

Comments

Projects
None yet
6 participants
@pkern
Contributor

pkern commented Jul 23, 2015

In kind of the same vein as #10323 Kubernetes should allow for a service to repoint a Google Cloud DNS entry to the (newly created) loadbalancer's IP to make the entrypoint publically accessible.

@vishh

This comment has been minimized.

Show comment
Hide comment
@vishh
Member

vishh commented Jul 23, 2015

@thockin

This comment has been minimized.

Show comment
Hide comment
@thockin

thockin Jul 24, 2015

Member

I agree with the goal. I am not sure if it is an attribute of Service or
an orthogonal concept, e.g a Name object. something like this is
definitely in the cards, though.

On Thu, Jul 23, 2015 at 11:06 AM, Philipp Kern notifications@github.com
wrote:

In kind of the same vein as #10323
#10323
Kubernetes should allow for a service to repoint a Google Cloud DNS entry
to the (newly created) loadbalancer's IP to make the entrypoint publically
accessible.


Reply to this email directly or view it on GitHub
#11760.

Member

thockin commented Jul 24, 2015

I agree with the goal. I am not sure if it is an attribute of Service or
an orthogonal concept, e.g a Name object. something like this is
definitely in the cards, though.

On Thu, Jul 23, 2015 at 11:06 AM, Philipp Kern notifications@github.com
wrote:

In kind of the same vein as #10323
#10323
Kubernetes should allow for a service to repoint a Google Cloud DNS entry
to the (newly created) loadbalancer's IP to make the entrypoint publically
accessible.


Reply to this email directly or view it on GitHub
#11760.

@coleca

This comment has been minimized.

Show comment
Hide comment
@coleca

coleca Jul 24, 2015

Support for alternate services as well such as Route53 would be very desirable. At least for the natively supported providers, similar to the "magic" that happens with spinning up load balancers.

coleca commented Jul 24, 2015

Support for alternate services as well such as Route53 would be very desirable. At least for the natively supported providers, similar to the "magic" that happens with spinning up load balancers.

@gtaylor

This comment has been minimized.

Show comment
Hide comment
@gtaylor

gtaylor Sep 3, 2015

Contributor

In the meantime, does anyone have suggestions for how to accomplish this (with Google Cloud DNS in particular)?

Contributor

gtaylor commented Sep 3, 2015

In the meantime, does anyone have suggestions for how to accomplish this (with Google Cloud DNS in particular)?

@justinsb

This comment has been minimized.

Show comment
Hide comment
@justinsb

justinsb Nov 15, 2016

Member

dns-controller does this. It is currently part of kops. If there is interest I could propose it for incubation as a top-level project. Right now it is nestled under kops: https://github.com/kubernetes/kops/tree/master/dns-controller

Member

justinsb commented Nov 15, 2016

dns-controller does this. It is currently part of kops. If there is interest I could propose it for incubation as a top-level project. Right now it is nestled under kops: https://github.com/kubernetes/kops/tree/master/dns-controller

@thockin thockin added the sig/network label May 19, 2017

@thockin

This comment has been minimized.

Show comment
Hide comment
@thockin

thockin May 19, 2017

Member

ExternalDNS is a standalone project now.

Member

thockin commented May 19, 2017

ExternalDNS is a standalone project now.

@thockin thockin closed this May 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment