Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menunjukkan cara memperbarui kredensial vCenter dan F5 BIG-IP untuk
cluster admin atau cluster pengguna untuk Google Distributed Cloud.
Namun, kunci SSH untuk cluster pengguna dan admin tidak dapat diubah atau dirotasi
menggunakan prosedur standar ini atau prosedur standar lainnya. Jika kebijakan keamanan Anda memerlukan rotasi kunci SSH berkala, buat ulang cluster Anda untuk membuat kunci SSH baru.
Untuk memperbarui kredensial cluster admin, Anda juga harus menyertakan
flag --admin-cluster.
--admin-cluster: Flag wajib jika Anda
men-deploy perubahan ke cluster admin. Kecualikan tanda ini saat men-deploy
perubahan ke cluster pengguna.
Hasil: Kredensial vCenter yang diubah akan segera divalidasi terhadap
server dan konfirmasi akan ditampilkan ke terminal:
"vsphere credentials updated successfully". Jika kredensial baru gagal
login ke server vCenter, Anda dapat mengedit username dan password di
file kredensial, lalu men-deploy ulang perubahan Anda.
validating new credentials against vcenter
restarted "deployment/clusterapi-controllers" in namespace "kube-system"
vsphere credentials updated successfully.
Memperbarui kredensial F5 BIG-IP untuk cluster admin atau cluster pengguna
Perbarui kredensial F5 BIG-IP di antarmuka web F5.
Di workstation admin, gunakan langkah-langkah berikut untuk memperbarui kredensial F5 BIG-IP
untuk cluster admin atau cluster pengguna.
Edit file kredensial F5 Anda untuk mengubah kredensial.
Memperbarui kredensial registry pribadi untuk cluster admin atau cluster pengguna
Anda dapat memperbarui kredensial dan sertifikat registry pribadi (pembaruan server
tidak didukung) untuk cluster. Saat Anda melakukan update, kredensial saat ini dan
baru harus dapat terhubung ke registry pribadi.
Di workstation admin, gunakan langkah-langkah berikut untuk memperbarui kredensial
private registry untuk cluster admin atau cluster pengguna.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-01 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)."]]
