在 Google Distributed Cloud air-gapped 1.9.3 使用者介面 (UI) 元件中,透過 UI 建立 VM 時,可將從快照還原的磁碟做為開機磁碟。
在 Google Distributed Cloud air-gapped 1.9.3 身分與存取權管理 (IAM) 元件中,啟用升級的預先定義角色不再需要手動變更。預先定義的角色資訊清單會覆寫所有手動變更。
Google Distributed Cloud 實體隔離方案 1.9.3 版解決了在防火牆 (FW) 元件中輪替管理員憑證時,防火牆管理員帳戶遭到鎖定的問題。
Google Distributed Cloud 實體隔離設備 1.9.3 版修正了 LOG 元件中,將作業記錄匯出至 Splunk 的問題。
Google Distributed Cloud air-gapped 1.9.3 有已知問題,VM 管理員中的角色型存取控管 (RBAC) 和結構定義設定會導致使用者無法啟動 VM 備份和還原程序。
Google Distributed Cloud air-gapped 1.9.3 有一項已知問題,即在將 gpu-org-system-cluster 從 1.9.1 升級至 1.9.2 時,vm-runtime 外掛程式會停滯,因為 kubevm-gpu-driver-daemonset Pod 處於 CrashLoopBackOff 狀態。
Google Distributed Cloud 實體隔離方案 1.9.3 解決了 UNET 元件中的內部負載平衡器 (ILB) 服務問題。1.9.0 至 1.9.2 版含有錯誤,導致內部負載平衡器 (ILB) 服務獲派外部 IP,而非內部 IP。影響是外部負載平衡器 IP 集區會更快用完,因為 ILB 服務會從這個集區取得位址。不過,指派給 ILB 服務的 IP 並未在機構外部宣傳,因此服務仍屬於機構內部。這個錯誤已在 1.9.3 中修正,因此 ILB 服務會指派內部 IP。
Google Distributed Cloud air-gapped 1.9.3 有個已知問題,使用者叢集無法及時就緒。
Google Distributed Cloud air-gapped 1.9.3 有已知問題,導致外掛程式安裝失敗。
Google Distributed Cloud 實體隔離方案 1.9.3 有一項已知問題,即 OrganizationUpgrade 狀態不會更新。
Google Distributed Cloud air-gapped 1.9.3 有已知問題,使用者叢集升級作業無法呼叫 Webhook。
Google Distributed Cloud air-gapped 1.9.3 有一項已知問題,即車隊管理員控制器會陷入當機迴圈,且記錄檔中會出現 Fleet admin controller manager stopped: failed to wait for auditloggingtarget caches to sync: timed out waiting for cache to be synced 錯誤。
Google Distributed Cloud air-gapped 1.9.3 有個已知問題,即系統叢集無法及時就緒。
Google Distributed Cloud air-gapped 1.9.3 無法為根管理員叢集設定 AddOn 選取器標籤。
Google Distributed Cloud air-gapped 1.9.3 的 UI 有已知問題,會允許您選取不相容的 GPU 與 VM 類型配對。
Google Distributed Cloud air-gapped 1.9.3 有已知問題,如果 VM 的記憶體大於 32 GB,由於 QEMU 額外負擔計算錯誤,因此需要記憶體覆寫。
Google Distributed Cloud 氣隙隔離 1.9.3 有已知問題,kube-state-metrics 部署作業會進入當機迴圈。
Google Distributed Cloud air-gapped 1.9.3 有個已知問題,就是機構系統叢集中的快訊不會傳送至票證系統。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eGoogle Distributed Cloud air-gapped 1.9.3 is now available, introducing enhancements such as self-healing Kubernetes objects for AuditLoggingTargets and a UI message indicating the maximum worker node amount during cluster creation.\u003c/p\u003e\n"],["\u003cp\u003eThis version updates the Google Distributed Cloud version to 1.14.4-gke.4 to incorporate the latest security patches and critical updates, while also addressing 46 container image security vulnerabilities.\u003c/p\u003e\n"],["\u003cp\u003eThe new user interface allows disks restored from snapshots to be used as boot disks for VM creation, and it is no longer possible to make manual changes to predefined roles as they will be overriden.\u003c/p\u003e\n"],["\u003cp\u003eSeveral issues have been resolved, including a firewall admin account lock-out problem during credential rotation, the operational log export issue to Splunk, and a bug causing internal load balancer services to be assigned external IPs, along with many known issues that remain.\u003c/p\u003e\n"],["\u003cp\u003eSome of the many known issues include: issues with the VM manager, add-ons, upgrades, the fleet admin controller, system clusters, setting AddOn selector labels, incompatible coupling of GPU to VM types, memory overrides on VMs with 32GB or more, \u003ccode\u003ekube-state-metrics\u003c/code\u003e deployments, and alerts in the organization system clusters not reaching the ticketing system.\u003c/p\u003e\n"]]],[],null,["# Google Distributed Cloud air-gapped 1.9.3 release notes\n\n\u003cbr /\u003e\n\nApril 28, 2023 \\[GDC 1.9.3\\]\n----------------------------\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 is now released.\n\nSee the [product overview](/distributed-cloud/hosted/docs/latest/gdch/overview) to learn about the features of Google Distributed Cloud air-gapped.\n\n*** ** * ** ***\n\n\nThe Google Distributed Cloud air-gapped 1.9.3 audit logging (AL) operable component introduces an enhancement for AuditLoggingTargets. Kubernetes objects created by an AuditLoggingTarget CR are now self-healed if they are updated or deleted.\n\n*** ** * ** ***\n\n\nUpdated Google Distributed Cloud version to 1.14.4-gke.4 to apply the latest security patches and important updates.\n\nSee [the Google Distributed Cloud release notes](https://cloud.google.com/anthos/clusters/docs/bare-metal/latest/release-notes-ver) for the latest information.\n\n*** ** * ** ***\n\n\nThe Google Distributed Cloud air-gapped 1.9.3 user interface (UI) now includes a message to inform you about the maximum worker node amount with the current control plane setting and pod CIDR option when you create a cluster.\n\n*** ** * ** ***\n\n\nThe following container image security vulnerabilities are fixed:\n\n- [CVE-2021-46848](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46848)\n- [CVE-2022-1354](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1354)\n- [CVE-2022-1355](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1355)\n- [CVE-2022-2056](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2056)\n- [CVE-2022-2057](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2057)\n- [CVE-2022-2058](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2058)\n- [CVE-2022-2097](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2097)\n- [CVE-2022-23521](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23521)\n- [CVE-2022-24765](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24765)\n- [CVE-2022-2867](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2867)\n- [CVE-2022-2868](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2868)\n- [CVE-2022-2869](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2869)\n- [CVE-2022-29187](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29187)\n- [CVE-2022-32221](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32221)\n- [CVE-2022-34526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34526)\n- [CVE-2022-3570](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3570)\n- [CVE-2022-3597](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3597)\n- [CVE-2022-3598](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3598)\n- [CVE-2022-3599](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3599)\n- [CVE-2022-3626](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3626)\n- [CVE-2022-3627](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3627)\n- [CVE-2022-3970](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3970)\n- [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253)\n- [CVE-2022-39260](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39260)\n- [CVE-2022-41903](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41903)\n- [CVE-2022-42898](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42898)\n- [CVE-2022-4304](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4304)\n- [CVE-2022-4450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4450)\n- [CVE-2022-4645](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4645)\n- [CVE-2022-48281](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48281)\n- [CVE-2023-0215](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0215)\n- [CVE-2023-0286](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0286)\n- [CVE-2023-0361](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0361)\n- [CVE-2023-0795](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0795)\n- [CVE-2023-0796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0796)\n- [CVE-2023-0797](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0797)\n- [CVE-2023-0798](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0798)\n- [CVE-2023-0799](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0799)\n- [CVE-2023-0800](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0800)\n- [CVE-2023-0801](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0801)\n- [CVE-2023-0802](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0802)\n- [CVE-2023-0803](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0803)\n- [CVE-2023-0804](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0804)\n- [CVE-2023-26604](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-26604)\n\n*** ** * ** ***\n\n\nIn the Google Distributed Cloud air-gapped 1.9.3 user interface (UI) component, VM creation using UI allows disks restored from a snapshot to serve as boot disks.\n\n*** ** * ** ***\n\n\nIn the Google Distributed Cloud air-gapped 1.9.3 identity and access management (IAM) component, predefined roles enabled for upgrades are no longer subject to manual changes. Predefined role manifests override any manual changes.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 resolves the Firewall admin account lock out issue while rotating the admin credentials in the firewall (FW) component.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 fixes export of operational logs to Splunk in the LOG component.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 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.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue where the `vm-runtime` addon is stuck during the upgrade of the `gpu-org-system-cluster` from 1.9.1 to 1.9.2 because the `kubevm-gpu-driver-daemonset` pods are in the `CrashLoopBackOff` state.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 resolves an internal load balancer (ILB) services issue in the UNET component. Releases 1.9.0 - 1.9.2 contained a bug where internal load balancer (ILB) services were assigned an external IP instead of an internal IP. The impact is that the external load balancer IP pool is used more quickly as ILB services take addresses from this pool. However, the IPs assigned to ILB services were not advertised outside of the org, so the service remained internal to the org. This bug is fixed in 1.9.3 so that ILB services are assigned internal IPs.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue where a user cluster does not become ready in time.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue where an add-on installation fails.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue where an `OrganizationUpgrade` status does not get updated.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue where a user cluster upgrade fails to call webhooks.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue where a fleet admin controller gets stuck in a crash loop with the `Fleet admin controller manager stopped: failed to wait for auditloggingtarget caches to sync: timed out waiting for cache to be synced` error in the logs.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue where a system cluster does not become ready in time.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 is unable to set AddOn selector labels for the root admin cluster.\n\n*** ** * ** ***\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue in the UI that lets you select an incompatible coupling of GPU to VM type.\n\n*** ** * ** ***\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue where VMs with memory greater than 32 GB require a memory override due to an incorrect QEMU overhead calculation.\n\n*** ** * ** ***\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known\nissue where the `kube-state-metrics` deployment crash loops.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.3 has a known issue where alerts in organization system clusters don't reach the ticketing system."]]