The new operator and experimental KubeCluster is designed to be more flexible and extensible than the current KubeCluster implementation. This will allow us to implement features that we have not been able to do before, such as support dask-ctl or delete clusters simply with kubectl.

This milestone goes beyond the Feature Parity milestone where the classic and experimental cluster managers can be switched out. This targets when all stretch features have been implemented.