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
- Discovers hardware. Redfish gives it CPU, memory, drives, NICs, serial number, and BMC firmware. A machine is identified by its serial (the Dell service tag) or any NIC MAC, so MACs do not need to be typed in first.
- Boots it. UEFI HTTP boot, no TFTP. The BMC is told where to fetch the boot loader, the machine asks for its own GRUB config by serial or MAC, and then pulls the kernel and initrd of a verified kcoreOS image.
- Controls power. On, off, reset, and one-time boot override over Redfish. IPMI is there for BMCs that do not speak Redfish.
- Configures it. BIOS attributes, RAID volumes, non-RAID mode, and virtual media (mount an ISO, boot once, restart) through the BMC.
- Checks the disks. A write, power-cycle, verify run on every drive, with a verdict per drive. An optional wipe runs only after every disk verified.
- Issues node certificates. It has its own CA, so a node enrols with a certificate from the start.
- Serves DHCP and DNS records. A network provisioner drives Kea and PowerDNS: networks, reservations, leases, and records. The dashboard shows subnets, leases, and reservations.
Parts
| Part | Role |
|---|---|
kcore-provisioning-controller | gRPC API on port 9091: images, machines, boot targets, BMC calls, certificates. State is a local SQLite database. |
kcore-provisioning-http | Artifact 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. |
| Dashboard | Fleet overview, machine pages, power buttons, drive verdicts, boot configs, DHCP view. |
kcore-disk-verify | Runs inside the netboot image for the write, verify, and wipe phases. |
From rack to node
- Register an image. The controller downloads it, checks its SHA-256, and marks it verified. An unverified image cannot be a boot target.
- Discover the machine from its BMC. The inventory stores its identity, NICs, drives, and BMC address.
- Run the disk check. Stop here if a drive fails.
- 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.
- Set the boot target, configure the BMC to HTTP boot, and power the machine on.
- The machine boots kcoreOS. From there it is an ordinary node:
kctl node installputs kcore on its disk, and an operator approves it withkctl node approveor 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
- The controller authenticates with mTLS client certificates, falls back to a bearer token, and checks roles. Every operation is written to an audit log.
- Anything that destroys data (
ConfigureRaid,SetBiosAttributes,StartDiskCheckwith a wipe) needsconfirm: true. - BMC credentials come from the controller’s environment, not from machine records.
- Input is validated before it reaches a BMC or the file system: MACs, IPs, identifiers, and paths. Image downloads are capped at 50 GB.
- A disk-check run carries a random token in its report URL. Keep the artifact listener on an isolated VLAN, because anyone on the provisioning network can read a boot config.
Hardware and limits
- The boot path is tested end to end on Dell PowerEdge T140 (iDRAC 9). Other Redfish BMCs get discovery, power, and boot control. BIOS, RAID, and virtual media are Dell iDRAC only.
- Virtual media needs an iDRAC Enterprise or Datacenter licence.
- It installs kcoreOS only. It is not a general OS provisioner.
- One controller, one SQLite database. There is no HA for the provisioning plane itself. Running nodes do not depend on it.
- No firmware updates, and no burn-in beyond the disk check.
- The gRPC listener on 9091 is plain by default in the examples. Put it on a management network or turn on mTLS.
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.