-
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
kubelet: Pass --config to use kubeadm generated configuration #5697
Conversation
Hi @nanikjava. 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? |
Travis tests have failedHey @nanikjava, 1st Buildmake test
TravisBuddy Request Identifier: 2d2f33d0-f514-11e9-9e2b-01a46d152451 |
Tested for both kvm2 and vbox. Test done by changing the value inside pkg/minikube/bootstrapper/kubeadm/templates.go
Following is kubelet log when reading the config.yaml (using 0,0,0 as evictionHard value)
Following is kubelet log when reading the config.yaml (using 10,10,10 as evictionHard value)
|
…es#5329 Kubelet startup parameters does not include the --config flag. This flag pass the location of the configuration file. During minikube startup process this file is copied over to the VM. Fix test cases.
Codecov Report
@@ Coverage Diff @@
## master #5697 +/- ##
=======================================
Coverage 37.83% 37.83%
=======================================
Files 106 106
Lines 7773 7773
=======================================
Hits 2941 2941
Misses 4452 4452
Partials 380 380
|
/retest |
@nanikjava: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
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. |
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 great. Thank you for fixing this!
@minikube-bot OK to test |
/ok-to-test |
It seems some (if not most) kubelet parameters are now duplicated in kubelet commandline and config.yaml file. I'm not even sure if all the values are the same:
|
Can you please open a separate ticket issue for the above so we can take a look at it separately so it's easier to track. Thanks |
Thanks @thomas-riccardi Will wait for feedback from the reviewers about this. |
This overlap is intentional, because at first, very few kubelet flags were exposed by kubeadm. Flags always take precedence over configuration files. Here is my guidance:
Unless someone sees something I'm not, I think the conflict is OK as is. User-provided flags will still take precedence. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: nanikjava 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 |
FYI, I think this PR is doing the right thing, and I would like to merge it in order to solve #5751 correctly, by asking kubeadm to program kubelet for setting set file limits. |
/ok-to-test |
#5329
Kubelet startup parameters does not include the --config flag. This flag pass the
location of the configuration file. During minikube startup process this file
is copied over to the VM. Fix test cases.