3.2 KiB
3.2 KiB
SIG Node Meeting Notes
Jan 14, 2025
-
Tim Allclair
Jan 7, 2025
-
Tim Allclair- See In Place Pod Resize - Handling Memory Limit Decreases
-
sergey- should we disable resize on cgroupv1 to avoid diff behavior?
- Mrunal: true, but we like the v1 behavior better
- How VPA can use the feature safely? This is another example of VPA cannot guarantee non-disruptive pod resize (best effort)
- Tim to follow up with VPA folks
- All checks suggested still have possibility for the race condition, the user experience will be super annoying. Should we reconsider the application of memory.high?
- should we disable resize on cgroupv1 to avoid diff behavior?
-
- Mrunal: Ask Waiman (Red Hat memory subsystem maintainer) if switching to v1 behavior is possible
- Peter: we probably need to do this to fully avoid TOCTOU / OOM kills
- Tim: Pause container to avoid TOCTOU?
- See In Place Pod Resize - Handling Memory Limit Decreases
-
Tim Allclair- See proposal section of[PUBLIC] Design proposal: Pod ResizeStatus Improvements
-
Zeel Patel- Create a KEP PR: https://github.com/kubernetes/enhancements/pull/5022
-
fromani
-
HirazawaUi- Due to the time zone difference, I regret that I am unable to attend the meeting. I have compiled the entire process of how @hshiina and I attempted to address this issue, as well as my proposal, into a detailed document: https://docs.google.com/document/d/1TPrY56q9MNW8r1FuzKDFkBBhOjQ0hqi7wJAbIP1O-4g. I sincerely hope this can be discussed during the meeting.
-
SergeyKanzhelev- State containderd and cri-o explicitly
-
kannon92 -
https://github.com/kubernetes/enhancements/pull/4113marquiz - 1.33 time is coming! https://github.com/kubernetes/sig-release/pull/2706/