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

Add clarity note around required user-created overlay #2972

Merged
merged 1 commit into from
Apr 21, 2017
Merged

Add clarity note around required user-created overlay #2972

merged 1 commit into from
Apr 21, 2017

Conversation

johnharris85
Copy link
Contributor

Proposed changes

Fix #176

@@ -158,6 +158,8 @@ the service a VIP. The VIP maps to a DNS alias based upon the service name.
Containers on the network share DNS mappings for the service via gossip so any container on the network can access the service via its service
name.

>**Note**: Service discovery will only work if your services are attached to a user-created overlay network (see top of this article). When a Swarm is initialized an ingress network is created (if it doesn't already exist) however containers are not added directly to this network. Ingress is used to enable to routing mesh functionality of swarm mode.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to capitalize swarm

Maybe a little rewording:

When a swarm is initialized, an ingress network is created if it does not exist. This network is not used by containers, but to enable the daemons participating in the swarm to communicate.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Misty. Agree on first sentence. For second, what about "This network is not used by containers, but to enable the routing mesh functionality in swarm mode."

Just to make explicit that it's routing mesh that ingress enables, rather than 'just' daemon communication? WDYT?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good!

@londoncalling
Copy link
Contributor

LGTM

@londoncalling londoncalling merged commit fd1fd15 into docker:master Apr 21, 2017
@johnharris85 johnharris85 deleted the 176-overlay-explanation branch April 21, 2017 19:06
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

Successfully merging this pull request may close these issues.

4 participants