Skip to main content
Skip table of contents

Delete AKS Cluster

These pages refer to DKP Enterprise and DKP Gov Advanced products.

Ensure that the KUBECONFIG environment variable is set to the self-managed cluster by running export KUBECONFIG={SELF_MANAGED_AZURE_CLUSTER}.conf

Delete the AKS cluster and clean up your environment

Delete the Workload Cluster

  1. Delete the Kubernetes cluster and wait a few minutes:

    Before deleting the cluster, DKP deletes all Services of type LoadBalancer on the cluster. Deleting the Service deletes the Azure LoadBalancer that backs it. To skip this step, use the flag --delete-kubernetes-resources=false.

NOTE: Do not skip this step if the Azure Network is managed by DKP. When DKP deletes cluster, it deletes the Network.

dkp delete cluster --cluster-name=${CLUSTER_NAME} 

 ✓ Deleting Services with type LoadBalancer for Cluster default/aks-example
 ✓ Deleting ClusterResourceSets for Cluster default/aks-example
 ✓ Deleting cluster resources
 ✓ Waiting for cluster to be fully deleted
Deleted default/aks-example cluster

Next Step:

After your cluster is built in the Konvoy component of DKP for your infrastructure/environment, you will Install the Kommander component of DKP to see your dashboard and continue customization.

Known Limitations

NOTE: Be aware of these limitations in the current release of DKP.

  • The DKP version used to create the workload cluster must match the DKP version used to delete the workload cluster.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.