docs: give the deployment shapes one home and link to it
The three supported shapes were described in pieces across the swarm docs, so a reader assembling them got a different answer depending on which page they landed on. They live in services.md now, and the other pages point at it. Split out of #3719 at mara's request: that PR also rewrites the snapshot-store doc, which is a separate argument.
This commit is contained in:
parent
c73ce03244
commit
d6ca52535f
3 changed files with 39 additions and 2 deletions
|
|
@ -25,9 +25,13 @@ missing, and a secret minted on another container's first boot does not exist
|
|||
yet. Binding it would make one container wait on a file that waits on a
|
||||
container that starts after it.
|
||||
|
||||
## The three topologies
|
||||
## Topologies, by who places secrets
|
||||
|
||||
Every row below is read against one of these.
|
||||
Every row below is read against one of these. This is a different cut
|
||||
from the [deployment shapes](services.md#deployment-shapes) --- those
|
||||
say *where services run*, these say *who is responsible for a secret
|
||||
file being there* --- so the two lists do not line up one-to-one, and
|
||||
neither is a renaming of the other.
|
||||
|
||||
| topology | what it means | who places secrets |
|
||||
|---|---|---|
|
||||
|
|
|
|||
Loading…
Reference in a new issue