Delete Cluster

Prepare to delete a self-managed workload cluster

NOTE: A self-managing workload cluster cannot delete itself. If your workload cluster is self-managing, 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-managing, as described in Make New Cluster Self-Managed, see Delete the workload cluster.

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. If you have set your KUBECONFIG to your environment, run the command unset KUBECONFIG before continuing below.
```
dkp create bootstrap --kubeconfig $HOME/.kube/config
```
The output resembles this example:
```
✓ Creating a bootstrap cluster
✓ Initializing new CAPI components
```

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 
You can now view resources in the moved cluster by using the --kubeconfig flag with kubectl. For example: kubectl --kubeconfig=$HOME/.kube/config get nodes

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/d2iq-e2e-cluster_name-1                                     True                     13h
├─ClusterInfrastructure - VSphereCluster/d2iq-e2e-cluster_name-1    True                     13h
├─ControlPlane - KubeadmControlPlane/d2iq-control-plane             True                     13h
│ ├─Machine/d2iq--control-plane-7llgd                               True                     13h
│ ├─Machine/d2iq--control-plane-vncbl                               True                     13h
│ └─Machine/d2iq--control-plane-wbgrm                               True                     13h
└─Workers
    └─MachineDeployment/d2iq--md-0                                  True                     13h
    ├─Machine/d2iq--md-0-74c849dc8c-67rv4                           True                     13h
    ├─Machine/d2iq--md-0-74c849dc8c-n2skc                           True                     13h
    ├─Machine/d2iq--md-0-74c849dc8c-nkftv                           True                     13h
    └─Machine/d2iq--md-0-74c849dc8c-sqklv                           True                     13h

NOTE: After moving the cluster lifecycle services to the workload cluster, remember to use DKP with the workload cluster kubeconfig.

Use DKP with the bootstrap cluster to delete the workload cluster.

Wait for the cluster control-plane to be ready:

kubectl --kubeconfig $HOME/.kube/config wait --for=condition=controlplaneready "clusters/${CLUSTER_NAME}" --timeout=60m

The output should be similar to this example:

d2iq-e2e-cluster-1-control-plane/vsphere-example condition met

Delete the workload cluster

Make sure your vSphere credentials are up-to-date. Refresh the credentials using this command:
```
dkp update bootstrap credentials vsphere --kubeconfig $HOME/.kube/config
```

Delete the Kubernetes cluster and wait a few minutes:

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.

dkp delete cluster --cluster-name=${CLUSTER_NAME} --kubeconfig $HOME/.kube/config

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

After the workload cluster is deleted, delete the bootstrap cluster.

Delete the bootstrap cluster

dkp delete bootstrap --kubeconfig $HOME/.kube/config

 ✓ Deleting bootstrap cluster

Known Limitations

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

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

Delete the Kubernetes cluster and clean up your environment

Prepare to delete a self-managed workload cluster

Delete the workload cluster

Delete the bootstrap cluster

Known Limitations