k8s-clean-cluster

Force-clean Kubernetes resources by deleting orphaned Kurtosis namespaces, pods, daemonsets, cluster roles, and cluster role bindings. This removes residual resources that block engine startup when the normal kurtosis clean -a command fails or hangs.

Orphaned Kurtosis resources in a Kubernetes cluster include namespaces, pods, daemonsets, cluster roles, and cluster role bindings. These residual resources block engine startup and require forceful deletion via kubectl to restore a clean cluster state.

Yes, you need kubectl access to the target Kubernetes cluster with appropriate permissions to delete both cluster-scoped and namespace-scoped resources. This access is required to successfully remove all Kurtosis resources and prepare for a fresh engine restart.

Kurtosis clean -a may leave behind resources due to failures or hangs during the deletion process. When this happens, orphaned namespaces, pods, and cluster roles remain in the Kubernetes cluster, requiring a force-clean operation to ensure a completely clean state.

Yes, you can manually remove orphaned Kurtosis namespaces, pods, daemonsets, cluster roles, and cluster role bindings using kubectl. A force-clean operation automates this deletion to reliably remediate residual resources when standard cleanup fails.

Force-clean Kurtosis resources when kurtosis clean -a hangs, encounters failures, or leaves behind residual resources that block engine startup. This approach ensures a clean Kubernetes cluster state for a fresh engine restart.