[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[[["\u003cp\u003eGoogle Distributed Cloud (GDC) air-gapped 1.13.4 is now available, offering new features as detailed in the product overview.\u003c/p\u003e\n"],["\u003cp\u003eThe Ubuntu OS image has been updated to version 20240903, and the Rocky OS image has been updated to version 20240906, both to address multiple security vulnerabilities, requiring nodes to be upgraded to obtain the fixes.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Distributed Cloud for bare metal has been updated to version 1.29.400-gke.86, which includes the latest security patches and important updates, detailed in the release notes.\u003c/p\u003e\n"],["\u003cp\u003eSeveral issues have been identified, including an error with IPsec configuration in block storage, a locked GDU service, and upgrade issues with the \u003ccode\u003eNodeUpgradeTask\u003c/code\u003e CR and \u003ccode\u003emeta-monitoring\u003c/code\u003e addon.\u003c/p\u003e\n"],["\u003cp\u003eSeveral issues have been resolved across block storage, cluster management, identity and access management, physical servers, virtual machines, and Vertex AI, enhancing the overall stability and functionality of the platform.\u003c/p\u003e\n"]]],[],null,["# Google Distributed Cloud air-gapped 1.13.4 release notes\n\n\u003cbr /\u003e\n\nOctober 4, 2024\n---------------\n\n*** ** * ** ***\n\nGoogle Distributed Cloud (GDC) air-gapped 1.13.4 is available. \nSee the [product overview](/distributed-cloud/hosted/docs/latest/gdch/overview) to learn about the features of Distributed Cloud.\n\n*** ** * ** ***\n\nUpdated the Ubuntu OS image version to 20240903 to apply the latest security patches and important updates.\n\n\u003cbr /\u003e\n\nTo take advantage of the bug and security vulnerability fixes, you must upgrade all nodes with each release.\n\nThe following security vulnerabilities are fixed:\n\n- [CVE-2021-46926](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46926)\n- [CVE-2022-48174](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48174)\n- [CVE-2023-40546](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40546)\n- [CVE-2023-40547](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40547)\n- [CVE-2023-40548](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40548)\n- [CVE-2023-40549](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40549)\n- [CVE-2023-40550](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40550)\n- [CVE-2023-40551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40551)\n- [CVE-2023-42667](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-42667)\n- [CVE-2023-49141](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49141)\n- [CVE-2023-52629](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52629)\n- [CVE-2023-52760](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52760)\n- [CVE-2024-2201](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-2201)\n- [CVE-2024-2511](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-2511)\n- [CVE-2024-4741](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4741)\n- [CVE-2024-5535](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-5535)\n- [CVE-2024-24853](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-24853)\n- [CVE-2024-24860](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-24860)\n- [CVE-2024-24980](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-24980)\n- [CVE-2024-25939](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-25939)\n- [CVE-2024-26830](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26830)\n- [CVE-2024-26921](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26921)\n- [CVE-2024-26929](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26929)\n- [CVE-2024-36901](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36901)\n- [CVE-2024-39484](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39484)\n- [CVE-2024-40897](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40897)\n\n*** ** * ** ***\n\nUpdated the Rocky OS image version to 20240906 to apply the latest security patches and important updates.\n\n\u003cbr /\u003e\n\nTo take advantage of the bug and security vulnerability fixes, you must upgrade all nodes with each release.\n\nThe following security vulnerabilities are fixed:\n\n- [CVE-2021-35937](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35937)\n- [CVE-2021-35938](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35938)\n- [CVE-2021-35939](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35939)\n- [CVE-2021-41072](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41072)\n- [CVE-2023-3758](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3758)\n- [CVE-2024-1737](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-1737)\n- [CVE-2024-1975](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-1975)\n- [CVE-2024-4076](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4076)\n- [CVE-2024-6345](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-6345)\n- [CVE-2024-32487](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-32487)\n\n*** ** * ** ***\n\nThe following issues are identified:\n\n**Block storage**:\n\n- The IPsec configuration has an error.\n\n**Object storage**:\n\n- The `ObjectStorageStorageNodeReconciler` reports that the GDU service is locked.\n\n**Upgrades**:\n\n- `NodeUpgradeTask` CR is stuck at the `NodeOSInPlaceUpgradePostProcessingCompleted` condition.\n- The `meta-monitoring` addon fails due to the strongswan location being in a different runtime directory.\n\n*** ** * ** ***\n\nThe following issues are fixed:\n\n**Upgrades**:\n\n- The node upgrade is stuck on `maintenanceMode false`. ---\n\n**Block storage**:\n\n- Fixed the issue with Grafana pods stuck in `Init` state due to volume mount errors.\n- Fixed the issue with a Trident multi-attach error.\n\n**Cluster management**:\n\n- Fixed the issue with the `GPUAllocation` for a shared service cluster not configured correctly.\n\n**Identity and access management**:\n\n- Fixed the issue with the `gatekeeper-audit` pods in the `opa-system` namespace frequently restarting.\n\n**Physical servers**:\n\n- Fixed the issue with servers stuck in a provisioning state.\n\n**Upgrade**:\n\n- Fixed the issue with the root org upgrade being stuck on a failed signature job.\n - Fixed the issue where the tenant organization upgrade fails at the preflight check stage with `ErrImagePull`.\n\n**Virtual machines**:\n\n- Fixed the issue where a BYO image import fails for qcow2 and raw images.\n- Fixed the issue where provisioning a disk from an image fails.\n\n**Vertex AI**:\n\n- Fixed the issue where the Operable Component Lifecycle Management (OCLCM) controller for Vertex AI subcomponents shows errors during upgrades from version 1.9.x to 1.13.3.\n- Fixed the issue where Translation requests with more than 250 characters crash `translation-prediction-server` pods.\n\n*** ** * ** ***\n\nThe following changes are identified:\n\n**Version updates**:\n\n- The Google Distributed Cloud for bare metal version is updated to 1.29.400-gke.86 to apply the latest security patches and important updates. \n\n See the [Google Distributed Cloud for bare metal 1.29.400-gke.86 release notes](https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/release-notes-ver-1#release_129400-gke86) for details."]]