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.
Actualiza las referencias del certificado de AC de vCenter
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En esta página, se describe cómo actualizar la referencia al certificado de AC de vCenter si cambió, ya que los clústeres de administrador y de usuario en ejecución deben estar informados sobre el cambio. Esto afecta el campo vCenter.caCertPath en el archivo de configuración del clúster de administrador y los archivos de configuración del clúster de usuario para Google Distributed Cloud.
Puedes actualizar las referencias del certificado con el comando gkectl update como se describe aquí.
Actualiza el certificado de la AC de vCenter al que se hace referencia en los archivos de configuración del clúster
Para actualizar los clústeres de administrador y de usuario en ejecución a fin de usar el certificado nuevo, sigue estos pasos:
Recupera el nuevo certificado de la AC de vCenter y descomprímelo:
Puedes usar la marca -k si deseas permitir certificados desconocidos. Esto sirve para evitar cualquier problema de certificado que tengas cuando accedas a vCenter.
Guarda el certificado de Linux en un archivo llamado vcenter-ca.pem.
En el archivo de configuración del clúster de administrador, configura vCenter.caCertPath, en la ruta de acceso de tu archivo vcenter-ca.pem nuevo.
En cada uno de los archivos de configuración del clúster de usuario, configura vCenter.caCertPath como la ruta de acceso del archivo vcenter-ca.pem nuevo.
Para cada uno de tus clústeres de usuario, ejecuta el comando gkectl update:
[[["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-09-26 (UTC)"],[],[],null,["This page describes how to update the reference to the vCenter CA certificate if it has changed, as your running admin cluster and user clusters must be informed of the change. This affects the `vCenter.caCertPath` field in the admin cluster configuration file and the user cluster configuration files for Google Distributed Cloud.\n\nYou can update the certificate references with the `gkectl update` command as described here.\n\nUpdate the referenced vCenter CA certificate in the cluster configuration files\n\nTo update the running admin and user clusters to use the new certificate:\n\n1. Retrieve the new vCenter CA certificate and extract it:\n\n ```\n curl -o certs.zip https://VCENTER_IP_ADDRESS_OR_FQDN/certs/download.zip\n unzip certs.zip\n ```\n\n You can use the `-k` flag if you want to allow unknown certificates. This is to avoid any certificate issues you may have accessing vCenter.\n2. Determine which of the vCenter certificates is valid. Only one of the Linux certificate files in the extracted `..../certs/lin` folder is the valid vCenter certificate. To determine which file is the valid vCenter certificate, do the following:\n\n 1. Set the following environment variables from the Admin Workstation where `govc` is already installed. If not already done, [download and install govc tool](https://github.com/vmware/govmomi/tree/main/govc#binaries):\n\n ```\n export GOVC_URL=https://VCENTER_IP_ADDRESS_OR_FQDN\n export GOVC_USERNAME=VCENTER_USERNAME\n export GOVC_PASSWORD=VCENTER_PASSWORD\n export GOVC_TLS_CA_CERTS=FULL_PATH_OF_EXTRACTED_LIN_FILE\n export GOVC_INSECURE=false\n ```\n\n \u003cbr /\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eVCENTER_IP_ADDRESS_OR_FQDN\u003c/var\u003e: the IP address or FQDN of the vCenter Server.\n\n - \u003cvar translate=\"no\"\u003eVCENTER_USERNAME\u003c/var\u003e: the username of the vCenter Server.\n\n - \u003cvar translate=\"no\"\u003eVCENTER_PASSWORD\u003c/var\u003e: the password for the specified username.\n\n - \u003cvar translate=\"no\"\u003eFULL_PATH_OF_EXTRACTED_LIN_FILE\u003c/var\u003e: the full path to the Linux certificate file for which you are conducting a validity test.\n\n 2. To verify that the vCenter certificate is valid, run the `govc about` command:\n\n ```\n govc about\n ```\n\n If the vCenter certificate is valid, the `govc about` command prints details about the vCenter Server similar to the following: \n\n FullName: VMware Center Server 7.0.3 build-24322018\n Name: VMware Center Server\n Vendor: VMware, Inc.\n Version: 7.0.3\n Build: 24322018\n OS type: linux-x64\n API type: VirtualCenter\n API version: 7.0.3.0\n Product ID: vpx\n UUID: 475fa366-faa9-43f0-9417-e6dadc55514c\n\n If the certificate is invalid, you should see an `x509` error. If you see an `x509` error, update the `FULL_PATH_OF_EXTRACTED_LIN_FILE` environment variable to point at a different Linux certificate file in the extracted `..../certs/lin` folder, and then run the `govc about` command again. Repeat steps a. and b. until you locate the valid certificate, or until you are done testing each of the Linux certificate files in the extracted `..../certs/lin` folder.\n3. To backup the old vCenter CA certificate file (which is at the path specified in the [`vCenter.caCertPath`](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest#vcenter-cacertpath-field) field of your admin cluster configuration file), rename it to `vcenter-ca-cert.pem.old`.\n\n4. Rename the new valid certificate file in the `..../certs/lin` folder to `vcenter-ca-cert.pem` and then move it to the path specified in the [`vCenter.caCertPath`](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest#vcenter-cacertpath-field) field of your admin cluster configuration file.\n\n5. Update your admin cluster:\n\n ```\n gkectl update admin --config ADMIN_CLUSTER_CONFIG --kubeconfig ADMIN_CLUSTER_KUBECONFIG\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_CONFIG\u003c/var\u003e: the path of your admin cluster configuration file.\n\n After the update command completes, the admin cluster will use the new\n certificate.\n6. Verify that the admin cluster is healthy:\n\n ```\n gkectl diagnose cluster --kubeconfig ADMIN_CLUSTER_KUBECONFIG\n ```\n\n For more information, see\n [Diagnose an admin cluster](/kubernetes-engine/distributed-cloud/vmware/docs/troubleshooting/diagnose#diagnose_admin_cluster).\n7. In each of your user cluster configuration files, set [`vCenter.caCertPath`](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/user-cluster-configuration-file-latest#vcenter-cacertpath-field) to the path of your new `vcenter-ca-cert.pem` file.\n\n8. For each of your user clusters, run the `gkectl update` command:\n\n ```\n gkectl update cluster --config USER_CLUSTER_CONFIG --kubeconfig ADMIN_CLUSTER_KUBECONFIG\n ```\n\n \u003cbr /\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eUSER_CLUSTER_CONFIG\u003c/var\u003e: the path of your user cluster configuration file.\n\n After the update command completes for a particular user cluster, the cluster\n will use the new certificate.\n9. Verify that the user cluster is healthy:\n\n ```\n gkectl diagnose cluster --kubeconfig ADMIN_CLUSTER_KUBECONFIG \\\n --cluster-name USER_CLUSTER_NAME\n ```\n\n For more information, see\n [Diagnose a user cluster](/kubernetes-engine/distributed-cloud/vmware/docs/troubleshooting/diagnose#diagnose_user_cluster).\n\n| **Note:** The `vCenter.caCertPath` field also appears in the admin workstation configuration file. If you want to create a new admin workstation, make sure that you edit the `vCenter.caCertPath` field to reference the current certificate."]]
