metal3-io/metal3-dev-env

Metal³ Development Environment

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

metal3-io/metal3-dev-env has 100+ stars and 100+ forks on GitHub, is written in Shell, and was last pushed on Oct 12, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on May 1st, 2019
Open Issues & Pull Requests: 28 (+0)
GitHub issues: Enabled
Number of forks: 135
Total Stargazers: 131 (+0)
Total Subscribers: 9 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.3 hours
Mean response time: 8.3 days
90th percentile: 12.0 days
Tracked items: 29

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 868 days
Stale 30+ days: 8
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • triage/accepted (28)
  • help wanted (11)
  • lifecycle/frozen (7)
  • kind/bug (6)
  • good first issue (5)
  • kind/feature (5)
  • kind/ci (3)
  • lifecycle/stale (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Metal³ Development Environment is a collection of shell scripts that sets up a local development environment for Metal³, a Kubernetes-native bare metal provisioning project.

The project solves the problem of bootstrapping a complex multi-component development setup by automating the deployment of a Minikube cluster alongside virtualized target hosts. It handles the provisioning of the necessary infrastructure, including configuration of hypervisors, networking, and the Metal³ stack components, allowing developers to test bare metal provisioning workflows locally without manual infrastructure setup.

Developers should use this tool if they are working on Metal³ components such as Cluster API Provider Metal³, Baremetal Operator, or IPAM, and need an isolated environment to test provisioning logic. The tool supports multiple target operating systems including Ubuntu and CentOS, with different resource requirements depending on the chosen distribution. The environment can be deployed using standard scripts or through Tilt for local development of CAPI, BMO, CAPM3, and IPAM components. The README explicitly warns that these scripts are invasive and will reconfigure the host OS, making it strongly recommended to run the environment in a virtual machine rather than on a production system.

The project maintains active testing across multiple release branches, with a defined test matrix covering different versions of CAPM3, IPAM, Baremetal Operator, Ironic, and IPA components. Development activity spans support for current and previous release branches, indicating ongoing maintenance of multiple versions in parallel. The project provides detailed documentation through external references and maintains configuration for different hypervisor options, including experimental QEMU support alongside the default KVM setup.