-
Notifications
You must be signed in to change notification settings - Fork 39.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
Remove flags low-diskspace-threshold-mb and outofdisk-transition-frequency #48846
Conversation
Yay kill the flags! 😈 |
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.
A couple small comments.
pkg/kubelet/kubelet_node_status.go
Outdated
@@ -56,6 +56,9 @@ const ( | |||
// maxNamesPerImageInNodeStatus is max number of names per image stored in | |||
// the node status. | |||
maxNamesPerImageInNodeStatus = 5 | |||
|
|||
// mb is used to easily convert an int to an mb | |||
mb = 1024 * 1024 |
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.
There must be a helper for this somewhere, right? We do these sorts of calculations for memory limits, don't we?
Consider risk of overflow if you ever use ints for GB-size values with this, they can be 32 bits (unless you only ever divide by mb
?).
It's a nit but differentiating between MB and Mb is also sometimes important.
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.
Is this constant still used? I don't see it show up anywhere in this PR except for removed code.
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.
It was used in a test file. But the numbers didnt actually matter, so I removed this.
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.
SG
/retest |
Still need to remove |
9cda7b5
to
04459f0
Compare
/test pull-kubernetes-federation-e2e-gce |
/unassign |
/lgtm looks like you need to rebase but the bot didn't add the label :\ |
f8b62c8
to
aced667
Compare
c640b7d
to
5e65014
Compare
/test pull-kubernetes-kubemark-e2e-gce |
/lgtm |
/assign @smarterclayton |
/approve Deprecation was announced and communicated over several releases, consistent with other flags removed from the Kubelet. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dashpole, mtaufen, smarterclayton Associated issue: 48843 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 |
Automatic merge from submit-queue |
Automatic merge from submit-queue (batch tested with PRs 49237, 49656, 49980, 49841, 49899) [Bug Fix] Set NodeOODCondition to false fixes #49839, which was introduced by #48846 This PR makes the kubelet set NodeOODCondition to false, so that the scheduler and other controllers do not consider the node to be unschedulable. /assign @vishh /sig node /release-note-none
issue: #48843
This removes two flags replaced by the eviction manager. These have been depreciated for two releases, which I believe correctly follows the kubernetes depreciation guidelines.
cc @mtaufen since I am changing kubelet flags
cc @vishh @derekwaynecarr
/sig node