* Added Azure Disk and Azure File
I have added Azure Disk and Azure file documentation for use with UCP
3.0 or newer.
* Added the Azure Disk Content
* Added the Azure File Content
* Updated the Toc to include Azure Disk and Azure File
Signed-off-by: Olly Pomeroy <olly@docker.com>
* Responding to feedback, inc changing Azure File to Azure Files
Following on from Steven and Deeps feedback this commit addresses those
nits. Including changing `Operators` to `Platform Operators`, switching
`Azure File` to `Azure Files` and many small formating changes.
Signed-off-by: Olly Pomeroy <olly@docker.com>
* Minor style updates
* Minor style updates
* Final edits
* Logging driver port from vnext-engine
* Update json-file.md
* Update json-file.md
* Port changes from vnext-engine
* Updates based on feedback
* Added note back in
* Added note back in
* Added limitations per Anusha
* New dual logging info
* Added link to new topic
Needs verification.
* Changes per feedback.
* Updates per feedback
* Updates per feedback
* Updated 20m
* Added CE version
* Added missing comma
* Updates per feedback
* Add raw tag
Add TOC entry - subject to change
* Add entry for local logging driver
* Update config/containers/logging/configure.md
Co-Authored-By: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Update config/containers/logging/configure.md
Co-Authored-By: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Update config/containers/logging/configure.md
Co-Authored-By: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Update config/containers/logging/configure.md
Co-Authored-By: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* Updates per feedback
* Updates per feedback
content management:
- rename interlock-default-mode.{png,svg} to interlock-task...
- add frontmatter and TOC
formatting:
- newline sentences for reviewability
content:
- replace default mode with task mode
- note introduced-in UCP versions
- remove websockets from unsupported. websocket upgrade routes fine
through Swarm VIP. applications that use web sockets tend to want
sticky sessions, but sticky sessions must be configured separately.
don't conflate the two.
- clarify effect on canary deployments
- general wording improvements
