Default and built-in Swarm collections¶
This topic describes both MKE default and built-in Swarm collections.
Default Swarm collections¶
Each user has a default collection, which can be changed in the MKE preferences.
To deploy resources, they must belong to a collection. When a user deploys a resource without using an access label to specify its collection, MKE automatically places the resource in the default collection.
Default collections are useful for the following types of users:
Users who work only on a well-defined portion of the system
Users who deploy stacks but do not want to edit the contents of their compose files
Custom collections are appropriate for users with more complex roles in the system, such as administrators.
Note
For those using Docker Compose, the system applies default collection labels
across all resources in the stack unless you explicitly set
com.docker.ucp.access.label.
Built-in Swarm collections¶
MKE includes the following built-in Swarm collections:
Built-in Swarm collection |
Description |
|---|---|
|
Path to all resources in the Swarm cluster. Resources not in a collection are put here. |
|
Path to MKE managers, MSR nodes, and MKE/MSR system services. By default, only administrators have access to this collection. |
|
Path to a user’s private collection. Private collections are not created until the user logs in for the first time. |
|
Path to a user’s private collection. Private collections are not created until the user logs in for the first time. |
|
Path to the access control labels of legacy versions (UCP 2.1 and earlier). |