Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add master node/worker node type to minikube status #7586

Merged
merged 4 commits into from
Apr 15, 2020
Merged

Add master node/worker node type to minikube status #7586

merged 4 commits into from
Apr 15, 2020

Conversation

govargo
Copy link
Contributor

@govargo govargo commented Apr 10, 2020

What type of PR is this?

/kind ux

What this PR does / why we need it:

When minikube status is executed, the node name & component status are printed.
It don't have node type like master or worker.

This PR add node type(master/worker) to minikube status for user to know node clearly.

Which issue(s) this PR fixes:

Fixes #7475

Does this PR introduce a user-facing change?

Yes.
This PR fixes the minikube status command output(node type).

Before this PR

$ out/minikube status
minikube
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured

minikube-m02
host: Running
kubelet: Running

After this PR

$ out/minikube status
master node: minikube
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured

worker node: minikube-m02
host: Running
kubelet: Running

Added node type master node and worker node.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

@k8s-ci-robot k8s-ci-robot added kind/ux cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 10, 2020
@k8s-ci-robot
Copy link
Contributor

Hi @govargo. 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 k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Apr 10, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: govargo
To complete the pull request process, please assign sharifelgamal
You can assign the PR to them by writing /assign @sharifelgamal 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:

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

@minikube-bot
Copy link
Collaborator

Can one of the admins verify this patch?

@govargo
Copy link
Contributor Author

govargo commented Apr 10, 2020

/assign @sharifelgamal

@medyagh
Copy link
Member

medyagh commented Apr 10, 2020

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 10, 2020
@minikube-pr-bot
Copy link

kvm2 Driver
docker Driver

@sharifelgamal
Copy link
Collaborator

Could you change it to have type: attribute instead of appending it to the node name?

For example,

$ out/minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured

minikube-m02
type: Worker
host: Running
kubelet: Running

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 11, 2020
@govargo
Copy link
Contributor Author

govargo commented Apr 11, 2020

I updated to add type to each node.

@govargo
Copy link
Contributor Author

govargo commented Apr 11, 2020

I noticed there is the multi node tutorial docs after I opened this PR.
And I added minikube status output example to it.

@minikube-pr-bot
Copy link

kvm2 Driver
Times for minikube: [65.486760528 63.068115647 64.057181136]
Average time for minikube: 64.20401910366667

Times for Minikube (PR 7586): [60.630296565 64.62627673899999 61.138140944]
Average time for Minikube (PR 7586): 62.13157141599999

Averages Time Per Log

+--------------------------------+-----------+--------------------+
|              LOG               | MINIKUBE  | MINIKUBE (PR 7586) |
+--------------------------------+-----------+--------------------+
| * minikube v1.9.2 on Debian    |  0.057007 |           0.054364 |
|                           9.11 |           |                    |
| * Using the kvm2 driver based  |  0.017569 |           0.018366 |
| on existing profile            |           |                    |
| * Starting control plane node  |  0.003140 |           0.002799 |
| minikube in cluster minikube   |           |                    |
| * Creating kvm2 VM (CPUs=2,    | 41.956894 |          40.178798 |
| Memory=3700MB, Disk=20000MB)   |           |                    |
| ...                            |           |                    |
| * Preparing Kubernetes v1.18.0 | 20.326404 |          19.951991 |
| on Docker 19.03.8 ...          |           |                    |
| * Enabling addons:             |  1.760048 |           1.847329 |
| default-storageclass,          |           |                    |
| storage-provisioner            |           |                    |
| * Done! kubectl is now         |  0.079687 |           0.073663 |
| configured to use "minikube"   |           |                    |
|                                |  0.003270 |           0.004261 |
+--------------------------------+-----------+--------------------+

docker Driver
Times for minikube: [26.210655147 25.178506902 25.693017427]
Average time for minikube: 25.69405982533333

Times for Minikube (PR 7586): [35.594420821 32.970830936 45.955961341]
Average time for Minikube (PR 7586): 38.17373769933334

Averages Time Per Log

+----------------------------------------+-----------+--------------------+
|                  LOG                   | MINIKUBE  | MINIKUBE (PR 7586) |
+----------------------------------------+-----------+--------------------+
| * minikube v1.9.2 on Debian            |  0.071102 |           0.067283 |
|                                   9.11 |           |                    |
| * Using the docker driver              |  0.002025 |           0.002205 |
| based on existing profile              |           |                    |
| * Starting control plane node          |  0.000489 |           0.000124 |
| minikube in cluster minikube           |           |                    |
| * Pulling base image ...               |  0.146886 |           0.150649 |
| * Creating Kubernetes in               |  7.281042 |           8.406201 |
| docker container with (CPUs=2)         |           |                    |
| (4 available), Memory=3700MB           |           |                    |
| (15043MB available) ...                |           |                    |
| * Preparing Kubernetes v1.18.0         |  0.000161 |           0.097598 |
| on Docker 19.03.2 ...                  |           |                    |
|   -                                    | 16.870674 |          24.118811 |
| kubeadm.pod-network-cidr=10.244.0.0/16 |           |                    |
| * Enabling addons:                     |  1.257055 |           5.257779 |
| default-storageclass,                  |           |                    |
| storage-provisioner                    |           |                    |
| * Done! kubectl is now                 |  0.060312 |           0.069543 |
| configured to use "minikube"           |           |                    |
|                                        |  0.004314 |           0.003544 |
+----------------------------------------+-----------+--------------------+

