The kubeconfig problem, removed
Every Kubernetes estate eventually leaks a kubeconfig: a laptop image, a CI log, a shared drive. If that file carries a static token, the leak is a standing door into the cluster. ProjectX Kubernetes mints a short-lived kubeconfig from your identity on demand, bound to the principal — a leaked file stops working instead of opening the door.
What you get
- Managed clusters with the control plane run for you, on the upstream that serves your region — or self-managed on our own metal for bare-metal economics, with an identical lifecycle either way.
- Access minted per person from the identity pillar: no static tokens, nothing standing to steal.
- Upgrades one minor version at a time with the source version recorded, so a rollback returns to exactly where you started.
- Node pools that cordon and drain before nodes disappear, so work reschedules instead of dying.
Why it matters
Cluster access is usually the widest standing credential in a company. Binding it to identity means an access review covers the cluster too, offboarding closes it with everything else, and a leaked file is a non-event.