Restez organisé à l'aide des collections
Enregistrez et classez les contenus selon vos préférences.
Cette page explique comment mettre à jour les identifiants vCenter et F5 BIG-IP pour le cluster d'administrateur ou un cluster d'utilisateur pour Google Distributed Cloud.
ADMIN_CLUSTER_KUBECONFIG : spécifie le fichier kubeconfig du cluster d'administrateur.
Exemple : kubeconfig
Pour mettre à jour les identifiants du cluster d'administrateur, vous devez également inclure l'option --admin-cluster.
--admin-cluster : option requise si vous déployez des modifications sur le cluster d'administrateur. Excluez cette option lorsque vous déployez des modifications sur un cluster d'utilisateur.
Résultat : les identifiants vCenter modifiés sont immédiatement validés sur le serveur et une confirmation est envoyée au terminal : "vsphere credentials updated successfully". Si les nouveaux identifiants ne parviennent pas à se connecter au serveur vCenter, vous pouvez modifier username et password dans le fichier d'identifiants, puis redéployer vos modifications.
validating new credentials against vcenter
restarted "deployment/clusterapi-controllers" in namespace "kube-system"
vsphere credentials updated successfully.
Mettre à jour les identifiants F5 BIG-IP pour un cluster d'administrateur ou un cluster d'utilisateur
Mettez à jour les identifiants F5 BIG-IP dans l'interface Web F5.
Sur votre poste de travail administrateur, procédez comme suit pour mettre à jour les identifiants F5 BIG-IP pour un cluster d'administrateur ou un cluster d'utilisateur.
Modifiez votre fichier d'identifiants F5 pour modifier les identifiants.
Mettez à jour les identifiants F5 BIG-IP de votre cluster d'utilisateur :
Mettre à jour les identifiants du registre privé pour un cluster d'administrateur ou un cluster d'utilisateur (preview)
Vous pouvez mettre à jour les identifiants et le certificat du registre privé (la mise à jour du serveur n'est pas prise en charge) pour un cluster. Lors de la mise à jour, les identifiants actuels et les nouveaux identifiants doivent pouvoir se connecter au registre privé.
Sur votre poste de travail administrateur, procédez comme suit pour mettre à jour les identifiants de registre privé pour un cluster d'administrateur ou un cluster d'utilisateur.
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/04/22 (UTC).
[[["Facile à comprendre","easyToUnderstand","thumb-up"],["J'ai pu résoudre mon problème","solvedMyProblem","thumb-up"],["Autre","otherUp","thumb-up"]],[["Difficile à comprendre","hardToUnderstand","thumb-down"],["Informations ou exemple de code incorrects","incorrectInformationOrSampleCode","thumb-down"],["Il n'y a pas l'information/les exemples dont j'ai besoin","missingTheInformationSamplesINeed","thumb-down"],["Problème de traduction","translationIssue","thumb-down"],["Autre","otherDown","thumb-down"]],["Dernière mise à jour le 2025/04/22 (UTC)."],[],[],null,["This page shows how to update the vCenter and F5 BIG-IP credentials for the\nadmin cluster or a user cluster for Google Distributed Cloud.\n\nHowever, the SSH keys for user and admin clusters cannot be changed or rotated\nusing this or any other standard procedure. If your security policies require\nperiodic SSH key rotation, recreate your cluster to create a new SSH key.\n\nUpdate vSphere credentials\n\nThe vCenter credentials that you want to add to a cluster must already\nexist. [Learn about vCenter roles and user\nprivileges](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.security.doc/GUID-18071E9A-EED1-4968-8D51-E0B4F526FDA3.html).\n\nThe admin cluster and each user cluster are initially configured to use the\n[vCenter username and password](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/credentials-configuration-file)\nthat you used to create those clusters. The [admin cluster configuration file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest#vcenter-credentials-fileref-path-field) contains a reference to a credentials file, as does each [user cluster configuration file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/user-cluster-configuration-file-latest#vcenter-credentials-fileref-path-field). These references can be different for each cluster.\n\nUse the following steps to update the vCenter credentials on a cluster:\n\n1. In the admin workstation, open your [credentials configuration\n file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/credentials-configuration-file) in an editor.\n\n Update the `username` and `password` attributes in the credentials configuration file.\n2. Run the `gkectl update credentials vsphere`\n command to deploy the changes to a cluster:\n\n ```\n gkectl update credentials vsphere \\\n --config CLUSTER_CONFIG \\\n --kubeconfig CLUSTER_KUBECONFIG \\\n --admin-cluster\n ```\n\n Replace the following:\n - \u003cvar class=\"edit\" translate=\"no\"\u003eCLUSTER_CONFIG\u003c/var\u003e: Specifies the [admin cluster configuration\n file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest) or the [user cluster configuration\n file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/user-cluster-configuration-file-latest), depending on which cluster you are updating.That cluster configuration file includes a reference to the vCenter credentials that you want to deploy to your cluster.\n - \u003cvar class=\"edit\" translate=\"no\"\u003eADMIN_CLUSTER_KUBECONFIG\u003c/var\u003e: Specifies the [`kubeconfig`](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/create-admin-cluster#create-admin-cluster) file of the admin cluster. Example: `kubeconfig`\n\n For updating credentials for the admin cluster, you must also include the\n `--admin-cluster` flag.\n - `--admin-cluster`: Required flag if you are deploying changes to the admin cluster. Exclude this flag when deploying changes to a user cluster.\n\n Result: The changed vCenter credentials are immediately validated against\n the server and a confirmation is output to the terminal:\n \"`vsphere credentials updated successfully`\". If the new credentials fail to\n log in to the vCenter server, you can edit the `username` and `password` in\n the credentials file and redeploy your changes.\n\n **Examples:**\n - User cluster example:\n\n ```\n gkectl update credentials vsphere \\\n --config USER_CLUSTER_CONFIG --kubeconfig ADMIN_CLUSTER_KUBECONFIG\n ```\n\n If successful, the result output indicates that the vSphere credentials have updated successfully.\n - Admin cluster example:\n\n ```\n gkectl update credentials vsphere \\\n --config ADMIN_CLUSTER_CONFIG --kubeconfig ADMIN_CLUSTER_KUBECONFIG \\\n --admin-cluster\n ```\n\n Result: \n\n ```\n validating new credentials against vcenter\n restarted \"deployment/clusterapi-controllers\" in namespace \"kube-system\"\n vsphere credentials updated successfully.\n ```\n\nUpdate F5 BIG-IP credentials for an admin cluster or a user cluster\n\nUpdate the F5 BIG-IP credentials in the F5 web interface.\n\nOn your admin workstation, use the following steps to update the F5 BIG-IP\ncredentials for an admin cluster or a user cluster.\n\n1. Edit your F5 credentials file to change the credentials.\n\n2. Update the F5 BIG-IP credentials for your cluster:\n\n ```\n gkectl update credentials f5bigip --config CLUSTER_CONFIG \\\n --kubeconfig ADMIN_CLUSTER_KUBECONFIG --admin-cluster\n ```\n\n| **Note:** The user cluster configuration file and the admin cluster configuration file reference the path to this credentials file. If you want to change the path of the credentials, update the corresponding cluster configuration file to change the file reference. Run the appropriate `gkectl update admin` or `gkectl update cluster` command to update this reference.\n\nUpdate private registry credentials for an admin cluster or a user cluster\n\nYou can update the private registry credentials and certificate (server update\nis **not** supported) for a cluster. As you do the update, both the current and\nnew credentials must be able to connect to the private registry.\n| **Note:** If your cluster is using Artifact Registry, you can't update the cluster to use a private registry.\n\nOn your admin workstation, use the following steps to update the private\nregistry credentials for an admin cluster or a user cluster.\n\n1. Update your private registry credentials in the\n [credentials configuration file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/credentials-configuration-file).\n\n2. Update the cluster to use the new private registry credentials:\n\n Admin cluster: \n\n ```\n gkectl update credentials privateregistry --config CLUSTER_CONFIG \\\n --kubeconfig ADMIN_CLUSTER_KUBECONFIG --admin-cluster\n ```\n\n User cluster: \n\n ```\n gkectl update credentials privateregistry --config CLUSTER_CONFIG \\\n --kubeconfig ADMIN_CLUSTER_KUBECONFIG\n ```\n\nUpdate other credentials\n\nTo update keys for your Identity and Access Management\n[service accounts](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/service-accounts), see\n[Rotate service account keys](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/rotating-service-account-keys)."]]
