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

Allow to set the dashboard proxyfied port #11553

Merged
merged 3 commits into from
Jul 12, 2021
Merged

Allow to set the dashboard proxyfied port #11553

merged 3 commits into from
Jul 12, 2021

Conversation

zigarn
Copy link
Contributor

@zigarn zigarn commented Jun 1, 2021

Add a --port option to minikube dashboard, still defaults to 0 to use a random port.

As the value of the port is not accessible elsewhere than from the minikube dashboard output, it can be sometimes useful to set the port in advance to be able to use it.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 1, 2021
@k8s-ci-robot
Copy link
Contributor

Welcome @zigarn!

It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/minikube has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

Hi @zigarn. 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 needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jun 1, 2021
@k8s-ci-robot k8s-ci-robot requested review from RA489 and tstromberg June 1, 2021 13:27
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 1, 2021
@minikube-bot
Copy link
Collaborator

Can one of the admins verify this patch?

Copy link
Contributor

@ilya-zuyev ilya-zuyev left a comment

Choose a reason for hiding this comment

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

ilyaz@skeletron --- g/minikube ‹dashboard-set-port* ?› » m dashboard --port 77777                                                                                                                                                                       130 ↵
* Enabling dashboard ...
  - Using image kubernetesui/dashboard:v2.1.0
  - Using image kubernetesui/metrics-scraper:v1.0.4
* Verifying dashboard health ...
* Launching proxy ...

X Exiting due to HOST_KUBECTL_PROXY: readByteWithTimeout: EOF
* 
╭──────────────────────────────────────────────────────────────────────────────────╮
│                                                                                  │
│    * If the above advice does not help, please let us know:                      │
│      https://github.com/kubernetes/minikube/issues/new/choose                    │
│                                                                                  │
│    * Please attach the following file to the GitHub issue:                       │
│    * - /tmp/minikube_dashboard_b89fa4de843e548f653e88533f246d7844106df0_0.log    │
│                                                                                  │
╰──────────────────────────────────────────────────────────────────────────────────╯

Could you validate dashboardExposedPort on start? Just to catch the error early and make a better error message

@zigarn
Copy link
Contributor Author

zigarn commented Jun 3, 2021

@ilya-zuyev: port range validation added.
But also it would be good to be able to detect an error of kubectl proxy without waiting for it's stdout, no? It would allow to catch any error.

@ilya-zuyev
Copy link
Contributor

@ilya-zuyev: port range validation added.
But also it would be good to be able to detect an error of kubectl proxy without waiting for it's stdout, no? It would allow to catch any error.

@zigarn yeah, you're right, would be good to have a better error handling for kubectl proxy. PRs are welcome :)
Thanks for the validation fix!

@ilya-zuyev
Copy link
Contributor

/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 Jun 3, 2021
@minikube-pr-bot
Copy link

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 47.8s    | 46.4s               |
| enable ingress | 39.3s    | 41.8s               |
+----------------+----------+---------------------+

Times for minikube start: 49.5s 47.7s 46.9s 47.3s 47.6s
Times for minikube (PR 11553) start: 46.3s 47.1s 46.1s 45.5s 47.0s

Times for minikube ingress: 39.7s 36.3s 42.7s 35.7s 42.2s
Times for minikube (PR 11553) ingress: 43.2s 42.8s 37.3s 43.2s 42.8s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 21.6s    | 21.7s               |
| enable ingress | 35.4s    | 37.4s               |
+----------------+----------+---------------------+

Times for minikube ingress: 35.5s 31.5s 36.0s 33.6s 40.5s
Times for minikube (PR 11553) ingress: 31.5s 35.0s 38.5s 41.5s 40.5s

Times for minikube start: 23.5s 21.2s 20.6s 21.1s 21.8s
Times for minikube (PR 11553) start: 22.8s 22.1s 21.5s 20.9s 21.1s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 42.3s    | 45.9s               |
| enable ingress |          |                     |
+----------------+----------+---------------------+

Times for minikube start: 31.8s 47.0s 43.0s 42.6s 47.2s
Times for minikube (PR 11553) start: 48.0s 47.2s 47.2s 43.3s 43.8s

@zigarn
Copy link
Contributor Author

zigarn commented Jun 10, 2021

Hi!
CI failures doesn't seem to be caused by this changes.
Anything I need to do to continue the PR validation process?

@minikube-bot
Copy link
Collaborator

These are the flake rates of all failed tests on Docker_Linux.

Failed Tests Flake Rate (%)
TestStartStop/group/no-preload/serial/AddonExistsAfterStop 1.37 (chart)
TestStartStop/group/no-preload/serial/SecondStart 1.37 (chart)
TestStartStop/group/no-preload/serial/UserAppExistsAfterStop 1.37 (chart)
TestStartStop/group/no-preload/serial/VerifyKubernetesImages 1.37 (chart)
TestStartStop/group/newest-cni/serial/Pause 2.74 (chart)
TestStartStop/group/no-preload/serial/Pause 6.85 (chart)

@minikube-bot
Copy link
Collaborator

These are the flake rates of all failed tests on Docker_Linux_containerd.

Failed Tests Flake Rate (%)
TestPause/serial/Pause 12.00 (chart)
TestPause/serial/VerifyStatus 12.00 (chart)
TestPause/serial/PauseAgain 16.00 (chart)

