doctl kubernetes cluster delete
Generated on 9 Apr 2025
from doctl version
v1.124.0
Usage
doctl kubernetes cluster delete <id|name>... [flags]Aliases
d, rmDescription
Deletes the specified Kubernetes clusters and the Droplets associated with them. To delete all other DigitalOcean resources created during the operation of the clusters, such as load balancers, volumes or volume snapshots, use the --dangerous flag.
Example
The following example deletes a cluster named example-cluster:
doctl kubernetes cluster delete example-clusterFlags
| Option | Description |
|---|---|
--dangerous |
Deletes the cluster’s associated resources like load balancers, volumes and volume snapshots Default: false |
--force, -f |
Deletes the cluster without a confirmation prompt Default: false |
--help, -h |
Help for this command |
--update-kubeconfig |
Remove the deleted cluster from your kubeconfig Default: true |
Related Commands
| Command | Description |
|---|---|
| doctl kubernetes cluster | Display commands for managing Kubernetes clusters |
Global Flags
| Option | Description |
|---|---|
--access-token, -t |
API V2 access token |
--api-url, -u |
Override default API endpoint |
--config, -c |
Specify a custom config file Default: |
--context |
Specify a custom authentication context name |
--http-retry-max |
Set maximum number of retries for requests that fail with a 429 or 500-level error
Default: 5 |
--http-retry-wait-max |
Set the minimum number of seconds to wait before retrying a failed request
Default: 30 |
--http-retry-wait-min |
Set the maximum number of seconds to wait before retrying a failed request
Default: 1 |
--interactive |
Enable interactive behavior. Defaults to true if the terminal supports it (default false)
Default: false |
--output, -o |
Desired output format [text|json] Default: text |
--trace |
Show a log of network activity while performing a command Default: false |
--verbose, -v |
Enable verbose output Default: false |