@codecov-io
Copy link

Codecov Report

Merging #7586 into master will not change coverage by %.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #7586   +/-   ##
=======================================
  Coverage   36.49%   36.49%           
=======================================
  Files         147      147           
  Lines        9139     9139           
=======================================
  Hits         3335     3335           
  Misses       5416     5416           
  Partials      388      388           
Impacted Files Coverage Δ
cmd/minikube/cmd/status.go 21.18% <ø> (ø)

@@ -42,6 +43,21 @@ multinode-demo Ready master 9m58s v1.18.0
multinode-demo-m02 Ready <none> 9m5s v1.18.0
```

```
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a note here:

  • You can also check the status of your nodes:

Copy link
Contributor Author

@govargo govargo Apr 14, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the NOTE.

@minikube-pr-bot
Copy link

kvm2 Driver
Times for minikube: [64.468924122 62.823430949 65.970996493]
Average time for minikube: 64.421117188

Times for Minikube (PR 7586): [63.288898895 61.998257601000006 60.506507842999994]
Average time for Minikube (PR 7586): 61.93122144633333

Averages Time Per Log

+--------------------------------+-----------+--------------------+
|              LOG               | MINIKUBE  | MINIKUBE (PR 7586) |
+--------------------------------+-----------+--------------------+
| * minikube v1.9.2 on Debian    |  0.055102 |           0.056091 |
|                           9.11 |           |                    |
| * Using the kvm2 driver based  |  0.019845 |           0.019374 |
| on existing profile            |           |                    |
| * Starting control plane node  |  0.015585 |           0.004705 |
| minikube in cluster minikube   |           |                    |
| * Creating kvm2 VM (CPUs=2,    | 40.428127 |          40.273569 |
| Memory=3700MB, Disk=20000MB)   |           |                    |
| ...                            |           |                    |
| * Preparing Kubernetes v1.18.0 | 22.019570 |          19.727939 |
| on Docker 19.03.8 ...          |           |                    |
| * Enabling addons:             |  1.794941 |           1.778082 |
| default-storageclass,          |           |                    |
| storage-provisioner            |           |                    |
| * Done! kubectl is now         |  0.079588 |           0.067227 |
| configured to use "minikube"   |           |                    |
|                                |  0.008360 |           0.004235 |
+--------------------------------+-----------+--------------------+

docker Driver
Times for minikube: [25.597429407 25.900885767999995 25.803364665]
Average time for minikube: 25.76722661333333

Times for Minikube (PR 7586): [26.658757137000002 25.169288617 24.032754563000005]
Average time for Minikube (PR 7586): 25.286933439

Averages Time Per Log

+----------------------------------------+-----------+--------------------+
|                  LOG                   | MINIKUBE  | MINIKUBE (PR 7586) |
+----------------------------------------+-----------+--------------------+
| * minikube v1.9.2 on Debian            |  0.070244 |           0.071952 |
|                                   9.11 |           |                    |
| * Using the docker driver              |  0.002480 |           0.002151 |
| based on existing profile              |           |                    |
| * Starting control plane node          |  0.000114 |           0.000119 |
| minikube in cluster minikube           |           |                    |
| * Pulling base image ...               |  0.057068 |           0.054093 |
| * Creating docker container            |  7.254650 |           7.430912 |
| (CPUs=2, Memory=3700MB) ...            |           |                    |
| * Preparing Kubernetes v1.18.0         |  0.000157 |           0.000164 |
| on Docker 19.03.2 ...                  |           |                    |
|   -                                    | 16.878574 |          16.279409 |
| kubeadm.pod-network-cidr=10.244.0.0/16 |           |                    |
| * Enabling addons:                     |  1.439811 |           1.378675 |
| default-storageclass,                  |           |                    |
| storage-provisioner                    |           |                    |
| * Done! kubectl is now                 |  0.060707 |           0.062676 |
| configured to use "minikube"           |           |                    |
|                                        |  0.003421 |           0.006781 |
+----------------------------------------+-----------+--------------------+

@sharifelgamal sharifelgamal merged commit 1554d8e into kubernetes:master Apr 15, 2020
@govargo govargo deleted the feature/add-status-node-section branch February 13, 2021 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/ux ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Explicitly show node type in minikube status
7 participants