Ironic Cube: bringing two worlds together
summary
Metal3 integrates Kubernetes with Ironic and adds concrete pieces: it implements HTTP basic auth for non‑Keystone environments, introduces verify steps to run predeploy checks, and ships a Prometheus exporter for IPMI/Redfish metrics. Ironic gains a JSON‑RPC + single binary mode so no RabbitMQ and a lightweight SQLite local DB option instead of MariaDB. Real hardware issues surface—Redfish virtual media, etag quirks and firmware bugs—and a custom ISO flow forces extendable deployment hooks; most changes work and reduce operator toil.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:37Agenda
- 0:55Overview
- 1:25How they work together
- 1:56Kubernetes
- 2:37Authentication
- 3:56Verify steps
- 5:15Lessons learned
- 5:45Use cases
- 7:03Redfish
- 9:05Redfish Etags
- 10:49Architecture Challenges
- 16:22Perception Challenges
- 21:01Questions
related talks
30mIntroduction To Metal³ — Kubernetes-Native Bare Metal Provisioning
36mIntroducing Metal³: Kubernetes Native Bare Metal Host Management
33mCRI-O Still Loves Kubernetes
28mCNI, CRI, and OCI - Oh My! [I]
24mImage-Based Bare-Metal Provisioning With Metal3.io, Cluster API and…
21mCRI-O: Secure, Performant, and Boring...
26mWhat's New in CRI-O?
31mCRI-O: The Runtime Control Room