Kubius · StatefulSets

Manage StatefulSets without the footguns

StatefulSets are fussier than Deployments - ordered pods, partitions, per-replica volumes. Kubius lays out the ordinal pods, the update strategy and partition, and each replica's PVC, so scaling and rollouts are less nerve-wracking.

Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later

The state that makes StatefulSets tricky, visible

Ordinal pods, in order

See pods by ordinal with their ready state, so you know exactly where an ordered rollout has got to.

Scale carefully

Change the replica count with a stepper and a clear before/after, mindful that ordinal scale-down removes the highest ordinals.

Rollout restart

Cycle pods with a rolling restart, respecting the StatefulSet's ordered update behaviour.

Per-replica volumes

Each replica's PersistentVolumeClaim is shown, so you can see the storage that scaling and deletion will (or won't) touch.

Update strategy & partition

The update strategy, and any rollout partition, are surfaced - so a partitioned canary rollout is obvious, not hidden in YAML.

Live status

Ready and updated replica counts update in real time as an ordered rollout proceeds.

Simple, one-time pricing

Pay once. No subscription.

One-time licence from €49 - no subscription. 14-day free trial, no card required.

Free 14-day trial · macOS Sonoma (14) or later · No agents, nothing to install in-cluster

Questions, answered

How does Kubius handle StatefulSet quirks?

It shows the ordinal pods in order with their ready state, the update strategy and any partition, and each replica's PVC - the things that make StatefulSets riskier to scale and roll out than Deployments.

Can I scale and restart a StatefulSet?

Yes - scale with a stepper and trigger a rolling restart, both through the API. Kubius surfaces the StatefulSet's ordered-update behaviour so there are no surprises.

Can I see the volumes attached to each replica?

Yes. Each replica's PersistentVolumeClaim is shown, so you know what storage is in play before scaling down or deleting.

Do I need kubectl?

No - all of this goes directly through the Kubernetes API with your kubeconfig.

Handle StatefulSets with confidence