From 5f5863574485d77b72e6b7eea0ee032be81a5c57 Mon Sep 17 00:00:00 2001 From: Pavan Gudiwada <25551553+pavangudiwada@users.noreply.github.com> Date: Thu, 11 Apr 2024 16:38:14 +0530 Subject: [PATCH] Added docs about Popeye not running on Arm (#1376) Co-authored-by: Pavan Gudiwada Co-authored-by: Natan Yellin --- docs/playbook-reference/actions/scans.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/playbook-reference/actions/scans.rst b/docs/playbook-reference/actions/scans.rst index ee33510ed..438cbfd7f 100644 --- a/docs/playbook-reference/actions/scans.rst +++ b/docs/playbook-reference/actions/scans.rst @@ -75,7 +75,7 @@ If you are having performance issues, specifically with Prometheus using a lot o globalConfig: krr_args: "--cpu-min 15 --mem-min 200 --cpu_percentile 90 --memory_buffer_percentage 25" - max_workers: 2 + max_workers: 2 **Common KRR Settings** @@ -191,8 +191,13 @@ To set custom tolerations or a nodeSelector update your ``generated_values.yaml` operator: "Exists" effect: "NoSchedule" nodeSelector: + kubernetes.io/arch: "amd64" nodeName: "your-selector" +.. Note:: + + Popeye does `not support `_ arm nodes yet. If your cluster has both Arm and x64 nodes add ``kubernetes.io/arch: "amd64"`` as a node selector to schedule Popeye jobs on the x64 nodes. + Troubleshooting Popeye =======================