Seleccione el Google Cloud proyecto en el que se encuentra el cluster.
En la lista de clústeres, seleccione el nombre del clúster y luego seleccione Ver detalles en el panel lateral.
Seleccione la pestaña Nodos para ver una lista de todos los grupos de nodos.
Seleccione un grupo de nodos de la lista.
Cerca de la parte superior de la ventana, haga clic en deleteEliminar .
Si la eliminación falla, siga los pasos de la pestaña gcloud y agregue el indicador --ignore-errors al comando gcloud container azure node-pools delete .
NODE_POOL_NAME : el nombre del grupo de nodos que se eliminará
CLUSTER_NAME
GOOGLE_CLOUD_LOCATION
Si el comando devuelve un error y la eliminación falla, puede forzarla volviendo a ejecutar el comando con la opción --ignore-errors . Esta opción está disponible a partir de la versión 1.29.
Cómo GKE en Azure protege las cargas de trabajo durante la eliminación del grupo de nodos
Durante la eliminación de un grupo de nodos, GKE en Azure realiza un apagado ordenado en cada nodo sin respetar PodDisruptionBudget. Esto implica los siguientes pasos:
Deshabilite el escalador automático del clúster si estaba habilitado.
Establezca una fecha límite para el proceso de vaciado. Transcurrido este plazo, incluso si aún existen objetos de pod, GKE en Azure detiene el vaciado y procede a eliminar las máquinas virtuales subyacentes. El plazo predeterminado es de 5 minutos. Por cada 10 nodos adicionales, se añaden 5 minutos adicionales.
Acordonar todos los nodos en el grupo de nodos.
Antes de que se cumpla la fecha límite, elimine los objetos Pod en el grupo de nodos haciendo todo lo posible.
Eliminar todos los recursos computacionales subyacentes.
Eliminar un clúster
Antes de eliminar un clúster, asegúrese de haber eliminado todos sus grupos de nodos.
Consola
En el Google Cloud consola, vaya a la página de descripción general de clústeres de Google Kubernetes Engine .
Seleccione el Google Cloud proyecto en el que se encuentra el cluster.
En la lista de clústeres, seleccione el nombre del clúster y luego seleccione Ver detalles en el panel lateral.
Cerca de la parte superior de la ventana, haga clic en deleteEliminar .
Si la eliminación falla, siga los pasos de la pestaña gcloud y agregue el indicador --ignore-errors al comando gcloud container azure clusters delete .
nube g
Para eliminar un clúster, ejecute el siguiente comando:
GOOGLE_CLOUD_LOCATION : la Google Cloud Ubicación que alberga este clúster
Si el comando devuelve un error y la eliminación falla, puede forzarla volviendo a ejecutar el comando con la opción --ignore-errors . Esta opción está disponible a partir de la versión 1.29.
Eliminar un recurso de AzureClient
Debe eliminar un AzureClient en los siguientes casos:
Ha eliminado todo GKE en Azure y ya no necesita AzureClient.
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-06-12 (UTC)."],[],[],null,["Delete a cluster\n\nThis page explains how to delete a node pool, a cluster, and an\nAzureClient resource.\n| **Warning:** Soon after you delete a Google Cloud project, the resources in Azure are permanently deleted. To safeguard against the accidental deletion of a Google Cloud project, use a [Project lien](/resource-manager/docs/project-liens).\n\nDelete a node pool\n\nTo delete a cluster, you must first delete all of its node pools. \n\nConsole\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. In the cluster list, select the name of the cluster, and then select\n **View details** in the side panel.\n\n4. Select the **Nodes** tab to see a list of all the node pools.\n\n5. Select a node pool from the list.\n\n6. Near the top of the window, click delete **Delete**.\n\n If the delete fails, follow the steps in the `gcloud` tab and add the\n `--ignore-errors` flag to the `gcloud container azure node-pools delete`\n command.\n\ngcloud\n\n1. Get a list of your node pools:\n\n gcloud container azure node-pools list \\\n --cluster \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e: the name of the cluster that the node pool is attached to\n - \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e: the Google Cloud location hosting the node pool\n2. For each of your node pools, delete it with the following command:\n\n gcloud container azure node-pools delete \u003cvar translate=\"no\"\u003eNODE_POOL_NAME\u003c/var\u003e \\\n --cluster \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eNODE_POOL_NAME\u003c/var\u003e: the name of the node pool to delete\n - \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e\n - \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e\n\n If the command returns an error and the delete fails, you can force the\n deletion by running the command again with the `--ignore-errors` flag.\n This flag is available in version 1.29 and later.\n | **Caution:** Adding the `--ignore-errors` flag to the delete command might result in orphaned Azure resources. If that happens, consult the Azure documentation on how to remove the orphaned resources.\n\nHow GKE on Azure protects workloads during node pool deletion\n\nDuring node pool deletion, GKE on Azure performs graceful shut down on\neach node without honoring PodDisruptionBudget. It takes the following\nsteps:\n\n1. Disable cluster autoscaler if it was enabled.\n2. Set up a deadline for the draining process. After this deadline, even if there are still Pod objects existing, GKE on Azure stops draining and proceeds to deleting underlying virtual machines. The default deadline is 5 minutes. For every 10 more nodes, 5 more minutes is added.\n3. Cordon all the nodes in the node pool.\n4. Before deadline is met, delete Pod objects in the node pool with best efforts.\n5. Delete all the underlying compute resources.\n\nDelete a cluster\n\nBefore deleting a cluster, make sure that you have deleted all of its node pools. \n\nConsole\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. In the cluster list, select the name of the cluster, and then select\n **View details** in the side panel.\n\n4. Near the top of the window, click delete **Delete**.\n\n If the delete fails, follow the steps in the `gcloud` tab and add the\n `--ignore-errors` flag to the `gcloud container azure clusters delete`\n command.\n\ngcloud\n\nTo delete a cluster, run the following command: \n\n gcloud container azure clusters delete \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e: the name of the cluster to delete\n- \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e: the Google Cloud location\n hosting this cluster\n\n If the command returns an error and the delete fails, you can force the\n deletion by running the command again with the `--ignore-errors` flag.\n This flag is available in version 1.29 and later.\n | **Caution:** Adding the `--ignore-errors` flag to the delete command might result in orphaned Azure resources. If that happens, consult the Azure documentation on how to remove the orphaned resources.\n\nDelete an AzureClient resource\n\nYou should delete an AzureClient in the following cases:\n\n- You have removed all GKE on Azure and you don't need the AzureClient any more.\n- You have updated the cluster's Authentication from AzureClient to [workload identity federation](/kubernetes-engine/multi-cloud/docs/azure/how-to/create-cluster#workload-identity-federation).\n\nNote that before deleting an AzureClient, you need to have deleted all the clusters that use the AzureClient.\n\nTo delete an AzureClient resource, run the following command: \n\n gcloud container azure clients delete \u003cvar translate=\"no\"\u003eCLIENT_NAME\u003c/var\u003e \\\n --location=\u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eCLIENT_NAME\u003c/var\u003e: the name of the AzureClient to delete\n- \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e: the Google Cloud location where the client is located\n\nAfter deleting the AzureClient resource, remove the certificate at Azure AD\nthat you uploaded when you created the client.\n\nWhat's next\n\n- For more information, see the [`gcloud container azure clusters delete`](https://cloud.google.com/sdk/gcloud/reference/container/azure/clusters/delete) documentation."]]
