What "Production-Ready" Actually Means for a Kubernetes Cluster

It means the cluster passes a concrete checklist rather than possessing some vague quality. You score it across five dimensions — identity and access, network, workload health, observability, and recovery — and a total of 70 or more out of 80 is production-ready.

Five dimensions, eight items each, and every item scored 0 (not addressed), 1 (partially or informally addressed), or 2 (fully addressed and operationally verified). That gives each dimension 0-16 points and a cluster a total out of 80.

70 to 80 is production-ready, 60 to 69 is 'production-soft' — acceptable for non-customer-facing or non-regulated workloads but not for the production workload customers depend on — and below 60 is a demo that shouldn't carry production traffic or PHI. The threshold is somewhat arbitrary; the number's real value is comparing clusters and tracking progress.

That's expected. Most teams score around 50 on their first honest pass, and the honesty is the point. The next quarter's work is moving that 50 to 70, which is where the identity, network-policy, and observability investment lives.

Every six months. Readiness drifts — an item that scored 2 becomes a 1 when a person leaves, a process lapses, or a tool changes — so the score is a leading indicator rather than a one-time certificate.

Share the methodology, not the raw score. The methodology builds trust; the raw number tends to get weaponized in contract negotiations. Making the scorecard part of a cluster's launch criteria also gives engineering, security, and product one explicit gate to point at.