gcloud alpha container clusters delete - delete an existing cluster for running containers
gcloud alpha container clusters delete NAME [NAME ...] [--async] [--region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...]
(ALPHA) When you delete a cluster, the following resources are deleted:
The control plane resources
All of the node instances in the cluster
Any Pods that are running on those instances
Any firewalls and routes created by Kubernetes Engine at the time of cluster creation
Data stored in host hostPath and emptyDir volumes
GKE will attempt to delete the following resources. Deletion of these resources is not always guaranteed:
External load balancers created by the cluster
Internal load balancers created by the cluster
Persistent disk volumes
To delete an existing cluster, run:
$ gcloud alpha container clusters delete sample-cluster
- NAME [NAME ...]
The names of the clusters to delete.
- --async
Return immediately, without waiting for the operation in progress to complete.
- At most one of these can be specified:
- --region=REGION
Compute region (e.g. us-central1) for the cluster.
- --zone=ZONE, -z ZONE
Compute zone (e.g. us-central1-a) for the cluster. Overrides the default compute/zone property value for this command invocation.
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. These variants are also available:
$ gcloud container clusters delete
$ gcloud beta container clusters delete