Determine the viability of start/stop lifecycle hooks in unmanaged-cluster for the kind provider

[joshrosso]

With #3804 in place, we can now start/stop single-node kind clusters we install Tanzu atop.

However, kind does not support this as a first-class feature, see:

• Add start and stop command to kind. kubernetes-sigs/kind#2715

Today, we drop a layer below kind and talk to docker to do start/stop-like functionality.

In our next release, we should consider whether we want to keep this approach for kind. Considerations include things like:

• Is upstream kind interested in us contributing this?
• If not, are we comfortable with the technical debt it brings on?
• etc

note: minikube has first-class support for start/stop and could continue to offer this feature independent of this decision

[kartiklunkad26]

I'm pretty used to using kind versus minikube, and this is valuable for me as a user so that I can use the resources on my laptop for other purposes when I'm not interacting with TCE unmanaged clusters. Especially when the installed packages start to grow on the cluster, this becomes critical.

[jorgemoralespou]

I too think this is very interesting for developers as they might use a workflow similar to the described here: http://jorgemoral.es/posts/2018-07-12-care-and-feed-minishift-dev-envs/. (Although the blog uses minishift/minikube) it is relevant to the "enhanced" development workflow experience.

[vrabbi]

I love this feature and have been using it with kind and its very helpful! Ive been using 0.12.rc2 now for a bit and this feature is already a key part that makes the experience ao great with the 0.12 UC

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.