All posts
RELEASEv3.2.3.2September 23, 2026· 2 min read · by VirtConsole

VirtConsole 3.2.3.2

Kubernetes security groups now accept remote groups and IP sets as sources, cluster operations stay reachable over the VPC when you lock down the API load balancer, node pool rotations and the autoscaler are coordinated, and PostgreSQL incremental backups report their real WAL volume.

ShareLink copied

VirtConsole 3.2.3.2 is a full release for both the management server and the hypervisor agent. It closes out a round of Kubernetes networking and reliability fixes found by running node pools against control planes with a locked-down API endpoint.

Kubernetes networking

Security-group rules on Kubernetes cluster pages and load balancer pages now accept remote security groups and IP sets as sources, not just plain CIDRs, so you can scope cluster or LB access to another group of resources instead of a hand-maintained IP list. Remote-group rules also now cover members that only have a VPC address, so a rule pointing at a security group no longer silently misses the VPC-only instances sitting inside it.

Control plane reliability

Platform operations, node joins, pool rotations, autoscaling and drains, now reach the cluster’s control plane over the VPC, so they keep working even after you restrict the API endpoint’s load balancer to your own networks. If one control-plane node stops answering, these operations fail over to another one automatically.

Pool rotations, the autoscaler and the background reconcilers are coordinated so they never act on the same node at once, and a long-running operation keeps its lock for as long as it runs. Stuck-worker recovery, which used to watch only the default pool, now covers every node pool in a cluster.

The Kubernetes Tasks tab is a proper table now, searchable and sortable, with a log drawer per task instead of a raw dump, and a prune action to clear out old completed tasks.

Also in this release

  • PostgreSQL incremental backups now show the actual WAL volume the backup covers, instead of reporting 0 B.
  • A new admin setting lets you list extra platform addresses that guests must always be able to reach, for networks where the built-in defaults aren’t enough.

The Kubernetes networking fixes in this release need the Slave agent 3.2.3.2 on every hypervisor. Update it from the panel’s Update agent action before relying on the new VPC-routed operations and control-plane failover.

Thanks for building on VirtConsole. Questions or trouble along the way, reach us any time.

ReleaseReleaseKubernetesNetworkingBackups
Back to all posts