连接到 vCenter Server 的 Pod 会出现一些预期错误,例如 vsphere-controller-manager 和 cluster-health-controller Pod。
可以创建和删除无状态 Pod。
创建有状态 Pod 将失败,因为挂接磁盘需要访问 vCenter Server。这些 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
[[["易于理解","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。"],[],[],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)."]]