8 Commits

Author	SHA1	Message	Date
Dixita Narang	d2dbc583a0	Adding coverage for OOM Kill scenario due to node allocatable memory limits, when pod level memory limits are not set	2023-08-22 00:45:17 +00:00
Todd Neal	905f07f1ac	Revert "mark the OOM killer as serial to reduce flakes" ... This reverts commit bd6f548746. Running as serial didn't completely eliminate the flake so I think there's something more going on here. Reverting the change to serial since its not a solution.	2023-08-20 13:38:07 -05:00
Todd Neal	bd6f548746	mark the OOM killer as serial to reduce flakes ... In testing I could only reproduce the flake by running stress-ng to load the CPU. Running it as serial should reduce and hopefully eliminate the flakiness.	2023-08-18 13:18:50 -05:00
Kubernetes Prow Robot	3111fee8bf	Merge pull request #119670 from lengrongfu/fix/oomkill-multi-target-container ... fix OOM killer	2023-08-15 19:43:40 -07:00
lengrongfu	c23cee1be3	fix OOM killer ... Signed-off-by: lengrongfu <rongfu.leng@daocloud.io>	2023-07-30 11:16:12 +08:00
CoderSherlock	b7cbebcd03	Added oomkill test for init container and fix typos	2023-07-13 17:19:34 +00:00
Stanislav Laznicka	7f532891c9	e2e tests: set all PSa labels instead of just enforcing	2023-06-21 15:05:13 +02:00
Todd Neal	4e20a8f52b	kill all processes in a container in the event of OOM ... Set memory.oom.group if using cgroups v2 unified mode so all processes in the container will be killed together in the event of an OOM kill.	2023-06-12 15:49:01 -05:00