Added option --all to stop all clusters

[kadern0]

Resolves #8237

Signed-off-by: kadern0 kaderno@gmail.com

Example of the PR working:

./out/minikube start --profile=cluster1
😄  [cluster1] minikube v1.10.1 on Ubuntu 20.04
✨  Using the docker driver based on existing profile
👍  Starting control plane node cluster1 in cluster cluster1
🔄  Restarting existing docker container for "cluster1" ...
🐳  Preparing Kubernetes v1.18.2 on Docker 19.03.2 ...
    ▪ kubeadm.pod-network-cidr=10.244.0.0/16
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "cluster1"

 ./out/minikube start --profile=cluster2
😄  [cluster2] minikube v1.10.1 on Ubuntu 20.04
✨  Automatically selected the docker driver
👍  Starting control plane node cluster2 in cluster cluster2
🔥  Creating docker container (CPUs=2, Memory=3900MB) ...
🐳  Preparing Kubernetes v1.18.2 on Docker 19.03.2 ...
    ▪ kubeadm.pod-network-cidr=10.244.0.0/16
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "cluster2"

 ./out/minikube stop --all
✋  Stopping "cluster1" in docker ...
🛑  Powering off "cluster1" via SSH ...
🛑  Node "cluster1" stopped.
✋  Stopping "cluster2" in docker ...
🛑  Powering off "cluster2" via SSH ...
🛑  Node "cluster2" stopped.

[k8s-ci-robot]

Hi @kadern0. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kadern0
To complete the pull request process, please assign medyagh
You can assign the PR to them by writing /assign @medyagh in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[minikube-bot]

Can one of the admins verify this patch?

[codecov-commenter]

Codecov Report

Merging #8285 into master will decrease coverage by 0.24%.
The diff coverage is 10.71%.

@@            Coverage Diff             @@
##           master    #8285      +/-   ##
==========================================
- Coverage   34.35%   34.11%   -0.25%     
==========================================
  Files         147      153       +6     
  Lines        9456     9823     +367     
==========================================
+ Hits         3249     3351     +102     
- Misses       5808     6069     +261     
- Partials      399      403       +4     

Impacted Files	Coverage Δ
cmd/minikube/cmd/stop.go	6.66% <10.71%> (+6.66%)	⬆️
pkg/minikube/perf/start.go	13.15% <0.00%> (-16.85%)	⬇️
pkg/minikube/driver/driver.go	58.87% <0.00%> (-1.13%)	⬇️
cmd/minikube/cmd/start.go	13.51% <0.00%> (-0.22%)	⬇️
pkg/minikube/machine/fix.go	38.31% <0.00%> (ø)
pkg/minikube/machine/start.go	62.67% <0.00%> (ø)
pkg/minikube/perf/result_manager.go	0.00% <0.00%> (ø)
pkg/minikube/perf/logs.go	76.92% <0.00%> (ø)
pkg/minikube/image/image.go	7.05% <0.00%> (ø)
pkg/minikube/perf/result.go	100.00% <0.00%> (ø)
... and 8 more

[prasadkatti]

@kadern0 - you will need to amend the commit msg to not include “fixes ...” and then force push it to get rid of the invalid commit message label.

[kadern0]

@prasadkatti I've updated the commit message although I thought it is a common practice to reference the issue within the commit.

[prasadkatti]

@kadern0 - yeah, I thought so too. I am not sure why it is setup that way. I had this same issue on one of my PRs a while back. So I thought I would help.

[medyagh]

thank you for doing this PR. looks good, just a minior nit