From b7df8e4abbd4b1e5973ab6d12d6d8e513cc7f796 Mon Sep 17 00:00:00 2001
From: okozachenko <okozachenko@vexxhost.com>
Date: Tue, 4 Nov 2025 01:25:53 +0100
Subject: [PATCH] fix: set maxUnavailable for ovs rolling update strategy

maxSurge and maxUnavailable are mutually exclusive in the DaemonSet update logic.
When maxSurge is non-zero, maxUnavailable is ignored; when maxSurge is zero, only maxUnavailable is used.
We need to make sure availability so keep maxUnavailable.

Signed-off-by: okozachenko <okozachenko@vexxhost.com>
---
 openvswitch/values.yaml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/openvswitch/values.yaml b/openvswitch/values.yaml
index 60c4de542..c9eb9d432 100644
--- a/openvswitch/values.yaml
+++ b/openvswitch/values.yaml
@@ -112,8 +112,7 @@ pod:
         ovs:
           enabled: true
           min_ready_seconds: 0
-          max_unavailable: 0
-          max_surge: 1
+          max_unavailable: 1
   resources:
     enabled: false
     ovs: