← Back to blog

Early kcore versions were easy to install and nervous to update. 0.7.0 fixes that part, and it is the first release where I would call the whole product ready for real workloads.

One command moves the cluster

kctl update version set v0.7.0 --dry-run
kctl update version set v0.7.0

The controller picks one node as the canary, switches it first, and watches it for a soak window. It looks at the reported version, heartbeats, guest starts, agent errors, and Ceph OSD latency. If the canary is healthy, the rest follow. If not, the canary goes back and the rollout stops.

In-place switches run under a guard timer. A kernel change uses a one-shot boot entry. If the node does not confirm itself in time, it returns to the previous generation without waiting for the controller. The same tag works for a downgrade.

What else is in the cluster

Vault and Provisioning

Two separate paid products now have full docs. kcore Vault keeps encrypted backups that nothing can delete before their retention date, with an offsite copy in an S3 bucket under Object Lock. kcore Provisioning turns racked servers into nodes through the BMC. Read ransomware resistance for what Vault does and does not protect against.

What is still rough

The full list is on the what is new in 0.7.0 page.