update-context: Automatically set the context as current/active in ku…

[prezha]

fixes #9246

example scenario:

common starting point:

❯ minikube profile list
|---------------------------------|-----------|---------|------------|------|---------|---------|
|             Profile             | VM Driver | Runtime |     IP     | Port | Version | Status  |
|---------------------------------|-----------|---------|------------|------|---------|---------|
| functional-20200910153511-83042 | docker    | docker  | 172.17.0.3 | 8443 | v1.19.2 | Running |
|---------------------------------|-----------|---------|------------|------|---------|---------|

❯ kubectl get pods -A
The connection to the server localhost:8080 was refused - did you specify the right host or port?

❯ kubectl config get-contexts
CURRENT   NAME                              CLUSTER                           AUTHINFO                                                       NAMESPACE
          functional-20200910153511-83042   functional-20200910153511-83042   functional-20200910153511-83042

before PR:

❯ minikube update-context -p functional-20200910153511-83042
🙄  No changes required for the "functional-20200910153511-83042" context

❯ kubectl get pods -A
The connection to the server localhost:8080 was refused - did you specify the right host or port?

❯ kubectl config get-contexts
CURRENT   NAME                              CLUSTER                           AUTHINFO                                                       NAMESPACE
          functional-20200910153511-83042   functional-20200910153511-83042   functional-20200910153511-83042

after PR:

❯ minikube update-context -p functional-20200910153511-83042
🙄  No changes required for the "functional-20200910153511-83042" context
💗  Current context is "functional-20200910153511-83042"

❯ kubectl get pods -A
NAMESPACE     NAME                                                      READY   STATUS    RESTARTS   AGE
kube-system   coredns-f9fd979d6-gqgcm                                   1/1     Running   0          8m35s
kube-system   etcd-functional-20200910153511-83042                      1/1     Running   0          8m32s
kube-system   kube-apiserver-functional-20200910153511-83042            1/1     Running   0          8m32s
kube-system   kube-controller-manager-functional-20200910153511-83042   1/1     Running   0          8m32s
kube-system   kube-proxy-8vnrd                                          1/1     Running   0          8m34s
kube-system   kube-scheduler-functional-20200910153511-83042            1/1     Running   0          8m32s
kube-system   storage-provisioner                                       1/1     Running   1          8m38s

❯ kubectl config get-contexts
CURRENT   NAME                              CLUSTER                           AUTHINFO                                                       NAMESPACE
*         functional-20200910153511-83042   functional-20200910153511-83042   functional-20200910153511-83042

[k8s-ci-robot]

Hi @prezha. 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: prezha
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 #9281 into master will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #9281      +/-   ##
==========================================
- Coverage   29.48%   29.47%   -0.02%     
==========================================
  Files         170      170              
  Lines       10307    10311       +4     
==========================================
  Hits         3039     3039              
- Misses       6846     6850       +4     
  Partials      422      422              

Impacted Files	Coverage Δ
cmd/minikube/cmd/update-context.go	0.00% <0.00%> (ø)

[prezha]

/assign @medyagh

[medyagh]

@prezha thank you for this PR, would you please put the before/after this PR output in the PR descripion.

[prezha]

@medyagh thank you for your comment - i've added example output before and after this PR (with the common starting point), similar to your example in the issue description

please let me know if i should add more details

[medyagh]

thank you @prezha for this PR

[prezha]

thank you @prezha for this PR

you're very welcome @medyagh, and thank you for your review and comments