Volumes

Volumes

MKE uses named volumes to persist data on all nodes on which it runs.

Volumes used by MKE

Volume name

Contents

ucp-auth-api-certs

Certificate and keys for the authentication and authorization service

ucp-auth-store-certs

Certificate and keys for the authentication and authorization store

ucp-auth-store-data

Data of the authentication and authorization store, replicated across managers

ucp-auth-worker-certs

Certificate and keys for authentication worker

ucp-auth-worker-data

Data of the authentication worker

ucp-client-root-ca

Root key material for the MKE root CA that issues client certificates

ucp-cluster-root-ca

Root key material for the MKE root CA that issues certificates for swarm members

ucp-controller-client-certs

Certificate and keys that the MKE web server uses to communicate with other MKE components

ucp-controller-server-certs

Certificate and keys for the MKE web server running in the node

ucp-kv

MKE configuration data, replicated across managers

ucp-kv-certs

Certificates and keys for the key-value store

ucp-metrics-data

Monitoring data that MKE gathers

ucp-metrics-inventory

Configuration file that the ucp-metrics service uses

ucp-node-certs

Certificate and keys for node communication

You can customize the volume driver for the volumes by creating the volumes prior to installing MKE. During installation, MKE determines which volumes do not yet exist on the node and creates those volumes using the default volume driver.

By default, MKE stores the data for these volumes at /var/lib/docker/volumes/<volume-name>/_data.