Overlay networking tutorial: confusing info about default network use

[3rdcycle]

Is this a docs issue?

• My issue is about the documentation content or website

Type of issue

Other

Description

I find the information about using / not using the default overlay network very confusing.

The first section is about using the default overlay network:

Use the default overlay network demonstrates how to use the default overlay network that Docker sets up for you automatically when you initialize or join a swarm. This network is not the best choice for production systems.

Does this refer to the ingress network? If yes, why is this not a good choice for production? Isn't ingress traffic supposed to go via ingress network? Am I not supposed to publish a port to the Ingress network? Or is it not a good choice for a different kind of use (inter-task communication)?

The tutorial then goes on to create a user defined network nginx-net and attach a service to it in the same section (so, it's not using the "default network"?)

The second section is about "Using a user-defined overlay network". Yet the steps involved seem to be exactly the same as in the first section only with a different name for the network (my-overlay instead of nginx-net).

Location

https://docs.docker.com/network/network-tutorial-overlay/

Suggestion

• Clarify for what purpose exactly one should not use the default network
• Point out the differences (if any) between the "Use the default overlay network" and "Use a user-defined overlay network" approaches

[dvdksn]

/cc @akerouanton @robmry

[docker-robot]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale