Require "name" in "kind delete cluster" cli command

[abuchanan-airbyte]

What would you like to be added:

I'd like to require the "name" option in the kind delete cluster command.

Why is this needed:

I accidentally deleted my "kind" cluster when I had intended to delete my "foo" cluster. This happened because I assumed kind would delete the "current" cluster instead of the "cluster".

I realize now that the kind command does not actually have a "current" context, but since kind create cluster updates the current kube context, where I think work for awhile with kubectl, I was in that mindset.

But aside from that, for something destruction like delete, I think it's better to be explicit about what you want to delete.

One reason not to do this could be backwards compat – users that have scripts that depend on the current behavior would have failing scripts after upgrading kind. I'm not sure how sensitive this project is to CLI compat.

Thanks!

[aojea]

I'm not sure how sensitive this project is to CLI compat.

Very very sensitive, one of the biggest strength is the stability ... Does not mean if something is reasonable it can be considered, but this seems a fat fingers problem that can be solved by end user by applying convention to not mix default and explicit values