From 3f230251b4f98e0dde5ec07c9a0246284c3f5ea3 Mon Sep 17 00:00:00 2001
From: Vasyl Saienko <vsaienko@mirantis.com>
Date: Wed, 18 Dec 2024 11:06:54 +0000
Subject: [PATCH] [memcached] Drop max_surge option

We do not use service proxy to comminicate to memcached.
All services has exact number of endpoints to communicate.
Having max_surge is useless as clients will never use it.

Change-Id: I74a665c96cfc99cbb8d31c4a17700c467c746c9e
---
 memcached/values.yaml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/memcached/values.yaml b/memcached/values.yaml
index a23d2c366..d6e0e8999 100644
--- a/memcached/values.yaml
+++ b/memcached/values.yaml
@@ -203,7 +203,6 @@ pod:
         pod_replacement_strategy: RollingUpdate
         revision_history: 3
         rolling_update:
-          max_surge: 3
           max_unavailable: 1
     termination_grace_period:
       memcached: