Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menjelaskan cara membatalkan pendaftaran cluster dari fleet secara manual. Google Cloud
Saat Anda membatalkan pendaftaran cluster secara manual, koneksinya ke fleet akan dihapus, tetapi cluster tetap ada. Menghapus cluster GKE terdaftar di Google Cloud menggunakan konsol Google Cloud atau gcloud CLI juga akan menghapus keanggotaan fleet cluster.
Anda hanya dapat membatalkan pendaftaran cluster GKE di Google Cloud dan cluster pihak ketiga yang terpasang. Jenis cluster lainnya tidak dapat dibatalkan pendaftarannya.
Perhatikan bahwa memindahkan cluster terdaftar antar-fleet (membatalkan pendaftaran, lalu mendaftarkan ulang) tidak direkomendasikan, karena dapat menyebabkan perilaku yang tidak terduga atau tidak diinginkan: misalnya, Workload Identity fleet workload Anda akan berubah, yang berpotensi menyebabkan permintaan diblokir dan gangguan. Pendekatan yang direkomendasikan adalah membuat cluster baru di fleet tempat Anda ingin workload berada, lalu memindahkan workload dari cluster lama ke cluster baru.
Membatalkan pendaftaran cluster
gcloud
Membatalkan pendaftaran cluster GKE
Perintah ini hanya dapat digunakan untuk membatalkan pendaftaran cluster GKE yang didaftarkan menggunakan gcloud container clusters update atau gcloud container clusters create.
[MEMBERSHIP_NAME] adalah nama keanggotaan yang sesuai dengan
cluster Anda. Untuk mencantumkan semua keanggotaan di Hub, jalankan: gcloud container fleet memberships list.
[GKE_URI] adalah URI cluster GKE, misalnya: 'https://container.googleapis.com/projects/my-project/locations/us-central1-a/clusters/my-cluster'.
Anda bisa mendapatkan URI dengan menjalankan gcloud container clusters list --uri.
URI yang diberikan akan divalidasi untuk mengonfirmasi bahwa URI tersebut dipetakan ke cluster GKE yang valid.
[GKE_CLUSTER] adalah location/name dari
cluster GKE. Lokasinya dapat berupa zona atau region, misalnya: us-central1-a/my-cluster.
Membatalkan pendaftaran cluster terlampir
Petunjuk ini berlaku untuk cluster yang terdaftar menggunakan versi terbaru fitur cluster terlampir kami. Cluster yang dilampirkan menggunakan generasi sebelumnya yang tidak digunakan lagi dari fitur ini harus menggunakan perintah lama di bagian berikutnya.
[MEMBERSHIP_NAME] adalah nama keanggotaan yang sesuai dengan
cluster Anda. Untuk mendapatkan daftar semua langganan di Hub, jalankan:
gcloud container fleet memberships list.
[KUBECONFIG_PATH] adalah jalur lokal tempat file kubeconfig yang berisi entri untuk file cluster disimpan.
Nilai default-nya adalah $KUBECONFIG jika variabel lingkungan tersebut ditetapkan,
jika tidak, nilai default-nya adalah $HOME/.kube/config.
[KUBECONFIG_CONTEXT] adalah konteks cluster seperti yang
muncul di file kubeconfig. Anda bisa mendapatkan nilai ini dari command line dengan menjalankan kubectl config current-context.
Konsol
Membatalkan pendaftaran cluster GKE di Google Cloud
Untuk membatalkan pendaftaran cluster GKE:
Buka halaman GKE Clusters. Halaman ini menampilkan semua cluster Anda.
Klik nama cluster yang ingin Anda lepaskan, lalu pilih
Lihat detail selengkapnya di panel samping.
Di dekat bagian atas jendela, klik delete
Hapus.
Saat diminta untuk mengonfirmasi, masukkan nama cluster, lalu klik Confirm.
Terraform
Untuk membatalkan pendaftaran cluster GKE yang Anda daftarkan menggunakan Terraform:
Hapus blok berikut dari konfigurasi resource google_container_cluster cluster:
fleet {
project = "FLEET_HOST_PROJECT""
}
FLEET_HOST_PROJECT adalah Google Cloud project ID tempat cluster Anda terdaftar.
Mengelola Connect Agent
Langkah-langkah berikut hanya berlaku untuk membatalkan pendaftaran cluster terlampir, tempat Agen Connect diinstal di cluster sebagai bagian dari pendaftaran.
Setelah membatalkan pendaftaran cluster, Anda dapat memverifikasi bahwa namespace yang digunakan oleh
Agen Connect telah dihapus. Hal ini hanya berlaku untuk pendaftaran yang menginstal Agen Connect. Untuk melakukannya, jalankan:
kubectl get ns -l hub.gke.io/project
Jika perintah ini tidak menampilkan output, namespace sudah dihapus.
Menghapus Akun Layanan Connect Agent
Jika Anda membuat akun layanan untuk Connect Agent, Anda dapat menghapusnya sebagai berikut:
gcloud iam service-accounts delete [SERVICE_ACCOUNT_NAME]
Membatalkan pendaftaran cluster yang tidak tersedia
Jika Anda ingin membatalkan pendaftaran cluster yang tidak dapat diakses lagi, lakukan
langkah-langkah berikut:
Mencantumkan cluster (alias keanggotaan) yang saat ini terdaftar:
gcloud container fleet memberships list
Di output perintah, kolom Name mencantumkan nama keanggotaan cluster terdaftar, dan kolom EXTERNAL_ID mencantumkan UID cluster dari namespace kube-system.
Untuk membatalkan pendaftaran cluster yang tidak tersedia, jalankan perintah berikut:
[[["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-07-31 UTC."],[],[],null,["# Unregistering a cluster\n\nThis page describes how to manually unregister a cluster from a Google Cloud fleet.\nWhen you manually unregister a cluster, its connection to the fleet is\nremoved but the cluster remains. [Deleting a registered GKE cluster on Google Cloud](/kubernetes-engine/docs/how-to/deleting-a-cluster) using either the Google Cloud console or gcloud CLI also deletes the cluster's fleet membership.\n\nYou can unregister GKE clusters on Google Cloud and attached\nthird-party clusters only. Other cluster types can't be unregistered.\n\nNote that moving registered clusters between fleets (unregistering then\nreregistering) is not recommended, as it can result in unexpected\nor unwanted behavior: for example, your workloads' fleet Workload Identity\nwill change, potentially resulting in blocked requests and outages. The\nrecommended approach is to create a new cluster in the fleet in which you\nwant your workloads to reside, then move your workloads from your old cluster\nto the new cluster.\n\nUnregister a cluster\n--------------------\n\n### gcloud\n\n### Unregister a GKE cluster\n\nThis command can only be used to unregister GKE clusters registered using `gcloud container clusters update` or `gcloud container clusters create`.\n\nRun the following command: \n\n```\ngcloud container clusters update CLUSTER_NAME --clear-fleet-project\n```\n\nReplace \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e with the cluster's name you want to delete.\n\n### Unregister a GKE cluster (legacy command)\n\nIf you registered a cluster using the older `register` command, run either of the following commands to unregister it: \n\n```\ngcloud container fleet memberships unregister [MEMBERSHIP_NAME] \\\n --project=[PROJECT_ID] \\\n --gke-uri=[GKE_URI]\n``` \n\n```\ngcloud container fleet memberships unregister [MEMBERSHIP_NAME] \\\n --project=[PROJECT_ID] \\\n --gke-cluster=[GKE_CLUSTER]\n```\n\nwhere:\n\n- \u003cvar translate=\"no\"\u003e[PROJECT_ID]\u003c/var\u003e is your Google Cloud project ID. [Learn how to find\n this value](/resource-manager/docs/creating-managing-projects#identifying_projects).\n- \u003cvar translate=\"no\"\u003e[MEMBERSHIP_NAME]\u003c/var\u003e is the membership name that corresponds to your cluster. To list all the memberships on the Hub, run: `gcloud container fleet memberships list`.\n- \u003cvar translate=\"no\"\u003e[GKE_URI]\u003c/var\u003e is the URI of the GKE cluster, for example: 'https://container.googleapis.com/projects/my-project/locations/us-central1-a/clusters/my-cluster'. You can obtain the URI by running `gcloud container clusters list --uri`. The provided URI will be validated to confirm that it maps to the valid GKE cluster.\n- \u003cvar translate=\"no\"\u003e[GKE_CLUSTER]\u003c/var\u003e is the `location/name` of the GKE cluster. The location can be a zone or a region for example: `us-central1-a/my-cluster`.\n\n### Unregister an attached cluster\n\nThese instructions apply to clusters registered using the latest version of our attached clusters feature. Clusters attached using the deprecated previous generation of this feature should use the legacy command in the next section.\n\n- [Detach an EKS cluster](/anthos/clusters/docs/multi-cloud/attached/eks/how-to/detach-cluster)\n- [Detach an AKS cluster](/anthos/clusters/docs/multi-cloud/attached/aks/how-to/detach-cluster)\n- [Detach another attached cluster type](/anthos/clusters/docs/multi-cloud/attached/generic/how-to/detach-cluster)\n\n### Unregister an attached cluster (legacy command)\n\nIf you registered a cluster using the previous generation of attached clusters, run the following command to unregister it: \n\n```\ngcloud container fleet memberships unregister [MEMBERSHIP_NAME] \\\n --project=[PROJECT_ID] \\\n --context=[KUBECONFIG_CONTEXT] \\\n --kubeconfig=[KUBECONFIG_PATH]\n```\n\nwhere:\n\n- \u003cvar translate=\"no\"\u003e[PROJECT_ID]\u003c/var\u003e is your Google Cloud project ID. [Learn how to find\n this value](/resource-manager/docs/creating-managing-projects#identifying_projects).\n- \u003cvar translate=\"no\"\u003e[MEMBERSHIP_NAME]\u003c/var\u003e is the membership name that corresponds to your cluster. To get list of all the memberships on the Hub, run: `gcloud container fleet memberships list`.\n- \u003cvar translate=\"no\"\u003e[KUBECONFIG_PATH]\u003c/var\u003e is the local path where your kubeconfig containing an entry for the cluster file is stored. This defaults to `$KUBECONFIG` if that environment variable is set, otherwise this defaults to `$HOME/.kube/config`.\n- \u003cvar translate=\"no\"\u003e[KUBECONFIG_CONTEXT]\u003c/var\u003e is the cluster's context as it appears in the kubeconfig file. You can get this value from the command line by running `kubectl config current-context`.\n\n### Console\n\n### Unregister a GKE cluster on Google Cloud\n\nTo unregister a GKE cluster:\n\n1. Go to the **GKE Clusters** page. This\n page shows all your clusters.\n\n [Go to the GKE Clusters page](https://console.cloud.google.com/kubernetes/list/overview)\n2. Click more_vert **Actions** next to the cluster in the list that you want to unregister.\n\n3. In the Actions menu, select **Unregister**.\n\n4. In the dialog that displays, type the name of the cluster and click **Unregister** to confirm the action.\n\n### Unregister an attached third-party cluster\n\n\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\n\u003cbr /\u003e\n\nTo unregister an attached cluster:\n\n1. In the Google Cloud console, go to the **Google Kubernetes Engine clusters\n overview** page.\n\n [Go to GKE clusters](https://console.cloud.google.com/kubernetes/list/overview)\n2. Select the Google Cloud project that the cluster is in.\n\n3. Click the name of the cluster you want to detach, and then select\n **View more details** in the side panel.\n\n4. Near the top of the window, click delete **Delete**.\n\n5. When prompted to confirm, enter the name of the cluster and\n click **Confirm**.\n\n### Terraform\n\nTo unregister a GKE cluster that you registered using Terraform:\n\nDelete the following block from the `google_container_cluster` resource configuration of the cluster: \n\n fleet {\n project = \u003cvar translate=\"no\"\u003e\"FLEET_HOST_PROJECT\"\u003c/var\u003e\"\n }\n\n\u003cvar translate=\"no\"\u003eFLEET_HOST_PROJECT\u003c/var\u003e is the Google Cloud project ID your cluster is registered to.\n\nManage the Connect Agent\n------------------------\n\nThe following steps apply only to unregistering attached clusters, where the Connect Agent is installed on the cluster as part of registration.\n\n### Optional: Verify that the Connect Agent namespace is deleted\n\nAfter you unregister a cluster, you can verify that the namespace used by the\nConnect Agent has been deleted. This applies to registrations that install the Connect Agent only. To do so, run: \n\n```\nkubectl get ns -l hub.gke.io/project\n```\n\nIf this command returns no output, the namespace has already been deleted.\n\n### Delete the Connect Agent Service Account\n\nIf you created a service account for the Connect Agent, you can delete it as follows: \n\n```\ngcloud iam service-accounts delete [SERVICE_ACCOUNT_NAME]\n```\n\nUnregister an unavailable cluster\n---------------------------------\n\nIf you want to unregister a cluster that you can no longer access, perform\nthe following steps:\n\n1. List the clusters (a.k.a memberships) that are currently registered:\n\n ```\n gcloud container fleet memberships list\n ```\n\n In the command output, the `Name` column lists the membership names of registered\n clusters, and the `EXTERNAL_ID` column lists the clusters' UIDs of the kube-system\n namespace.\n2. To unregister an unavailable cluster, run the following command:\n\n ```\n gcloud container fleet memberships delete [MEMBERSHIP_NAME]\n ```\n\n where \u003cvar translate=\"no\"\u003e[MEMBERSHIP_NAME]\u003c/var\u003e is the membership name that corresponds to\n your cluster."]]
