The 512 MiB cgroup on 2026-11-15 at 13:49 UTC: full, with most of the top made of page cache the kernel can reclaim.
If your MinIO memory usage is high on Kubernetes ( kubectl top shows 495Mi against a 512Mi limit, an audit reports 7d memory working set p95 / limit = 0.95 ) but you never see a MinIO pod OOMKilled ( container_oom_events_total is still 0 ), MinIO is probably not leaking: community releases read the container's own cgroup memory.max and use 90 % of it as their budget (since PR #19839, May 2024, this includes the Go soft memory limit), so the memory fills the limit by design. To see whether yours is the same case, read the pod's cgroup (step 2 below): it is the same case when memory.current is within a few MB of memory.max , anon stays under 90 % of memory.max , and memory.events shows oom_kill 0 . The cluster is a 2-node k3s cluster that I run ( server-1 and agent-1 ); MinIO runs as a single-replica StatefulSet minio , pod minio-0 , one drive, image minio/minio:RELEASE.2025-04-22T22-12-26Z .…