-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
multi-node: Add support for volumes using CSI addon #15829
Conversation
Welcome @denisok! |
Hi @denisok. 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 Once the patch is verified, the new status will be reflected by the 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. |
Can one of the admins verify this patch? |
containers: | ||
- name: csi-external-health-monitor-agent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
health-agent was merged to kubelet: https://github.com/kubernetes-csi/external-health-monitor#overview
@@ -92,12 +96,24 @@ metadata: | |||
rules: | |||
# Only one of the following rules for endpoints or leases is required based on | |||
# what is set for `--leader-election-type`. Endpoints are deprecated in favor of Leases. | |||
- apiGroups: [""] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you mind adding output of minikube Before / After this PR?
also, it would be nice to add a section on multinode use example in our website
https://minikube.sigs.k8s.io/docs/tutorials/volume_snapshots_and_csi/
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube ingress: 27.7s 26.7s 24.7s 26.7s 24.2s Times for minikube (PR 15829) start: 55.0s 53.9s 53.3s 49.9s 53.7s docker driver with docker runtime
Times for minikube start: 25.1s 25.6s 26.2s 27.4s 26.9s Times for minikube ingress: 20.0s 22.0s 23.0s 21.0s 82.6s docker driver with containerd runtime
Times for minikube (PR 15829) start: 20.8s 21.1s 21.6s 21.7s 22.0s Times for minikube ingress: 80.0s 18.6s 31.6s 31.6s 31.6s |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
sure, here evertyhing with
|
I see some failures related to csi, will check it. |
OK, I looked to some of the tests, and those failures related to I tried different confirurations and don't see any issues with kvm or podman driver, Once I seen the issue minikube starting with podman and cri-o - Node wasn't ready and thus containers were in
But it was only once and I can't reproduce it.
needs re-run. |
Hi @medyagh, I added docs and checked tests. So far I found no regressions. Thanks, |
kvm2 driver with docker runtime
Times for minikube start: 54.0s 53.6s 53.0s 52.9s 53.3s Times for minikube ingress: 25.7s 27.7s 29.2s 24.2s 26.4s docker driver with docker runtime
Times for minikube start: 26.4s 26.0s 25.9s 26.6s 26.6s Times for minikube ingress: 21.1s 20.1s 22.1s 21.1s 22.1s docker driver with containerd runtime
Times for minikube start: 22.3s 21.8s 23.1s 21.9s 22.0s Times for minikube ingress: 32.6s 32.6s 20.6s 31.6s 32.6s |
kvm2 driver with docker runtime
Times for minikube (PR 15829) start: 57.1s 55.0s 54.5s 56.7s 56.0s Times for minikube ingress: 28.4s 29.8s 28.9s 24.8s 25.8s docker driver with docker runtime
Times for minikube start: 28.5s 28.9s 28.7s 27.0s 28.4s Times for minikube ingress: 21.1s 22.6s 82.6s 22.2s 19.1s docker driver with containerd runtime
Times for minikube (PR 15829) ingress: 79.6s 21.6s 31.6s 20.6s 32.7s Times for minikube (PR 15829) start: 23.2s 23.1s 23.4s 23.5s 23.1s |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
I can't make any sense from test results. could someone help me to see where should I look into? Should be they all green? |
kvm2 driver with docker runtime
Times for minikube start: 57.9s 59.9s 57.6s 59.6s 59.3s Times for minikube ingress: 31.4s 30.5s 29.4s 30.9s 30.4s docker driver with docker runtime
Times for minikube start: 29.1s 28.6s 28.8s 29.6s 29.3s Times for minikube ingress: 21.2s 25.7s 22.2s 81.7s 21.3s docker driver with containerd runtime
Times for minikube start: 23.6s 24.8s 24.6s 24.2s 25.2s Times for minikube ingress: 47.8s 47.7s 32.3s 28.2s 31.7s |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this PR, please consider making a follow UP PR that when users use multi-node, minikube automatically enable this addon for them or suggests them to do so
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: denisok, medyagh 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 |
fixes #12360