Azure Delete Cluster
Delete the Kubernetes cluster and clean up your environment
Prepare to Delete a Workload Cluster
NOTE: A self-managed workload cluster cannot delete itself. If your workload cluster is self-managed, you must create a bootstrap cluster and move the cluster lifecycle services to the bootstrap cluster before deleting the workload cluster.
If you did not make your workload cluster self-managed, as described in Make New Cluster Self-Managed, proceed to Delete the workload cluster section below.
Create a bootstrap cluster:
The bootstrap cluster will host the Cluster API controllers that reconcile the cluster objects marked for deletion:
NOTE: To avoid using the wrong kubeconfig, the following steps use explicit kubeconfig paths and contexts.
dkp create bootstrap --kubeconfig $HOME/.kube/config
✓ Creating a bootstrap cluster
✓ Initializing new CAPI components
2. Move the Cluster API objects from the workload to the bootstrap cluster: The cluster lifecycle services on the bootstrap cluster are ready, but the workload cluster configuration is on the workload cluster. The move
command moves the configuration, which takes the form of Cluster API Custom Resource objects, from the workload to the bootstrap cluster. This process is also called a Pivot.
dkp move capi-resources \
--from-kubeconfig ${CLUSTER_NAME}.conf \
--from-context ${CLUSTER_NAME}-admin@${CLUSTER_NAME} \
--to-kubeconfig $HOME/.kube/config \
--to-context kind-konvoy-capi-bootstrapper
✓ Moving cluster resources
3. Use the cluster lifecycle services on the workload cluster to check the workload cluster status:
dkp describe cluster --kubeconfig $HOME/.kube/config -c ${CLUSTER_NAME}
NAME READY SEVERITY REASON SINCE MESSAGE
Cluster/azure-example True 15s
├─ClusterInfrastructure - AzureCluster/azure-example True 29s
├─ControlPlane - KubeadmControlPlane/azure-example-control-plane True 15s
│ ├─Machine/azure-example-control-plane-gvj5d True 22s
│ ├─Machine/azure-example-control-plane-l8j9r True 23s
│ └─Machine/azure-example-control-plane-xhxxg True 23s
└─Workers
└─MachineDeployment/azure-example-md-0 True 35s
├─Machine/azure-example-md-0-d67567c8b-2674r True 24s
├─Machine/azure-example-md-0-d67567c8b-n276j True 25s
├─Machine/azure-example-md-0-d67567c8b-pzg8k True 23s
└─Machine/azure-example-md-0-d67567c8b-z8km9 True 24s
NOTE: After moving the cluster lifecycle services to the workload cluster, remember to use dkp
with the workload cluster kubeconfig
.
Wait for the cluster control-plane to be ready:
CODEkubectl --kubeconfig $HOME/.kube/config wait --for=condition=controlplaneready "clusters/${CLUSTER_NAME}" --timeout=60m
CODEcluster.cluster.x-k8s.io/azure-example condition met
Persistent Volumes (PVs) are not deleted automatically by design in order to preserve your data. However, they take up storage space if not deleted. You must delete PVs manually. Information for backup of a cluster and PVs is on the page in documentation called Back up your Cluster's Applications and Persistent Volumes .
Delete the Workload Cluster
Make sure your Azure credentials are up to date. Refresh the credentials using this command:
CODEdkp update bootstrap credentials azure --kubeconfig $HOME/.kube/config
To delete a cluster, you would use
dkp delete cluster
and pass in the name of the cluster you are trying to delete with--cluster-name
flag. You would usekubectl get clusters
to get those details (--cluster-name
and--namespace
) of the Kubernetes cluster to delete it.
NOTE: Do not usedkp get clusters
since that gets you Kommander cluster details rather than Konvoy kubernetes cluster details.CODEkubectl get clusters
Delete the Kubernetes cluster and wait a few minutes:
NOTE: Before deleting the cluster, dkp deletes all Services of type LoadBalancer on the cluster. To skip this step, use the flag
--delete-kubernetes-resources=false
.CODEdkp delete cluster --cluster-name=${CLUSTER_NAME} --kubeconfig $HOME/.kube/config
CODE✓ Deleting Services with type LoadBalancer for Cluster default/azure-example ✓ Deleting ClusterResourceSets for Cluster default/azure-example ✓ Deleting cluster resources ✓ Waiting for cluster to be fully deleted Deleted default/azure-example cluster
After the workload cluster is deleted, delete the bootstrap cluster.
Delete the Bootstrap Cluster
Use
dkp
with the bootstrap cluster to delete the workload cluster.
dkp delete bootstrap --kubeconfig $HOME/.kube/config
✓ Deleting bootstrap cluster
Next Step:
Once 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 Konvoy.
The Konvoy version used to create the workload cluster must match the Konvoy version used to delete the workload cluster.