← All features
KUBERNETES · DEEP DIVE

Node Pools

Mix node shapes inside one cluster: a small general pool, a GPU pool and a memory pool side by side, each with its own plan, labels, taints and autoscaling bounds.

app.virtconsole.com/kubernetes/clusters/prod/pools
VirtConsole node pools screen showing multiple pools with different plans, labels and taints
01

Per-pool everything

Each pool is its own scaling and scheduling unit.

Plan-defined sizing

Workers run on the instance plans you already sell. CPU, RAM, storage and network limits come from the plan.

Labels & taints

NoSchedule, PreferNoSchedule or NoExecute per pool, pushed to every worker. Renaming a pool heals the labels on the next reconciliation.

Autoscaling bounds

Min and max per pool, enforced strictly. A GPU pool can sit at 0 until a workload demands it.

02

Pool identity

Know which node belongs where, in kubectl and in the panel.

Node-pool label

Workers carry a node-pool label following the convention major managed providers use, visible with kubectl get nodes -L.

Named hostnames

Panel hostnames include the pool name, so instance lists never show several pools of identically shaped names.

Per-node inspection

Click into any node for CPU and memory donuts, pod-level utilisation and top consumers.

03

Plan rotation

Change a pool’s plan while it runs. No scale-to-zero, no capacity outage.

Surge waves

New workers on the new plan provision and confirm ready first, then old ones cordon, drain and destroy, one wave at a time.

Drift visibility

A badge counts workers still on the previous plan, with a one-click Rotate now action.

Deliberate downsizing

Rotating to a smaller plan takes a second, separate confirmation naming the consequence. One click can never start one.

04

Lifecycle safety

The failure modes are handled, not hoped away.

Graceful drain

Cordon, evict within a configurable grace period, respect PodDisruptionBudgets, then delete the VM.

Self-healing rotations

A rotation stuck at pending is redispatched by the janitor. Rotations are resume-safe by design.

No stranded workers

Pool deletion marks every member for collection and refuses to remove the pool record if any live member could not be marked.

Deeper look

Pools sit inside the cluster they belong to

Node pool shapes, labels and taints alongside the control plane and worker inventory of the same cluster.

app.virtconsole.com/kubernetes/clusters/prod
VirtConsole Kubernetes cluster detail page with control plane status, node pools and worker inventory

Node pools in context: one cluster, control plane and workers together

More of the platform

Try it on your own hardware

Free 30-day trial. Every feature included. No credit card required.

View pricing