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

Unable to find documentation about how to expose ports from Kubernetes services #5690

Closed
jnewland opened this issue Jan 8, 2018 · 2 comments

Comments

@jnewland
Copy link

jnewland commented Jan 8, 2018

Problem description

After installing Docker for Mac w/ Kubernetes and deploying a service to it, I wanted to view this service's HTTP interface from a web browser on my Mac. I'm unable to find documentation on how to do this.

Problem location

I couldn't find the information I wanted. I expected to find it near the following URL: https://docs.docker.com/docker-for-mac/networking/ (or possibly on some non-Mac-specific URL!)

Project version(s) affected

I'm running Version 17.12.0-ce-mac45 (21669), but this missing documentation affects the experience for all users of Docker's Kubernetes support.

Suggestions for a fix

My experiments seem to indicate that Kubernetes services with type==LoadBalancer have their ports exposed with vpnkit, but I can't find this logic in any open source repo. I'd suggest reviewing the logic that exposes these ports and creating documentation outlining it's behavior. If ya'll can help me find that logic, I'd be happy to push up a PR with some proposed docs! 💞

@ghost
Copy link

ghost commented Jan 2, 2019

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!

@ghost ghost closed this as completed Jan 2, 2019
@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

@docker docker locked and limited conversation to collaborators Mar 12, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants