Google Distributed Cloud(에어 갭 적용형) 1.9.5 부가기능 구성요소에서 clamav 러너가 SIGTERM 신호를 처리하는 문제가 해결되었습니다.
Google Distributed Cloud 오프라인 버전 1.9.0~1.9.4에서 프로젝트 이름이 20자를 초과하는 경우 Kubernetes의 제한을 초과하는 볼륨 이름이 생성되어 모니터링 스택이 시작되지 않습니다. 볼륨 이름은 더 이상 이러한 방식으로 생성되지 않으며 모니터링 스택은 30자(영문 기준)의 전체 프로젝트 이름 제한을 지원합니다.
이 출시에서는 HSM 백업의 재해 복구 실행 문제를 수정합니다.
Google Distributed Cloud 오프라인 1.9.5에는 VM 관리자의 역할 기반 액세스 제어 (RBAC) 및 스키마 설정으로 인해 사용자가 VM 백업 및 복원 프로세스를 시작할 수 없는 알려진 문제가 있습니다.
Google Distributed Cloud 에어 갭 1.9.5에는 harbor-cert-secret의 인증 기관 (CA)이 클라이언트 측 CA와 다른 알려진 문제가 있습니다.
Google Distributed Cloud 오프라인 1.9.5에는 n2-standard-4 워커 노드가 3개인 사용자 클러스터에 업그레이드에 필요한 CPU 리소스가 부족한 알려진 문제가 있습니다.
Google Distributed Cloud(에어 갭 적용형) 1.9.5에는 포드가 종료될 때 업그레이드가 실패하는 알려진 문제가 있습니다.
Google Distributed Cloud air-gapped 1.9.5에는 kube-state-metrics 배포가 비정상 종료되는 알려진 문제가 있습니다.
Google Distributed Cloud 에어 갭 1.9.5에는 사용자 클러스터가 coredns 배포를 다시 시작할 때까지 준비되지 않는 알려진 문제가 있습니다.
Google Distributed Cloud 오프라인 1.9.5에는 조직 시스템 클러스터의 알림이 티켓팅 시스템에 도달하지 않는 알려진 문제가 있습니다.
[[["이해하기 쉬움","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(UTC)"],[[["\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."]]