vCenter Server に接続する Pod には、エラーがいくつか想定されています。たとえば、vsphere-controller-manager Pod と cluster-health-controller Pod です。
ステートレス Pod の作成と削除はできます。
ディスクにアタッチするには vCenter Server へのアクセスが必要となるため、ステートフル Pod の作成は失敗します。これらの Pod は 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 への接続エラーの状態が変更されないためです。
[[["わかりやすい","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-05-07 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)."]]