@minikube-pr-bot
Copy link

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 46.3s    | 46.4s               |
| enable ingress | 35.6s    | 36.3s               |
+----------------+----------+---------------------+

Times for minikube start: 47.0s 45.3s 46.0s 45.7s 47.4s
Times for minikube (PR 11553) start: 46.6s 46.0s 46.0s 46.3s 47.1s

Times for minikube ingress: 35.2s 35.7s 35.2s 37.8s 34.3s
Times for minikube (PR 11553) ingress: 35.2s 35.3s 42.2s 33.7s 35.2s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 21.8s    | 21.7s               |
| enable ingress | 36.5s    | 33.1s               |
+----------------+----------+---------------------+

Times for minikube (PR 11553) ingress: 30.6s 33.5s 35.0s 32.5s 34.0s
Times for minikube ingress: 34.5s 37.4s 35.0s 36.9s 38.5s

Times for minikube start: 22.2s 22.1s 21.9s 21.9s 21.0s
Times for minikube (PR 11553) start: 22.6s 22.0s 21.2s 21.4s 21.3s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 46.2s    | 43.9s               |
| enable ingress |          |                     |
+----------------+----------+---------------------+

Times for minikube start: 45.8s 46.7s 43.6s 47.8s 47.1s
Times for minikube (PR 11553) start: 42.7s 42.9s 47.0s 43.1s 43.8s

@minikube-bot
Copy link
Collaborator

These are the flake rates of all failed tests on KVM_Linux_containerd.

Failed Tests Flake Rate (%)
TestErrorSpam/setup 100.00 (chart)

@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jun 23, 2021
@zigarn
Copy link
Contributor Author

zigarn commented Jun 23, 2021

/assign @spowelljr

@minikube-pr-bot
Copy link

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 47.7s    | 48.4s               |
| enable ingress | 34.9s    | 34.4s               |
+----------------+----------+---------------------+

Times for minikube start: 48.6s 47.9s 47.8s 47.1s 47.1s
Times for minikube (PR 11553) start: 47.8s 46.8s 47.3s 53.5s 46.8s

Times for minikube ingress: 35.3s 36.2s 34.8s 34.3s 34.2s
Times for minikube (PR 11553) ingress: 33.7s 34.7s 35.7s 32.8s 34.8s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 21.8s    | 21.5s               |
| enable ingress | 43.5s    | 32.7s               |
+----------------+----------+---------------------+

Times for minikube ingress: 29.0s 91.6s 28.0s 36.5s 32.5s
Times for minikube (PR 11553) ingress: 36.5s 28.5s 37.5s 29.0s 32.0s

Times for minikube start: 23.1s 21.5s 21.1s 21.5s 21.9s
Times for minikube (PR 11553) start: 22.0s 22.1s 21.0s 21.4s 21.0s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 40.6s    | 44.8s               |
| enable ingress |          |                     |
+----------------+----------+---------------------+

Times for minikube start: 31.5s 42.8s 43.2s 41.7s 43.8s
Times for minikube (PR 11553) start: 43.4s 46.4s 47.0s 44.5s 42.9s

@minikube-bot
Copy link
Collaborator

These are the flake rates of all failed tests on KVM_Linux_containerd.

Failed Tests Flake Rate (%)
TestAddons/parallel/Olm 4.65 (chart)

@spowelljr
Copy link
Member

@zigarn Sorry for the delay, just tested it and it works great!
The only thing I'd like to see added is:

Once that's added I'd be happy to merge this!

@spowelljr spowelljr removed their assignment Jul 2, 2021
@minikube-pr-bot
Copy link

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 47.5s    | 48.1s               |
| enable ingress | 35.4s    | 36.8s               |
+----------------+----------+---------------------+

Times for minikube start: 47.8s 48.9s 47.5s 47.4s 46.1s
Times for minikube (PR 11553) start: 46.8s 50.9s 47.0s 49.3s 46.7s

Times for minikube ingress: 37.3s 35.2s 34.8s 33.7s 35.8s
Times for minikube (PR 11553) ingress: 34.2s 36.7s 42.2s 34.3s 36.7s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 21.6s    | 21.2s               |
| enable ingress | 36.1s    | 35.1s               |
+----------------+----------+---------------------+

Times for minikube start: 23.1s 21.6s 21.0s 21.2s 21.5s
Times for minikube (PR 11553) start: 21.2s 21.5s 21.3s 21.3s 20.8s

Times for minikube ingress: 31.0s 37.5s 33.5s 40.5s 38.0s
Times for minikube (PR 11553) ingress: 37.4s 34.0s 34.0s 33.4s 36.5s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11553) |
+----------------+----------+---------------------+
| minikube start | 41.6s    | 43.0s               |
| enable ingress |          |                     |
+----------------+----------+---------------------+

Times for minikube start: 31.0s 43.5s 47.2s 43.2s 43.2s
Times for minikube (PR 11553) start: 42.7s 43.3s 43.1s 42.9s 43.1s

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: spowelljr, zigarn

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

The pull request process is described 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

@spowelljr spowelljr merged commit 961bbbe into kubernetes:master Jul 12, 2021
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants