[rhanka]

The first half-memory deployment reached OVH through GitHub Actions but Elasticsearch was repeatedly OOMKilled immediately after its native Machine Learning controller started. This disables ML in the dev overlay while preserving the requested 256Mi memory request, 512Mi limit, and -Xms256m -Xmx256m heap.

An identical Elasticsearch 8.6.1 container with the same 512Mi limit and 256m heap reached green health and remained running at about 463–467MiB after this setting was applied.

Validation:

• kubectl kustomize deploy/k8s/overlays/dev
• kubectl apply --dry-run=client --validate=false
• local Elasticsearch 8.6.1 startup and green health under a 512Mi cgroup limit
• harness check scope
• harness check branch
• AGY Gemini 3.8 review: GO

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: df1cfb32-e21e-484c-a1c3-821cdc6abec5

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}