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.
Reparar la VM del plano de control del clúster de administrador
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En una implementación de Google Distributed Cloud, la VM del plano de control de un clúster de administrador tiene dos discos adjuntos:
El disco de arranque tiene el sistema operativo para la VM.
El disco de datos tiene credenciales y la base de datos etcd, que almacena el estado del clúster de administrador. Es decir, el disco de datos almacena todos los objetos de Kubernetes para el clúster de administrador.
En esta página, se muestra cómo recuperarse cuando se pierde la VM del plano de control o se vulnera el disco de arranque. Por ejemplo:
El disco de arranque se vuelve de solo lectura debido a los registros de diario de spam.
El sistema de archivos de superposición Docker se daña.
En esta página, no se abarca la recuperación del disco de datos. Si deseas obtener instrucciones para recuperar el disco de datos, consulta Restablece un clúster de administrador.
Repara la VM del plano de control
Los pasos que debes seguir para reparar la VM del plano de control del clúster de administrador difieren ligeramente según si tienes un clúster de administrador con alta disponibilidad (HA) o sin HA.
HA
Un clúster de administrador de alta disponibilidad tiene tres VMs del plano de control. Debes tener al menos dos VMs para abrir el plano de control del clúster. Si tres VMs fallaron, repara las VMs con errores una a la vez. Después de que se repare y ejecute la segunda VM, debería volver a iniciarse el plano de control del clúster.
ADMIN_CLUSTER_CONFIG por la ruta de acceso del archivo de configuración del clúster de administrador
ADMIN_CLUSTER_KUBECONFIG es la ruta de acceso del archivo kubeconfig del clúster de administrador.
El resultado del comando es similar al siguiente:
Please select the control plane VM template to be used for re-creating the admin cluster's control plane VM.
[1] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-2-tmpl
GKE on-prem version: 1.16.0-gke.550
Creation time: 2023-07-25 01:52:51.815518 +0000 UTC
CPU: 4 CPU(s)
Memory: 16384 MB
Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-2-data.vmdk
[2] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-0-tmpl
GKE on-prem version: 1.16.0-gke.550
Creation time: 2023-07-25 01:52:54.228252 +0000 UTC
CPU: 4 CPU(s)
Memory: 16384 MB
Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-0-data.vmdk
[3] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-1-tmpl
GKE on-prem version: 1.16.0-gke.550
Creation time: 2023-07-25 01:52:54.210705 +0000 UTC
CPU: 4 CPU(s)
Memory: 16384 MB
Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-1-data.vmdk
Please enter your numeric choice:
Ingresa el número de la VM que quieres reparar. Si no ves la VM en el resultado, comunícate con el equipo de asistencia de Google Cloud.
Si tienes tres VMs que se deben reparar, gkectl repair
admin-master muestra un mensaje de error similar al siguiente después de reparar la primera VM:
If you are repairing admin control plane VM for HA admin cluster,
it's possible that the API server is still down after repairing one
of the VMs. Try continue fixing other control plane VMs listed to
recover the quorum of control plane.
En este caso, vuelve a ejecutar el comando para reparar la segunda VM.
ADMIN_CLUSTER_CONFIG por la ruta de acceso del archivo de configuración del clúster de administrador
ADMIN_CLUSTER_KUBECONFIG es la ruta de acceso del archivo kubeconfig del clúster de administrador.
La VM del plano de control del clúster de administrador se clona en una plantilla de VM, que tiene toda la información necesaria para volver a crear la VM. El comando gkectl repair admin-master usa la plantilla de VM para crear una VM nueva. Luego, conecta un disco de arranque nuevo y el disco de datos existente.
Si los nodos del clúster obtienen sus direcciones de un servidor DHCP, la VM nueva podría tener una dirección IP diferente de la VM original.
[[["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: 2024-11-21 (UTC)"],[],[],null,["In a Google Distributed Cloud implementation, the control-plane VM for an\nadmin cluster has two attached disks:\n\n- The boot disk has the operating system for the VM.\n\n- The data disk has credentials and the etcd database, which stores the state of\n the admin cluster. That is, the data disk stores all of the Kubernetes objects\n for the admin cluster.\n\nThis page shows you how to recover when the control-plane VM is lost or the boot\ndisk is compromised. For example:\n\n- The boot disk becomes read-only due to spam journal logs.\n- The Docker overlay filesystem gets corrupted.\n\nThis page does not cover recovery of the data disk. For instructions on how to\nrecover the data disk, see\n[Restoring an admin cluster](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/back-up-and-restore-an-admin-cluster-with-gkectl).\n\nRepair the control-plane VM **Warning:** Don't run `gkectl repair admin-master` after a failed admin upgrade attempt. Instead, [resume the admin upgrade](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/upgrading#about_resume_admin).\n\nThe steps that you do to repair the admin cluster's control-plane VM differ\nslightly depending on whether you have a high-availability (HA) admin cluster\nor a non-HA admin cluster. \n\nHA\n\nAn HA admin cluster has three control plane VMs. You must have at least two VMs\nto bring up the cluster control plane. If three VMs have failed, repair\nthe failed VMs one at a time. After the second VM is repaired and running,\nthe cluster control plane should come back up.\n\n1. Run the following command:\n\n ```\n gkectl repair admin-master --config ADMIN_CLUSTER_CONFIG --kubeconfig ADMIN_CLUSTER_KUBECONFIG\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_CONFIG\u003c/var\u003e with the path of your admin cluster\n configuration file.\n\n - \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_KUBECONFIG\u003c/var\u003e with the path of your admin cluster's\n kubeconfig file.\n\n The output of the command is similar to the following: \n\n ```\n Please select the control plane VM template to be used for re-creating the admin cluster's control plane VM.\n [1] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-2-tmpl\n GKE on-prem version: 1.16.0-gke.550\n Creation time: 2023-07-25 01:52:51.815518 +0000 UTC\n CPU: 4 CPU(s)\n Memory: 16384 MB\n Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-2-data.vmdk\n\n [2] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-0-tmpl\n GKE on-prem version: 1.16.0-gke.550\n Creation time: 2023-07-25 01:52:54.228252 +0000 UTC\n CPU: 4 CPU(s)\n Memory: 16384 MB\n Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-0-data.vmdk\n\n [3] VM template: /atl-qual-vc07/vm/gke-admin-57f8g-fx9f4c729448z2v8-1-tmpl\n GKE on-prem version: 1.16.0-gke.550\n Creation time: 2023-07-25 01:52:54.210705 +0000 UTC\n CPU: 4 CPU(s)\n Memory: 16384 MB\n Data disk: [vsanDatastore] 37a73d64-b823-47cd-2e0c-00620b9189a0/gke-admin-57f8g/default/gke-admin-57f8g-1-data.vmdk\n\n Please enter your numeric choice:\n ```\n2. Enter the number for the VM that you want to repair. If you don't see\n the VM in the output, contact Google Cloud Support.\n\n If you have three VMs that need to be repaired, `gkectl repair\n admin-master` outputs an error message similar to the\n following after repairing the first VM: \n\n If you are repairing admin control plane VM for HA admin cluster,\n it's possible that the API server is still down after repairing one\n of the VMs. Try continue fixing other control plane VMs listed to\n recover the quorum of control plane.\n\n In this case, re-run the command to repair the second VM.\n\nNon-HA\n\nRun the following command: \n\n```\ngkectl repair admin-master \\\n --config ADMIN_CLUSTER_CONFIG \\\n --kubeconfig ADMIN_CLUSTER_KUBECONFIG\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_CONFIG\u003c/var\u003e with the path of your admin cluster configuration file.\n- \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_KUBECONFIG\u003c/var\u003e with the path of your admin cluster's `kubeconfig` file.\n\nThe admin cluster's control-plane VM is cloned into a VM template, which has\nall the information needed to re-create the VM. The `gkectl repair admin-master`\ncommand uses the VM template to create a new VM. Then it attaches a new\nboot disk and the existing data disk.\n\nIf your cluster nodes get their addresses from a DHCP server, the new VM might\nhave a different IP address from the original VM.\n\nWhat's next\n\n- If you need additional assistance, reach out to [Cloud Customer Care](/support-hub).\n\n You can also see\n [Getting support](/kubernetes-engine/distributed-cloud/vmware/docs/getting-support) for more information about support resources, including the following:\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)."]]
