이 문서에서는 vCenter Server가 다운된 경우의 클러스터 동작 방법을 설명합니다.
vCenter 서버가 다운된 상태에서의 각 상태는 다음과 같습니다.
머신은 Available 상태입니다.
노드는 Ready 상태입니다.
포드는 Running 상태입니다.
vCenter Server에 연결하는 포드에 몇 가지 예상되는 오류가 있습니다(예: vsphere-controller-manager 및 cluster-health-controller 포드).
스테이트리스(Stateless) 포드를 만들고 삭제할 수 있습니다.
디스크를 연결하려면 vCenter Server에 대한 액세스 권한이 필요하므로 스테이트풀(Stateful) 포드를 만들 수 없습니다. 이러한 포드는 Pending 상태가 됩니다.
다음과 유사한 오류가 표시되면서 gkectl diagnose 명령어가 실패합니다.
Exit with error:
failed to prepare diagnose parameters: failed to create vSphere client: Post "https://my-server": dial tcp 203.0.113.1:443: connect: connection timed out
자동 복구가 트리거되지 않습니다. 이는 머신 및 노드 상태가 vCenter Server에 대한 연결 오류의 상태를 변경하지 않기 때문입니다.
vCenter Server가 다시 온라인 상태로 된 후(버전 7.0U2 미만)
머신이 Unavailable 상태로 전환되며 자동 복구나 수동 해결 방법을 통해 올바른 상태로 되돌려야 합니다.
[[["이해하기 쉬움","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)"],[],[],null,["This document describes how a cluster behaves if vCenter Server is down.\n\nWhile vCenter Server is down:\n\n- The machines are in the `Available` state\n\n- The nodes are in the `Ready` state.\n\n- The Pods are in the `Running` state.\n\n- There are some expected errors in Pods that connect to vCenter Server; for\n example, the `vsphere-controller-manager` and `cluster-health-controller`\n Pods.\n\n- Stateless Pods can be created and deleted.\n\n- The creation of a stateful Pod will fail, because attaching a disk requires\n access to vCenter Server. These Pods will be in the `Pending` state.\n\n- The `gkectl diagnose` command will fail with an error similar to the\n following:\n\n ```\n Exit with error:\n failed to prepare diagnose parameters: failed to create vSphere client: Post \"https://my-server\": dial tcp 203.0.113.1:443: connect: connection timed out\n ```\n- Auto repair is not triggered. This is because the machine and node states do\n not change states on connection errors to vCenter Server.\n\nAfter vCenter Server comes back online (versions \\\u003c 7.0U2)\n\n- The machines go to the `Unavailable` state, and auto repair or or a manual\n workaround is needed to get back the correct states.\n\n- The cluster functions correctly even though the machines are in the\n `Unavailable` state.\n\nAfter vCenter Server comes back online (versions \\\u003e= 7.0U2)\n\n- No extra steps are needed, and the cluster is healthy again.\n\nWhat's next\n\nIf you need additional assistance, reach out to\n\n[Cloud Customer Care](/support-hub).\n\nYou can also see\n[Getting support](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support) for more information about support resources, including the following:\n\n- [Requirements](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#support_requirements) for opening a support case.\n- [Tools](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#support_tools) to help you troubleshoot, such as logs and metrics.\n- Supported [components](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#whats_supported), [versions](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#version_support_policy), and [features](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support#supported_features) of Google Distributed Cloud for VMware (software only)."]]
