Fix
The following issues were fixed in 1.36.100-gke.144:
The following issues were fixed in 1.36.100-gke.144:
- Link to Vulnerability fixes for the list of security vulnerabilities addressed in this release.
- Fixed an issue where user clusters repeatedly alternated between reconciling and running states if the management cluster had a different pod density configuration than the user cluster.
- Updated etcd to v3.5.33-0-gke.3 to address security vulnerabilities CVE-2026-46595 and CVE-2026-39821.
- Fixed an issue where updating control plane configurations could cause transient Kubernetes API server downtime. After the fix, the update process strictly verifies that each API server is healthy before restarting subsequent control plane nodes.
- Fixed an issue where deleting a cluster could stall indefinitely in the terminating state due to orphaned machine resources.
- Fixed an issue where worker node pool creation could stall during provisioning in environments with strict network firewall policies. The node pool controller no longer waits for all inventory machines to be ready before declaring the node pool, eliminating a provisioning deadlock.
- Fixed an issue where BareMetalMachine status conditions prematurely reported nodes as ready and available during maintenance mode transitions.
Read the original announcement