Los clústeres de Anthos en VMware ahora son Google Distributed Cloud (solo software) para VMware. Para obtener más información, consulta la descripción general del producto.
Mientras vCenter Server esté inactivo, haz lo siguiente:
Las máquinas están en el estado Available.
Los nodos están en el estado Ready.
Los Pods están en el estado Running.
Hay algunos errores esperados en los Pods que se conectan a vCenter Server, por ejemplo, los Pods vsphere-controller-manager y cluster-health-controller.
Se pueden crear y borrar pods sin estado.
No se podrá crear un Pod con estado, ya que conectar un disco requiere acceso al servidor de vCenter. Estos Pods estarán en el estado Pending.
El comando gkectl diagnose debería fallar con un error similar al siguiente:
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
No se activa la reparación automática. Esto se debe a que los estados de la máquina y del nodo no cambian de estado en los errores de conexión con vCenter Server.
Después de que vCenter Server vuelva a estar en línea (versiones anteriores a 7.0U2)
Las máquinas pasan al estado Unavailable y se necesita una reparación automática o una solución manual para recuperar los estados correctos.
El clúster funciona correctamente, aunque las máquinas estén en el estado Unavailable.
Después de que vCenter Server vuelva a estar en línea (versiones >= 7.0U2)
No se necesitan pasos adicionales, y el clúster vuelve a estar en buen estado.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 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)."]]