Bare-metal components

The bare-metal management solution for MOSK includes the following components:

Bare-metal components
Component	Description
OpenStack Ironic	The backend bare-metal manager in a standalone mode with its auxiliary services that include `httpd`, `dnsmasq`, and `mariadb`.
OpenStack Ironic Inspector	Introspects and discovers the bare-metal hosts inventory. Includes OpenStack Ironic Python Agent (IPA) that is used as a provision-time agent for managing bare-metal hosts.
Ironic Operator	Monitors changes in the external IP addresses of `httpd`, `ironic`, and `ironic-inspector` and automatically reconciles the configuration for `dnsmasq`, `ironic`, `baremetal-provider`, and `baremetal-operator`.
Bare Metal Operator	Manages bare-metal hosts through the Ironic API. The Bare Metal Operator implementation is based on the Metal³ project.
Bare-metal resources controller	Ensures that the bare-metal provisioning artifacts such as the distribution image of the operating system is available and up to date.
`cluster-api-provider-baremetal`	The controller that manages the bare-metal cluster and its machines in MOSK, based on the Metal³ implementation of `cluster-api-provider-baremetal` for the Cluster API.
HAProxy	Load balancer for external access to the Kubernetes API endpoint.
LCM Agent	Used for operating system configuration and control over the life cycle of a bare-metal machine resources.
Ceph	Distributed shared storage is required by MOSK services for MOSK clusters to create persistent volumes to store their data. Ceph is not deployed on management clusters.
MetalLB	Load balancer for Kubernetes services on bare metal. [1]
Keepalived	Monitoring service that ensures availability of the virtual IP for the external load balancer endpoint (HAProxy). [1]
IPAM	IP address management services provide consistent IP address space to the machines in bare-metal clusters. See details in IP Address Management.

The diagram below illustrates the components and resource kinds:

bm-component-stack

Note

For MOSK 25.2 clusters with MOSK management 2.30, the KaaSCephCluster object may still be present on the management cluster and translated into MiraCeph on the MOSK cluster.

Starting from MOSK management 2.31, KaaSCephCluster is unsupported, and Ceph Controller works with MiraCeph directly on the MOSK cluster, as shown in the diagram above.