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

Use services with endpoints using a hostname #23921

Closed
rata opened this issue Apr 6, 2016 · 2 comments
Closed

Use services with endpoints using a hostname #23921

rata opened this issue Apr 6, 2016 · 2 comments
Milestone

Comments

@rata
Copy link
Member

rata commented Apr 6, 2016

Hi,

It will be nice if an Amazon RDS, Amazon ELB or some other hosted service that provides a hostname and not a static IP (like searchify.com or tons of other hosted services) can be a kubernetes service.

If it is a kubernetes service, it can connect to it using the same way, use a simple name, connect to public services exposed in an ELB on another region (maybe by kubernetes ;)) on AWS, just a hosted service like I already said, etc.

The problem right now with that is that a service and an Endpoint needs to be created, and the endpoint can only point to an IP address IIUC 1.

Talking with @justinsb on slack, the immediate way seems to resolve the hostname when the TTL is about to expire and update the IP addresses in the endpoint. But haven't checked the Endpoint code and maybe is possible/desirable to add hostname support.

Do you also think it is valuable to have a way to use kubernetes services with hostnames? Do you have any suggestions on how to do it?

Thanks a lot!
Rodrigo

@justinsb justinsb added this to the v1.3 milestone Apr 6, 2016
@justinsb
Copy link
Member

justinsb commented Apr 6, 2016

This is a great idea! We should do something in the 1.3 timeline. It might not be a full integration into core, but even just an example pod that can mirror DNS into an external service would be great I think!

@thockin
Copy link
Member

thockin commented Apr 6, 2016

This is dup of #13748 and/or #13358 (which haven't been de-duped because they are subtly different). Let's please take the conversation there :)

@thockin thockin closed this as completed Apr 6, 2016
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this issue Oct 9, 2019
Bug 1751640: UPSTREAM: 83108: Use pod + nsenter instead of SSH in block volume tests

Origin-commit: a696b23432430416c7f8a1ea943f9cd0088c2829
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants