Releases
AI-analyzed release notes for CNCF graduated and incubating projects.
metal3-io v0.13.0 drops the iRMC driver, deprecates BMH firmware spec, and ships HostClaim CRDs plus multi-arch PXE boot — a release with real breaking changes that demand pre-upgrade review.
breakingAudit iRMC usage and BMH.Spec.Firmware fields before upgrading
The iRMC driver is gone — any BareMetalHost resources targeting iRMC BMC endpoints will stop reconciling after upgrade. Separately, BMH.Spec.Firmware is now deprecated; while it won't immediately break, you should plan migration to the replacement API. Scan your BMH manifests and Helm values for both before touching production.
breakingVerify CAPI and controller-runtime compatibility in your management cluster
The jump to CAPI v1.13.1 and controller-runtime v0.23.3 is not trivial. If you run other CAPI providers alongside metal3, check their compatibility matrices now. A version mismatch between providers sharing the same management cluster can cause subtle CRD conflicts or webhook failures at runtime.
enhancementAdopt HostClaim CRDs for declarative bare-metal host allocation
HostClaim and HostClaimSet resources give you a Kubernetes-native way to request and reserve bare-metal capacity without writing custom controllers. If you're currently managing host allocation through scripts or external tooling, evaluate whether HostClaim covers your use case — it's now feature-complete enough to replace simple reservation workflows.
Key changes (5)
- iRMC driver removed entirely; BMH.Spec.Firmware deprecated — clusters using either must migrate before upgrading
- CAPI bumped to v1.13.1, controller-runtime to v0.23.3, k8s group to v0.35.4 — dependency chain has shifted substantially
- New HostClaim and HostClaimSet CRDs with Association logic now available for declarative host reservation workflows
- Multi-architecture PXE boot support added, covering both x86_64 and aarch64 workloads
- Per-host pull secrets for external OCI registries and forced Ironic host detachment are now supported