Google Distributed Cloud air-gapped 1.9.6 release notes

October 4, 2023 [GDC 1.9.6]


Google Distributed Cloud air-gapped 1.9.6 is now released.

See the product overview to learn about the features of Google Distributed Cloud air-gapped.


In the Google Distributed Cloud air-gapped 1.9.6 Addon Manager (ADD) component, the Google Distributed Cloud version is updated to 1.14.8 to apply the latest security patches and important updates.

See Google Distributed Cloud 1.14.8 release notes for details.



Google Distributed Cloud air-gapped 1.9.6 has a known issue where role-based access control (RBAC) and schema settings in the VM manager is stopping users from starting VM backup and restore processes.


Google Distributed Cloud air-gapped 1.9.6 has a known issue where the kube-state-metrics deployment crash loops.


Google Distributed Cloud air-gapped 1.9.6 has a known issue where a worker node is unbalanced after upgrade.


Google Distributed Cloud air-gapped 1.9.6 has a known issue with the upgrade where the GPU device plugin does not start.


Google Distributed Cloud air-gapped 1.9.6 has a known issue where a user cluster with three n2-standard-4 worker nodes has insufficient CPU resources for upgrade.


Google Distributed Cloud air-gapped 1.9.6 has a known issue where upgrade is stuck while terminating a pod.


Google Distributed Cloud air-gapped 1.9.6 has a known issue where a user cluster does not become ready in time to restart the coredns deployment.


An issue with a Heap buffer overflow in WebP in Google Chrome prior to 116.0.5845.187 is fixed. This issue allowed a remote attacker to perform an out of bounds memory write by using a crafted HTML page (Chromium security severity: Critical). This issue usually affects anything that uses frameworks, code libraries, and OSes that incorporate Electron, another code library that uses libwebp, or has libwebp built-in directly.

For more details, see CVE-2023-4863dd.


Google Distributed Cloud air-gapped 1.9.6 has a known issue where alerts in organization system clusters don't reach the ticketing system.