-
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
add VerifiedMaintainer field to Addons and display a warning if empty #14499
Conversation
Hi @inifares23lab. 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? |
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.
Hi @inifares23lab, there are a lot of formatting problems in this PR, could you run gofmt -w -s .
to resolve them and then push the changes up, thanks.
Hi @spowelljr |
Hi @inifares23lab, thanks for formatting the code. Could you wrap all For example Could you also add If the
For the rest of addons could you update your message to:
And for 3rd party addons, if there's a verified maintainer for the addon could you also add the following line:
|
Hello
examples: ❗ ambassador is A 3rd party addon and not maintained or verified by minikube maintainers, enable at your own risk. 💡 metallb is maintained by 3rd party (MetalLB) for any concerns contact MOCK-VERIFI |
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.
The Google/Kubernetes and no verified maintainer case is perfect.
But if it's a 3rd party and has a verified maintainer it should have both messages:
<addon_name> is A 3rd party addon and not maintained or verified by minikube maintainers, enable at your own risk.
<addon_name> is maintained by <maintainer> for any concerns contact <verified_maintaer> on GitHub.
That ways they're notified it's a 3rd party addon and to enable at their own risk, but also pointed to someone if they have troubles.
Hi @spowelljr I agree that displaying both messages is more clear for the user, however I have one concern:
It may be better to further customize the messages for the two cases:
Let me know if it makes sense to you |
Hi @inifares23lab, I know in the issue I originally mentioned a verified maintainer but that was just something I quickly jotted down and should have named it something else. The field can be called anything, So the message: |
understood, thank you for clarifying. |
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.
Looks good! Just a few last comments
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube ingress: 29.0s 29.5s 28.6s 25.6s 28.5s Times for minikube start: 56.0s 54.7s 55.2s 55.9s 55.7s docker driver with docker runtime |
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. |
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.
Looks good, thanks for your work on this!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: inifares23lab, spowelljr 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 |
The Addon type now has another string Field: VerifiedMaintainer
The new field is added to the NewAddon function and to the Addons map.
When enabling an addon if the VerifiedMaintainer field is empty a warning message is displayed:
! The <ADDON_NAME> addon doesn't have a verified maintainer.
Since for now I just added an empty string for every addon, it will always display the warning when enabling
fixes #14493