kcore Provisioning

Racked servers become kcore nodes without a keyboard, a USB stick, or a trip to the machine room. It talks to the BMC and hands finished nodes to your cluster.

What it does

Discovers

Redfish returns CPU, memory, drives, NICs, serial number, and BMC firmware. A machine is known by serial or any NIC MAC.

Boots

UEFI HTTP boot, no TFTP. The machine fetches a per-machine GRUB config and a checksummed kcoreOS image.

Controls power

On, off, reset, and one-time boot override over Redfish. IPMI for BMCs that do not speak Redfish.

Configures

BIOS attributes, RAID volumes, non-RAID mode, and virtual media. Planning shows the difference before it applies.

Checks disks

Write, power-cycle, verify on every drive, with a verdict each. An optional wipe runs only after all drives verified.

Runs the network

Kea and PowerDNS for the networks it owns: reservations, leases, and records, with a view in the dashboard.

From rack to node

  1. Register an image. The controller checks its SHA-256. An unverified image cannot be a boot target.
  2. Discover the machine from its BMC.
  3. Run the disk check. Stop if a drive fails.
  4. Apply a machine profile for BIOS and RAID.
  5. Boot kcoreOS, install, and approve the node into the cluster with kctl.

Limits