From d5fdf65656f2b7c37bf545d9ab075f5cb73fdcea Mon Sep 17 00:00:00 2001
From: Maxime Beauchamp <15185355+baktun14@users.noreply.github.com>
Date: Fri, 25 Sep 2026 17:31:59 +0400
Subject: [PATCH] fix(provider-proxy): stop one slow status probe from
 restarting the only replica

Both probes called /status with a 5s timeout and failureThreshold 1, and
the deployment ran exactly one replica, so a single answer slower than 5s
restarted the container and took provider-proxy down until the new one was
ready. That happened on 2026-09-23 at 15:21 UTC and on 2026-09-25 at
10:26 UTC.

Liveness now restarts after 3 failed checks in a row and readiness drops
the pod after 2. The replica count is read from values, defaulting to 1.
The chart moves to 0.7.7 and the nodejs-app pin to 0.4.2, because with the
0.4.1 pin helm dependency build fails and the chart would not publish.
---
 charts/provider-proxy/Chart.lock                | 6 +++---
 charts/provider-proxy/Chart.yaml                | 4 ++--
 charts/provider-proxy/templates/deployment.yaml | 6 +++---
 charts/provider-proxy/values.yaml               | 1 +
 4 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/charts/provider-proxy/Chart.lock b/charts/provider-proxy/Chart.lock
index 40404487..22b3abcb 100644
--- a/charts/provider-proxy/Chart.lock
+++ b/charts/provider-proxy/Chart.lock
@@ -1,6 +1,6 @@
 dependencies:
 - name: nodejs-app
   repository: file://../nodejs-app
-  version: 0.4.1
-digest: sha256:94e236aa9486039f873f0eecce286baf1cf811fa57966a1807eb7d289c66dcea
-generated: "2026-05-06T22:14:32.99749+02:00"
+  version: 0.4.2
+digest: sha256:c974280c995d2a5a323b8960ffc2b46c144605d1fae25806006ffa02bc3651cc
+generated: "2026-09-25T17:29:54.173923+04:00"
diff --git a/charts/provider-proxy/Chart.yaml b/charts/provider-proxy/Chart.yaml
index aa6b7b58..48d17d54 100644
--- a/charts/provider-proxy/Chart.yaml
+++ b/charts/provider-proxy/Chart.yaml
@@ -14,7 +14,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.7.6
+version: 0.7.7
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
@@ -23,5 +23,5 @@ appVersion: "1.13.3"
 
 dependencies:
   - name: nodejs-app
-    version: 0.4.1
+    version: 0.4.2
     repository: "file://../nodejs-app"
diff --git a/charts/provider-proxy/templates/deployment.yaml b/charts/provider-proxy/templates/deployment.yaml
index ff54e84a..9ba03c1a 100644
--- a/charts/provider-proxy/templates/deployment.yaml
+++ b/charts/provider-proxy/templates/deployment.yaml
@@ -8,7 +8,7 @@ metadata:
   annotations:
     secrets.doppler.com/reload: 'true'
 spec:
-  replicas: 1
+  replicas: {{ .Values.replicas | default 1 }}
   selector:
     matchLabels:
       app: {{ .Chart.Name }}-{{ .Values.chain }}
@@ -39,7 +39,7 @@ spec:
             initialDelaySeconds: 5
             periodSeconds: 10
             timeoutSeconds: 5
-            failureThreshold: 1
+            failureThreshold: 2
           livenessProbe:
             httpGet:
               path: /status
@@ -47,4 +47,4 @@ spec:
             initialDelaySeconds: 5
             periodSeconds: 10
             timeoutSeconds: 5
-            failureThreshold: 1
+            failureThreshold: 3
diff --git a/charts/provider-proxy/values.yaml b/charts/provider-proxy/values.yaml
index 11a73b00..237bd044 100644
--- a/charts/provider-proxy/values.yaml
+++ b/charts/provider-proxy/values.yaml
@@ -2,6 +2,7 @@ appVersion: "1.4.3"
 hostNames: []
 chain: sandbox
 deploymentEnv: staging
+replicas: 1
 
 otel:
   enabled: true