metal3-io

metal3-io
Name	metal3-io
Developer	Linux Foundation, OpenInfra Foundation, Cloud Native Computing Foundation
Released	2018
Programming language	Go (programming language)
License	Apache License

metal3-io metal3-io is an open-source project that integrates bare-metal provisioning with cloud-native orchestration for Kubernetes clusters. It provides machine lifecycle management by combining technologies such as Ironic (OpenStack), Mellanox, PXE boot, and Cluster API to enable automated provisioning, reclamation, and control of physical servers. The project bridges tooling from OpenStack, Red Hat, Canonical (company), Intel and ecosystem projects like Docker, KubeVirt, and Prometheus to support scalable datacenter and edge deployments.

Overview

metal3-io was initiated to unify bare-metal operations with orchestration patterns pioneered by Kubernetes and Cloud Native Computing Foundation projects. It targets operators familiar with OpenStack fleets, administrators from Red Hat and Ubuntu environments, and hardware vendors including Dell Technologies, HPE, and Supermicro. The project leverages design patterns from Cluster API and borrows lifecycle concepts from Ironic (OpenStack) while interacting with provisioning standards such as PXE and firmware interfaces like UEFI.

Architecture

The architecture centers on controllers running alongside Kubernetes control planes and communicates with provisioning backends such as Ironic (OpenStack) and network services like DHCP. A reconciler model inspired by Controller-runtime and Kubebuilder drives state convergence between Kubernetes resources, Bare Metal Hosts and provisioning APIs originally defined by OpenStack Ironic. The control plane integrates with hardware management interfaces including Redfish, Intelligent Platform Management Interface and vendor-specific BMC implementations produced by Supermicro, Dell EMC and HPE. Storage and networking overlays can integrate with projects such as Ceph, OVN, Calico, and Flannel.

Components

metal3-io spans multiple components: the metal controllers implemented in Go (programming language), a set of Custom Resource Definitions compatible with Kubernetes API Server, and a provisioning backend adapter for Ironic (OpenStack). Key CRDs mirror concepts from Cluster API such as Machine and Cluster, and introduce resources like BareMetalHost and BareMetalMachine. Supporting components include an inspector that leverages IPMI or Redfish to collect inventory, and the provisioning engine which orchestrates PXE workflows, image deployment with iPXE and interactions with firmware for UEFI Secure Boot flows. Observability ties into Prometheus and Grafana for metrics and dashboards.

Installation and Deployment

Deployment commonly uses Cluster API providers, Kubectl, and operator frameworks like Operator Lifecycle Manager or tooling from kustomize and Helm. Operators set up RBAC linked to authentication systems such as OAuth2 or OpenID Connect providers used by enterprises like Google, Microsoft, and GitHub. Bare-metal provisioning requires integration with DHCP and DNS services often provided by ISC DHCP Server or cloud-integrated services from AWS, Azure, and Google Cloud Platform when hybrid control is needed. Automation pipelines frequently incorporate Ansible, Terraform, and CI/CD systems like Jenkins or GitLab CI for reproducible rollouts.

Use Cases and Integrations

metal3-io supports use cases including private cloud deployments for organizations such as NASA, CERN, and MIT, high-performance computing clusters for vendors like NVIDIA and Intel, and edge infrastructure for telecommunications firms including Ericsson and Nokia. Integrations exist with virtualization projects like KubeVirt and storage orchestration from Rook and Longhorn. It is used in hybrid scenarios combining OpenStack control planes with Kubernetes workloads and in CI infrastructures for projects such as Linux Kernel and Kubernetes itself.

Development and Governance

Development is driven by contributors from companies like Red Hat, Intel, IBM, and Equinix Metal, with governance practices reflecting foundations such as the Linux Foundation and OpenInfra Foundation. The project adopts contribution models similar to Kubernetes SIGs, with community meetings, issue tracking via GitHub, and design proposals akin to Kubernetes Enhancement Proposals. Release management coordinates with related projects including Cluster API and Ironic (OpenStack) to maintain compatibility matrices.

Security and Reliability

Security relies on secure firmware practices from Intel and AMD, BMC hardening recommendations from DMTF and OpenBMC, and cryptographic tooling from projects like Sigstore. Reliability patterns follow best practices endorsed by CNCF and The Linux Foundation such as observability via Prometheus, testing with Sonobuoy and Kind, and continuous integration with Zuul or Jenkins. Incident response and vulnerability disclosure align with policies used by Red Hat and Ubuntu (operating system) vendors.

Category:Bare metal provisioning Category:Kubernetes