-
Describe the bugI setup me resources as follows My vm_memory_high_watermark is set to 0.7 I expected the watermark to be 0.7*6Gi , but what I see in the logs is Memory high watermark set to 3440 MiB (3607772529 bytes) of 4915 MiB (5153960756 bytes) total Not sure why the max is set to 4915 MiB and not to 6144 MiB When I login to the container , I see the full amount that is assigned to the host Version and environment information
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @bdaoudtdc, I have converted the issue to a discussion since this is expected behavior and not a bug. A while back we added a feature to cluster operator so it provides headroom for the memory limit (see: cluster-operator/internal/resource/configmap_test.go Lines 505 to 516 in c813d56 |
Beta Was this translation helpful? Give feedback.
Hi @bdaoudtdc, I have converted the issue to a discussion since this is expected behavior and not a bug. A while back we added a feature to cluster operator so it provides headroom for the memory limit (see:
cluster-operator/internal/resource/configmap_test.go
Lines 505 to 516 in c813d56