Set a memory limit on the container
A container with no memory limit, or with mem_limit set to 0, can grow until the host runs out of memory.
Zero is not a limit
In Compose, `mem_limit: 0` means no cap. Leaving `mem_limit` out means the same thing. `mem_reservation` is not a cap. In a Pod, a container with no `resources.limits.memory` has no memory limit in that file. `resources.requests.memory` does not set one.
The missing-memory-limit check looks for a container with no memory limit, or a Compose memory limit of 0. It reads the workload text. It does not measure live memory use. A limit that exists only as a cluster policy, outside the file, is not visible to it. When the host runs out of memory, the kernel does not have to kill the container that grew.
Write the number on the container
Delete `mem_limit: 0`. Don't lower it and call that a limit. Put a number you can explain on that container: `mem_limit: 512m` in Compose, or `resources.limits.memory: 512Mi` in the Pod. A limit on a sibling container does not cover this one.
Paste the Compose file or the manifest and ask for the limit line, with the container name. If the line is missing, say so. Don't assume the cluster adds one later.