Google Distributed Cloud for bare metal 1.35.200-gke.66 released
Google Distributed Cloud (software only) for bare metal version 1.35.200-gke.66 is now available, running on Kubernetes v1.35.3-gke.400. This release addresses multiple critical issues, including vulnerabilities, node taint/label persistence problems, etcd pod initialization failures, and control plane certificate rotation stalls. The update also improves resiliency for API errors during the machine initialization phase. Users planning to upgrade should verify storage vendor compatibility and be aware of the typical 7-14 day rollout period for API clients.
Fixes (1) ›
- Google Distributed Cloud (software only) for bare metal
The following issues were fixed in 1.35.200-gke.66: Fixed vulnerabilities listed in Vulnerability fixes . Fixed an issue where a transient or partial failure during node pool updates could cause node taints or labels to become permanently stuck (stranded) on worker nodes, even after you removed them from the NodePool custom resource specification. Fixed an issue where, during the machine initialization phase, the etcd-events pod read the stale data directory when it started and attempted to reuse the old member ID to rejoin the cluster instead of the new one. Trying to use the old member ID to
Notes (1) ›
- Google Distributed Cloud (software only) for bare metal
Google Distributed Cloud (software only) for bare metal 1.35.200-gke.66 is now available for download. To upgrade, see Upgrade clusters . Google Distributed Cloud for bare metal 1.35.200-gke.66 runs on Kubernetes v1.35.3-gke.400. After a release, it takes approximately 7 to 14 days for the version to become available for installations or upgrades with the GKE On-Prem API clients: the Google Cloud console, the gcloud CLI, and Terraform. If you use a third-party storage vendor, check the Google Distributed Cloud-ready storage partners document to make sure the storage vendor has already passed t
https://docs.cloud.google.com/release-notes#June_16_2026