-
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 new --extra-config option "scheduler" #8147
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. I understand the commands that are listed here. |
Welcome @nezorflame! |
Hi @nezorflame. 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? |
CLA signed. |
/assign @medyagh |
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.
while this is a good PR ! I think we could do even better,
instead of waiting to fail the way here, we could detect and return without crashing.
here are options, we could add a helper func in start.go inside ValidateFlags
and we could validate the extra arg is okay. so the users get a faster resonse
the second option would make an ErrorType and return that error type for example and the caller can exit.WithUsage("Please ...blahblah") instead of crashing example of using the ErrorType can be found in kverify package
|
Codecov Report
@@ Coverage Diff @@
## master #8147 +/- ##
==========================================
- Coverage 35.27% 35.26% -0.02%
==========================================
Files 146 146
Lines 9326 9342 +16
==========================================
+ Hits 3290 3294 +4
- Misses 5637 5649 +12
Partials 399 399
|
Added a separate public validation func with test and used it inside of the Example output:
Not sure about the formatting, would like an opinion here. |
Codecov Report
@@ Coverage Diff @@
## master #8147 +/- ##
==========================================
- Coverage 35.27% 34.44% -0.83%
==========================================
Files 146 147 +1
Lines 9326 9443 +117
==========================================
- Hits 3290 3253 -37
- Misses 5637 5791 +154
Partials 399 399
|
@medyagh any chance you'll have some time to re-review this? |
@nezorflame do you mind updating the Before and After, we should fail fast Before configuring the cluster and use exit.WithUsage and also could you please pull the master too ? |
/ok-to-test |
kvm2 Driver |
Tests look OK - do you mind resolving the conflict so that this can be merged? |
Yup, will do it this week.
…_____________________________
Best regards,
Ilya Danilkin
С уважением,
Илья Данилкин
ср, 24 июн. 2020 г., 21:13 Thomas Strömberg <notifications@github.com>:
Tests look OK - do you mind resolving the conflict so that this can be
merged?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8147 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5ZZTSPM5BG7DXFRECHJWLRYI63HANCNFSM4NAY7DYQ>
.
|
60f1230
to
b470860
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: nezorflame 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 |
fe1fecf
to
b470860
Compare
@tstromberg done, now need to wait for the checks :) |
Travis tests have failedHey @nezorflame, 1st Buildmake test
TravisBuddy Request Identifier: 9aefce50-b979-11ea-a74d-ef5d1a577ce8 |
kvm2 Driver Times for Minikube (PR 8147): [66.60426911200001 64.890782119 64.736219276] Averages Time Per Log
docker Driver Times for Minikube (PR 8147): [26.076823896 27.623987482000004 27.251079315999995] Averages Time Per Log
|
kvm2 Driver Times for Minikube (PR 8147): [61.44879126299999 61.968026349 63.620719578999996] Averages Time Per Log
docker Driver Times for Minikube (PR 8147): [26.081426583 25.747434673 26.491521845] Averages Time Per Log
|
--extra-config
parsingThere 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.
@nezorflame thank you for this PR and your patience while it was under review
This PR fixes the error message for the
--extra-config
option parsing for theminikube start
command (also mentioned in #6689).Seems like it was a simple copy-paste issue in the original commit.
Example:
minikube start --extra-config=kubeProxy.IPTables.SyncPeriod.Duration=5000000000
Before (failing during the process of setup):
After (validation check during the initialization):