From 1a3a0d2b2a3578ccdaa68bc8b32f763a0d0bb6c3 Mon Sep 17 00:00:00 2001 From: Saurab Sonigra <67898315+ssonigra@users.noreply.github.com> Date: Wed, 5 Aug 2026 14:21:30 +0530 Subject: [PATCH] multus: Remove NoSchedule effect from tolerations Removed NoSchedule effect from tolerations in multus.yaml. As per bug https://redhat.atlassian.net/browse/OCPBUGS-77772 , the NoSchedule Effect is causing an issue with placement of the pods on the nodes where taint NoSchedule is added also as per the standard the toleration is only operator: Exists for all the other pods. Signed-off-by: Saurab Sonigra --- bindata/network/multus/multus.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/bindata/network/multus/multus.yaml b/bindata/network/multus/multus.yaml index 9e9b7ff9f9..a7f9e3eca5 100644 --- a/bindata/network/multus/multus.yaml +++ b/bindata/network/multus/multus.yaml @@ -652,7 +652,6 @@ spec: priorityClassName: "system-node-critical" tolerations: - operator: Exists - effect: NoSchedule containers: - name: whereabouts command: [ "/bin/sh" ]