Metal³
Metal³ is an open-source framework that integrates bare metal host provisioning into Kubernetes-based cluster management workflows using Kubernetes-native APIs and controllers.
- Bare metal host lifecycle management via Kubernetes Custom Resource Definitions (infrastructure automation).
- Integration with Kubernetes Cluster Application Programming Interface (API) for declarative cluster provisioning on physical infrastructure (cluster lifecycle management).
- Abstraction of underlying provisioning tools such as Ironic through a Kubernetes controller layer (infrastructure orchestration).
- Support for discovery, inspection, provisioning, deprovisioning, and configuration of bare metal servers (datacenter infrastructure management).
- Extensible architecture for integrating bare metal into cloud native and GitOps-oriented platforms (cloud native infrastructure enablement).
More About Metal³
Metal³ is an open-source project that brings bare metal host provisioning and management into the Kubernetes ecosystem by exposing infrastructure operations through Kubernetes-style APIs and controllers. It targets environments where operators want to manage physical servers using the same declarative patterns used for containerized workloads and cluster lifecycle management.
The project focuses on the problem space of automating the lifecycle of bare metal machines (infrastructure automation) in a Kubernetes context. It defines Kubernetes Custom Resource Definitions (CRDs) that represent physical hosts and related configuration objects. Controllers reconcile these resources to perform tasks such as hardware inspection, image deployment, network configuration, power control, and deprovisioning. Through this model, Metal³ enables infrastructure teams to express desired state for bare metal in a version-controlled, declarative manner.
Metal³ commonly integrates with the Kubernetes Cluster API (cluster lifecycle management), where it serves as the infrastructure provider for clusters that run directly on physical servers rather than on virtual machines or cloud instances. In this architecture, Cluster API resources describe the cluster topology and node pools, while Metal³ resources Marketing Automation Platform (MAP) those nodes onto actual bare metal hosts. The controllers coordinate provisioning so that Kubernetes nodes are installed, configured, and joined to the cluster according to the declared specifications.
Under the hood, Metal³ leverages existing bare metal provisioning technologies, notably Ironic (bare metal provisioning service), through a controller layer that abstracts vendor- and environment-specific details. This allows enterprises to standardize on Kubernetes-native workflows while reusing proven provisioning backends. The framework also supports capabilities such as hardware introspection and cleaning, which help prepare machines before they are handed over for cluster use.
In enterprise environments, Metal³ is used to manage datacenter or edge fleets of physical servers as part of cloud native platforms. Platform and Site Reliability Engineering (SRE) teams can integrate Metal³ with GitOps tooling, Continuous Integration and Continuous Deployment (CI/CD) pipelines, and Kubernetes control planes to achieve repeatable, declarative bare metal cluster deployments. The project aligns with the Cloud Native Computing Foundation (CNCF) ecosystem (cloud native infrastructure) and positions itself as a building block for organizations adopting Kubernetes for both workload and infrastructure management.
From a directory and taxonomy perspective, Metal³ fits into categories such as bare metal provisioning, infrastructure automation, Kubernetes ecosystem tooling, and cluster lifecycle infrastructure providers. Its primary role is to bridge physical infrastructure and Kubernetes control planes using CRDs and controllers so that physical machines can be managed through the same declarative interfaces as other cloud native resources.