-
Notifications
You must be signed in to change notification settings - Fork 39.3k
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
Deprecate and remove flags and conditions replaced by eviction flags and conditions. #48843
Comments
@dashpole There are no sig labels on this issue. Please add a sig label by: |
cc @vishh @derekwaynecarr |
Automatic merge from submit-queue Remove flags low-diskspace-threshold-mb and outofdisk-transition-frequency 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. ```release-note Remove depreciated flags: --low-diskspace-threshold-mb and --outofdisk-transition-frequency, which are replaced by --eviction-hard ``` cc @mtaufen since I am changing kubelet flags cc @vishh @derekwaynecarr /sig node
Automatic merge from submit-queue (batch tested with PRs 51915, 51294, 51562, 51911) Remove OutOfDisk from controllers This is one of the working items for #48843 for 1.8. This changes the scheduler and daemonset controllers to no longer respect the OutOfDisk condition. The kubelet has not published OutOfDisk=True since 1.5. This still preserves the Toleration for the OutOfDisk condition, as (I think?) this is required for backwards compatibility. I added TODOs to remove this in 1.10.
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
/remove-lifecycle stale |
does two task can do go head? @dashpole 1.10+: Remove kubelet generation of the OutOfDisk condition
1.10+: Remove the OutOfDisk condition if can , i glad to do that. |
I dont think we can actually remove the OOD condition, but the kubelet shouldn't need to generate it anymore. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. 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. |
The deprecated flags are documented here.
--low-diskspace-threshold-mb
and--outofdisk-transition-frequency
kubelet flags.--low-diskspace-threshold-mb
to 0, which causes the OutOfDisk condition to never trigger.--low-diskspace-threshold-mb
and--outofdisk-transition-frequency
kubelet flags, and the kubelet disk manager.The text was updated successfully, but these errors were encountered: