The 38-point Cluster Health Checklist
The exact list we work through in a paid audit. Quorum and fencing, failure domains, backup restorability, upgrade paths, GPU allocation idleness.
Get the checklist →Most of what we publish is the answer to a question a customer asked. No gated whitepapers written by marketing, no "10 trends" listicles. Just the engineering, including the parts where the conventional answer is wrong.
The exact list we work through in a paid audit. Quorum and fencing, failure domains, backup restorability, upgrade paths, GPU allocation idleness.
Get the checklist →Fencing and STONITH, explained by the failures they prevent. If your cluster cannot fence its peer, it is not highly available.
The placement rules that decide durability and rebalance behaviour — and the three configurations that show up in almost every broken cluster.
What each one actually guarantees, where each one fails, and which topology fits which constraint.
Dynamic Resource Allocation replaces the device plugin model. What that changes for scheduling, sharing and multi-tenancy.
Gang scheduling, topology awareness, and why the dividing line is about job shape rather than ideology.
Control plane pricing is public. Everything that makes the number real is not. Here is the model to fill in with your own figures.
Wave planning, rollback rehearsal, validation. Written from migrations we have actually run.
A real drill report, published with the numbers, including the parts that went worse than expected.
A method for timing restores, and why "the backup job succeeded" is the most dangerous sentence in infrastructure.
The package list, kernel parameters, networking and storage choices we start from, with reasoning.
A line-by-line comparison of what a managed contract includes versus the hours it displaces.
The exact list we work through during a paid audit: quorum and fencing, storage failure domains, backup restorability, upgrade paths, certificate expiry, GPU allocation idleness, and the eleven things that most often turn out to be wrong.
That's fine. Download it, use it, and if it finds something you'd rather not fix yourself, we're easy to reach.