Manager nodes¶
Manager nodes manage a swarm and persist the swarm state. Using several
containers per node, the ucp-manager-agent
automatically deploys all
MKE components on manager nodes, including the MKE web UI and the data stores
that MKE uses.
Note
Some Kubernetes components are run as Swarm services because the MKE control plane is itself a Docker Swarm cluster.
The following tables detail the MKE services that run on manager nodes:
MKE component |
Description |
---|---|
|
The centralized service for identity and authentication used by MKE and MSR. |
|
A container that stores authentication configurations and data for users, organizations, and teams. |
|
A container that performs scheduled LDAP synchronizations and cleans authentication and authorization data. |
|
A certificate authority to sign client bundles. |
|
The agent that monitors the cluster-wide MKE components. Runs on only one manager node. |
|
A certificate authority used for TLS communication between MKE components. |
|
The MKE web server. |
|
A container for collecting disk/hardware information about the host. |
|
A container that monitors Swarm workloads configured to use layer 7 routing. Only runs when you enable layer 7 routing. |
|
A service that manages Interlock configuration. |
|
A service that verifies the run status of the Interlock extension. |
|
A service that provides load balancing and proxying for Swarm workloads. Runs only when layer 7 routing is enabled. |
|
A master component that serves the Kubernetes API. It persists its state
in |
|
A master component that manages the desired state of controllers and other Kubernetes objects. It monitors the API server and performs background tasks when needed. |
|
The Kubernetes node agent running on every node, which is responsible for running Kubernetes pods, reporting the health of the node, and monitoring resource usage. |
|
The networking proxy running on every node, which enables pods to contact Kubernetes services and other pods by way of cluster IP addresses. |
|
A master component that manages Pod scheduling, which communicates with the API server only to obtain workloads that need to be scheduled. |
|
A container used to store the MKE configurations. Do not use it in your applications, as it is for internal use only. Also used by Kubernetes components. |
|
The agent that monitors the manager node and ensures that the right MKE services are running. |
|
A TLS proxy that allows secure access from the local Mirantis Container Runtime to MKE components. |
|
A Swarm service that sends notifications to Salesforce when alerts are configured by OpsCare, and later when they are triggered. |
|
A container used to provide backward compatibility with Docker Swarm. |
MKE component |
Description |
---|---|
|
An MKE service that accounts for the removal of dockershim from Kubernetes as of version 1.24, thus enabling MKE to continue using Docker as the container runtime. |
|
A cluster-scoped Kubernetes controller used to coordinate Calico networking. Runs on one manager node only. |
|
The Calico node agent, which coordinates networking fabric according
to the cluster-wide Calico configuration. Part of the |
|
An init container for Calico controller that sets the StrictAffinity in Calico networking according to the configured boolean value. |
|
An init container for |
|
A container in which the Calico CNI plugin binaries are installed and configured on each host. Part of the calico-node DaemonSet. Runs on all nodes. |
|
The CoreDNS plugin, which provides service discovery for Kubernetes services and Pods. |
|
The Gatekeeper manager controller for Kubernetes that provides policy enforcement. Only runs when OPA Gatekeeper is enabled in MKE. |
|
The audit controller for Kubernetes that provides audit functionality of OPA Gatekeeper. Only runs when OPA Gatekeeper is enabled in MKE. |
|
A custom Kubernetes resource component that translates Compose files into Kubernetes constructs. Part of the Compose deployment. Runs on one manager node only. |
|
The API server for Kube Compose, which is part of the compose deployment. Runs on one manager node only. |
|
The Ingress controller for Kubernetes, which provides layer 7 routing for Kubernertes services. Only runs with Ingress for Kubernetes enabled. |
|
A container that generates the inventory targets for Prometheus server. Part of the Kubernetes Prometheus Metrics plugin. |
|
A container used to collect and process metrics for a node. Part of the Kubernetes Prometheus Metrics plugin. |
|
A container that runs a proxy for the metrics server. Part of the Kubernetes Prometheus Metrics plugin. |
|
A container that provides node feature discovery labels for Kubernetes nodes. |
|
A container that provides node feature discovery labels for Kubernetes nodes. |
|
A container that provides support for Multi Instance GPU (MIG) on NVIDIA GPUs. |
|
A container that provides a per-node service that manages the encryption state of the data plane. |
|
A container that provides the key management process that configures and periodically rotates the encryption keys. |
MKE component |
Description |
---|---|
|
The pause container for the |
|
The pause container for the
|
|
The pause container for the |
|
The pause container for
|
|
The pause container for the ucp-coredns Pod. |
|
The pause container for
|
|
The pause container for
|
|
The pause container for
|
|
The pause container for the ucp-metrics. |
|
The pause container for the node feature discovery labels on Kubernetes nodes. |
|
A pause container for
|
|
A pause container for
|