[[["容易理解","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.5 has been released, with the Addon Manager (ADD) component updated to version 1.14.6 for the latest security patches and updates.\u003c/p\u003e\n"],["\u003cp\u003eThis release addresses numerous container image security vulnerabilities, including multiple CVEs ranging from 2020 to 2023, enhancing the system's overall security.\u003c/p\u003e\n"],["\u003cp\u003eThe release resolves an issue in AddOn component where the ClamAV runner was not properly handling SIGTERM signals, and also fixes a bug from prior versions where long Project names caused the Monitoring stack to fail.\u003c/p\u003e\n"],["\u003cp\u003eThere are several known issues in this version, such as RBAC and schema settings impacting VM backup and restore processes, certificate authority mismatches, insufficient CPU resources in certain user cluster configurations for upgrades, pod termination causing upgrade failures, and other operational issues.\u003c/p\u003e\n"],["\u003cp\u003eThe release also fixes a bug that affected the execution of disaster recovery of HSM backups.\u003c/p\u003e\n"]]],[],null,["# Google Distributed Cloud air-gapped 1.9.5 release notes\n\n\u003cbr /\u003e\n\nAugust 2, 2023 \\[GDC 1.9.5\\]\n----------------------------\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.5 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\nIn the Google Distributed Cloud air-gapped 1.9.5 Addon Manager (ADD) component, the Google Distributed Cloud version is updated to 1.14.6 to apply the latest security patches and important updates.\n\nSee [Google Distributed Cloud 1.14.6 release notes](https://cloud.google.com/anthos/clusters/docs/bare-metal/1.14/release-notes-ver#release_1146) for details.\n\n*** ** * ** ***\n\nThe following container image security vulnerabilities are fixed:\n\n- [CVE-2020-11080](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11080)\n- [CVE-2021-39537](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39537)\n- [CVE-2022-1050](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1050)\n- [CVE-2022-4144](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4144)\n- [CVE-2023-0330](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0330)\n- [CVE-2023-1380](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1380)\n- [CVE-2023-1523](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1523)\n- [CVE-2023-1667](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1667)\n- [CVE-2023-1859](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1859)\n- [CVE-2023-1981](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1981)\n- [CVE-2023-2283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2283)\n- [CVE-2023-24329](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24329)\n- [CVE-2023-24593](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24593)\n- [CVE-2023-25180](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-25180)\n- [CVE-2023-2602](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2602)\n- [CVE-2023-2603](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2603)\n- [CVE-2023-2609](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2609)\n- [CVE-2023-2610](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2610)\n- [CVE-2023-29491](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-29491)\n- [CVE-2023-29499](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-29499)\n- [CVE-2023-3138](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3138)\n- [CVE-2023-31436](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-31436)\n- [CVE-2023-31484](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-31484)\n- [CVE-2023-32233](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32233)\n- [CVE-2023-32324](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32324)\n- [CVE-2023-32611](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32611)\n- [CVE-2023-32636](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32636)\n- [CVE-2023-32643](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32643)\n- [CVE-2023-32665](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32665)\n- [CVE-2023-32681](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32681)\n- [CVE-2023-34241](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-34241)\n\n*** ** * ** ***\n\nIn the Google Distributed Cloud air-gapped 1.9.5 AddOn component, the issue on clamav runner handling SIGTERM signal is resolved.\n\n*** ** * ** ***\n\nIn Google Distributed Cloud air-gapped versions 1.9.0 through\n1.9.4, if a Project was created with a name longer than 20 characters, the\nMonitoring stack would fail to start due to a volume name being\ngenerated that exceeded Kubernetes' limit. The volume name is no longer\ngenerated in this way and the Monitoring stack supports the full\n30-character Project name limit.\n\n*** ** * ** ***\n\nThis release fixes an issue with disaster recovery execution of HSM backups.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.5 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.5 has a known issue where the\n`harbor-cert-secret` has a different certificate authority (CA) from the client side CA.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.5 has a known issue where a user cluster with three `n2-standard-4` worker nodes has insufficient CPU resources for upgrade.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.5 has a known issue where upgrade fails when a pod is terminated.\n\n*** ** * ** ***\n\nGoogle Distributed Cloud air-gapped 1.9.5 has a known\nissue where the `kube-state-metrics` deployment crash loops.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.5 has a known issue where a user cluster does not become ready in time to restart the `coredns` deployment.\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.5 has a known issue where alerts in organization system clusters don't reach the ticketing system."]]