-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Expose the --fail-swap-on flag for kubelet #4239
Conversation
/assign @justinsb |
Holy crap, we got 2018 all over the place. We should probably break that update into another PR :( |
i'll get rid of those pesky 2018's and update this thing |
@wannabesrevenge you want to do a 2018 PR? I will merge it quickly. Ping me on Slack if you put it in. |
@chrislovecnm can do |
Everything is wrapped and ready for scrutiny |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrislovecnm The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Closes #4123
This change exposes the "--fail-swap-on" flag for kubelet. This means that in the cluster config yaml, you can set
failSwapOn: true | false
under the kubelet config. More info on this option can be found in the referenced issue (#4123), in the kubernetes docs here, and in the kubernetes github issue here.I made this change by adding the
FailSwapOn
field to the kubelet config structs in the 3 componentconfig.go files. Then I ranmake apimachinery
to generate the rest of the changes you see.The changes involving
ImagePullProgressDeadline
, reordering some import statements, and changing the copyright to 2018 are the result of runningmake apimachinery
. They are unintended. I can undo some or all of these unintended changes if needed.