From af8451a9c15f7b79a3bd3b29f4bac0088c7d0a00 Mon Sep 17 00:00:00 2001 From: Pavan Gudiwada <25551553+pavangudiwada@users.noreply.github.com> Date: Wed, 15 May 2024 12:36:41 +0530 Subject: [PATCH] Updated KRR OOMkill docs (#1418) Co-authored-by: Pavan Gudiwada --- docs/playbook-reference/actions/scans.rst | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/playbook-reference/actions/scans.rst b/docs/playbook-reference/actions/scans.rst index 438cbfd7f..4ea65fd8b 100644 --- a/docs/playbook-reference/actions/scans.rst +++ b/docs/playbook-reference/actions/scans.rst @@ -116,7 +116,21 @@ If you are having performance issues, specifically with Prometheus using a lot o - The number of data points required to make a recommendation for a resource. - 100 +Configuring KRR Job Memory Requests and Limits +====================================================== +To prevent the KRR job from OOMKill (Out of Memory), you can configure the memory requests and limits by adding the following environment variables to your ``generated_values.yaml`` file: + +.. code-block:: yaml + + runner: + additional_env_vars: + - name: KRR_MEMORY_REQUEST + value: "2Gi" + - name: KRR_MEMORY_LIMIT + value: "2Gi" + +By default, the memory request and limit are set to ``1Gi``. Modify these values according to your requirements. Popeye - A Kubernetes Cluster Sanitizer ************************************************