Use case

Bring real servers under control before Kubernetes even boots

Kubernetes needs machines that exist, are named consistently, and are ready to image. This use case is about the ground floor: sites, machine records, MAAS inventory, and provisioning workflows that hand off cleanly to the cluster layer.

Get Demo All use cases

You register where servers live, sync metal automation, and trigger installs with clear JSON intent—no mystery scripts.

Who this is for

  • Datacenter or edge technicians coordinating with platform engineers.
  • Teams adopting MAAS or refreshing hardware generations.
  • Anyone tired of “the cluster installer failed” with no idea which NIC was wrong.

The problem (in plain words)

  • Hardware truth lives in tickets while Kubernetes thinks in abstract nodes.
  • Provisioning scripts diverge from what the metal controller actually saw.
  • Storage planning for Ceph starts after disks are already wrong-sized.

How FusioNative makes it easier

  • Infrastructure Management groups sites, machines, and workflows with simple forms.
  • MAAS Engine shows readiness, failures, and fabric work in one journey.
  • Compute Engine picks up once the control plane is live for kubelet-level health.

A simple way to think about the workflow

  1. Step 1. Create or update sites so every machine has a human place name.
  2. Step 2. Add machines with hostname and IP so DNS and automation agree.
  3. Step 3. Sync MAAS and review ready versus failed counts before imaging.
  4. Step 4. Trigger a workflow with explicit CPU/RAM and topology JSON, then join Kubernetes.
Why teams pick this path

Less context switching, clearer next steps

FusioNative keeps clusters, metal, security, and AI signals in one control plane so managers see status and engineers still get technical depth.

Readable for everyone

Executives see health and risk; operators keep kubectl-grade detail one click away.

Honest about gaps

When metrics or agents are missing, the UI says so—no fake green dashboards.

Same habits everywhere

Whether you run edge sites or a central fleet, navigation and language stay consistent.