migrate to kubelet config file#96
Conversation
|
/cc @derekwaynecarr |
ashcrow
left a comment
There was a problem hiding this comment.
I did a quick look through and it looks good.
There was a problem hiding this comment.
why this extra line ?
There was a problem hiding this comment.
fixed in 0ee9e75.
|
/test unit |
|
/approve @aaronlevy do you mind taking a quick look |
|
To my naive eyes this lgtm. I'm assuming flags that are left over are not represented in the config file? Might want someone else from pod team / someone more familiar with kubelet mechanics to take a pass - but could always be follow up. Not strictly related to this, but could also drop |
|
Removed the |
|
One last question is that it looks like |
|
/approve cancel
@aaronlevy good catch. |
dae4d2a to
459ce44
Compare
|
@aaronlevy good catch. fixed and squashed. |
|
This has been dragging on (apologies) so I can lgtm, but also just noticed that |
459ce44 to
b17b7b2
Compare
|
@aaronlevy updated to remove the lock |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aaronlevy, abhinavdahiya, rphillips The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Migrates the kubelet to a kubelet.conf file.
The customer typically had to set configuration settings within the kubelet unit file and pass command-line flags to reconfigure the Kubelet. With this patch, the configuration file will allow a subset of options to be set by the customer.