Core infrastructure
Under Core Infrastructure → Infrastructure, operators model physical reality before Kubernetes namespaces matter: logical sites, enrolled machines, optional Ceph OSD candidate counts, and JSON-driven provisioning workflows—MAAS-ready when your metal fabric is wired in.
Screenshots from the live product. Each note explains what you are looking at and when you would open this screen.
Sites, machines, MAAS, and provisioning workflows. This is the same interface your team uses in production.
Click the screenshot to open full size, zoom, and pan.
Infrastructure Management prevents “cluster sprawl on imaginary machines” by forcing sites, IPs, and workflow payloads to agree before automation promotes builds into production namespaces.
JSON workflows capture CPU/RAM envelopes and topology counts—easy to diff when finance asks why nodes doubled.
Sites map neatly into MAAS regions so networking and facilities teams talk about the same coordinates.
OSD candidate counts surface early—operators stop guessing whether Ceph can absorb the next tenant burst.