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

Container Port and Node Port mapping default to open #391

Closed
cdrage opened this issue Jan 25, 2017 · 2 comments
Closed

Container Port and Node Port mapping default to open #391

cdrage opened this issue Jan 25, 2017 · 2 comments

Comments

@cdrage
Copy link
Member

cdrage commented Jan 25, 2017

When mapping a port, for example:

- "80:80"

in the Docker Compose file. It's the same as simply doing

- "80"

Is this normal? Exposing the ports by default when converting them to a service?

@cdrage cdrage changed the title Issue with containerport + nodeport Container Port and Node Port mapping default to open Jan 25, 2017
@surajssd
Copy link
Member

surajssd commented Feb 9, 2017

I think so this is normal, because if you don't create a service name resolution wont happen from other pods. And it's safe because services are by default exposed as clusterIP which is not accessible from outside cluster.

@cdrage
Copy link
Member Author

cdrage commented Feb 9, 2017

Yeah, kind of realized that this issue was me just being a Kubernetes noob :) Closing! Thanks @surajssd

@cdrage cdrage closed this as completed Feb 9, 2017
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

2 participants