# baremetal-operator **Repository Path**: kubemetal/baremetal-operator ## Basic Information - **Project Name**: baremetal-operator - **Description**: Bare metal host provisioning integration for Kubernetes - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2020-11-28 - **Last Updated**: 2020-12-19 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # Bare Metal Operator [![Ubuntu V1alpha4 build status](https://jenkins.nordix.org/view/Airship/job/airship_master_v1a4_integration_test_ubuntu/badge/icon?subject=Ubuntu%20E2E%20V1alpha4)](https://jenkins.nordix.org/view/Airship/job/airship_master_v1a4_integration_test_ubuntu/) [![CentOS V1alpha4 build status](https://jenkins.nordix.org/view/Airship/job/airship_master_v1a4_integration_test_centos/badge/icon?subject=CentOS%20E2E%20V1alpha4)](https://jenkins.nordix.org/view/Airship/job/airship_master_v1a4_integration_test_centos/) The Bare Metal Operator implements a Kubernetes API for managing bare metal hosts. It maintains an inventory of available hosts as instances of the `BareMetalHost` Custom Resource Definition. The Bare Metal Operator knows how to: * Inspect the host’s hardware details and report them on the corresponding `BareMetalHost`. This includes information about CPUs, RAM, disks, NICs, and more. * Provision hosts with a desired image * Clean a host’s disk contents before or after provisioning. More capabilities are being added regularly. See open issues and pull requests for more information on work in progress. For more information about Metal³, the Bare Metal Operator, and other related components, see the [Metal³ docs](https://github.com/metal3-io/metal3-docs). ## Resources * [API documentation](docs/api.md) * [Setup Development Environment](docs/dev-setup.md) * [Configuration](docs/configuration.md) * [Testing](docs/testing.md) * [Publishing Images](docs/publishing-images.md) ### Important Notes Whenever there is a change in `config/` directory, please remember to run the following command: `make manifests` This will render the `config/render/capm3.yaml`. Please do not change the content of `config/render/capm3.yaml` manually.