systemd-oomd for Fedora CoreOS #663
JaimeMagiera
started this conversation in
General
Replies: 1 comment
-
For some time this won't affect us. Later on we might experience random unexplained pod failures - kubelet uses kernel's OOM to issue OOMKilled event, so if the process is killed by systemd-oom it would look like unexplained SIGKILL sent to the process. Seems we should be disabling that by default |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The systemd-oomd service uses cgroups-v2 and pressure stall information (PSI) to monitor and take action on processes before an OOM occurs in kernel space.
https://man7.org/linux/man-pages/man8/systemd-oomd.service.8.html
In Fedora 34 systemd-oomd is enabled by default.
https://fedoraproject.org/wiki/Changes/EnableSystemdOomd
FOCS is considering enabling by default as well to maintain parity.
coreos/fedora-coreos-tracker#840
What impact, if any, would there be on OKD?
Beta Was this translation helpful? Give feedback.
All reactions