kcore Provisioning

kcore Provisioning takes a rack of servers with a BMC and turns them into kcore nodes without a keyboard, a USB stick, or a trip to the machine room. It is a separate product from the hypervisor, licensed on its own. It runs next to your cluster and hands finished nodes to it. See the product page for what it is for and how it is licensed. This page is the operator guide.

What it does

Parts

PartRole
kcore-provisioning-controllergRPC API on port 9091: images, machines, boot targets, BMC calls, certificates. State is a local SQLite database.
kcore-provisioning-httpArtifact server: boot loader, per-machine GRUB config, kernel and initrd. HTTPS on 8443, plain HTTP on a second listener for firmware and BMCs that cannot do TLS.
DashboardFleet overview, machine pages, power buttons, drive verdicts, boot configs, DHCP view.
kcore-disk-verifyRuns inside the netboot image for the write, verify, and wipe phases.

From rack to node

  1. Register an image. The controller downloads it, checks its SHA-256, and marks it verified. An unverified image cannot be a boot target.
  2. Discover the machine from its BMC. The inventory stores its identity, NICs, drives, and BMC address.
  3. Run the disk check. Stop here if a drive fails.
  4. Apply a machine profile: the BIOS settings and RAID layout you want. Planning compares the profile with what the BMC reports and lists only the differences, so applying it twice changes nothing the second time.
  5. Set the boot target, configure the BMC to HTTP boot, and power the machine on.
  6. The machine boots kcoreOS. From there it is an ordinary node: kctl node install puts kcore on its disk, and an operator approves it with kctl node approve or in the dashboard. See Add a node.
grpcurl -plaintext -d '{"machine_id":"rack1-07","image_id":"kcoreos-0.7.0","boot_once":true,"restart":true}' \
  localhost:9091 kcore.provisioning.Provisioning/MountVirtualMedia

Every call is also a tool for the MCP server and kctl agent through kcore_rpc. Set connection.provisioning to the controller’s address. Calls that change a machine ask for approval first.

Safety

Hardware and limits

Provisioning is not needed for a lab. One node from the ISO is fine. It earns its place once you have a rack to bring up, rebuild, or re-image.