Meilisearch may read host memory instead of container limits in Kubernetes

In Kubernetes deployments, Meilisearch may read the total RAM of the host node instead of respecting cgroup container memory limits, leading to memory allocation decisions based on incorrect available memory values and potential OOM kills.

Verify memory detection by checking Meilisearch startup logs with --log-level DEBUG. Compare detected memory against container limits. Explicitly set max_indexing_memory based on actual container limits rather than relying on auto-detection. Monitor for correlation between increased memory usage in v1.13.x and containerized environments.