creamy-crayon-86622
10/01/2025, 5:12 PM# /usr/local/share/rke2/rke2-cis-sysctl.conf
vm.panic_on_oom=0
vm.overcommit_memory=1
kernel.panic=10
kernel.panic_on_oops=1
The vm.overcommit_memory seems questionable to me. The kernel docs (https://www.kernel.org/doc/Documentation/sysctl/vm.txt) call out:
overcommit_memory:
This value contains a flag that enables memory overcommitment.
When this flag is 0, the kernel attempts to estimate the amount
of free memory left when userspace requests more memory.
When this flag is 1, the kernel pretends there is always enough
memory until it actually runs out.
When this flag is 2, the kernel uses a "never overcommit"
policy that attempts to prevent any overcommit of memory.
Note that user_reserve_kbytes affects this policy.
This feature can be very useful because there are a lot of
programs that malloc() huge amounts of memory "just-in-case"
and don't use much of it.
The default value is 0.
Does anyone know what this has to do with CIS controls? Also why is this the default parameter? Memory seems like one of those things that you do not want to overcommit imo. Any thoughts or info would be appreciated.creamy-pencil-82913
10/01/2025, 5:49 PMcreamy-pencil-82913
10/01/2025, 5:50 PMcreamy-crayon-86622
10/01/2025, 6:22 PMcreamy-crayon-86622
10/03/2025, 12:23 PMCIS Kubernetes Benchmark v1.12 - 09-26-2025 and CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0 - 08-26-2024 but cannot find any document that refers to that configuration. The picture below doesnt show RKE2 either so maybe im missing something here. If you have any suggestions or pointers, that would be appreciated. Thanks!creamy-crayon-86622
10/03/2025, 12:49 PM