-
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
addon list: Add info on each addon's maintainer #11753
Conversation
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.
plz paste the output in the pr description list
@medyagh I knew I was missing something obvious :P |
Can one of the admins verify this patch? |
/ok-to-test |
pkg/minikube/assets/addons.go
Outdated
@@ -311,7 +313,7 @@ var Addons = map[string]*Addon{ | |||
vmpath.GuestAddonsDir, | |||
"olm.yaml", | |||
"0640"), | |||
}, false, "olm", map[string]string{ | |||
}, false, "olm", "OLM", map[string]string{ |
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.
this could be change t third party till we confirm
and also instead of OLM we could use their github org
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.
we should create a follow up issue to contact the owners of those repos to see if they consent their org to be added offically as maintainer/responsible fr this addon, so in case olm image has anything malscious in it, they be point of contact for it ?
or maybe we could use the company name redhat for olm addon?
kvm2 driver with docker runtime
Times for minikube ingress: 42.3s 34.3s 42.2s 41.7s 43.3s Times for minikube start: 49.1s 46.1s 46.9s 46.6s 45.5s docker driver with docker runtime
Times for minikube ingress: 38.0s 38.0s 43.5s 37.5s 34.5s Times for minikube start: 21.2s 21.1s 20.9s 22.1s 21.5s docker driver with containerd runtime
Times for minikube start: 47.3s 47.3s 43.5s 42.3s 47.8s |
These are the flake rates of all failed tests on KVM_Linux_containerd.
|
310773b
to
5f5a0c7
Compare
kvm2 driver with docker runtime
Times for minikube start: 54.4s 47.9s 55.2s 47.7s 47.0s Times for minikube ingress: 36.4s 33.7s 33.7s 33.7s 34.3s docker driver with docker runtime
Times for minikube start: 22.0s 22.4s 22.8s 23.5s 22.1s Times for minikube ingress: 29.0s 29.0s 29.5s 31.5s 27.5s docker driver with containerd runtime
Times for minikube start: 45.1s 47.3s 44.7s 44.2s 43.4s |
These are the flake rates of all failed tests on Docker_Linux.
|
5f5a0c7
to
2f523eb
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andriyDev, 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 |
kvm2 driver with docker runtime
Times for minikube (PR 11753) start: 51.6s 47.1s 47.1s 47.1s 46.7s Times for minikube (PR 11753) ingress: 34.8s 41.7s 39.2s 34.8s 35.3s docker driver with docker runtime
Times for minikube ingress: 33.4s 38.5s 33.5s 34.5s 33.5s Times for minikube start: 22.3s 21.7s 21.4s 21.4s 21.5s docker driver with containerd runtime
Times for minikube start: 30.9s 47.2s 43.4s 43.9s 43.4s |
These are the flake rates of all failed tests on Docker_Linux.
|
fixes #11444.
Some of these addons still need proper maintainers, we need to ask those who created the addons whether they are willing to be points of contact.