VOL · 05

Kubenix: stronger primitives for cluster definitions

Why we use Kubernetes for the runtime, Kubenix for the spec, and what property testing buys you on top.

Chapters 3

Stub. The chapters that exist are stubs too.

Kubernetes is the right tool for running production workloads because the world doesn’t stand still. Kubenix is the right tool for describing what you want Kubernetes to run, because hand- stitching Helm charts loses the relationships between services that make a cluster more than the sum of its parts.

The booklet covers both halves of that argument and what they unlock together.

Reading order:

  1. Why Kubernetes? Why prescriptive infrastructure tools (Terraform and friends) fray under dynamic systems, and why reconciliation loops don’t.
  2. Why Kubenix? The case for typed primitives over Helm-chart string-stitching — and the headline payoff: horizontal property testing across services.
  3. Property testing Kubenix. Cluster-wide invariants checked at compile time, not after a deploy.
  1. 01
    Why Kubernetes? Why prescribed-once infrastructure tools fray on dynamic systems, and why reconciliation loops don't.
    4 min
  2. 02
    Why Kubenix? The case for typed primitives over Helm-chart string-stitching.
    2 min
  3. 03
    Property testing Kubenix Cluster-wide invariants checked at compile time, not after a deploy.
    1 min