Skip to content

Commit 20176bb

Browse files
committed
Disable the readiness probe
Our terminationGracePeriodSeconds is set to 600 by default. However, since the readinessProbe will start failing immediately after the manager shutdown is initiated, any remaining work will be terminated once the readiness probe failure threshold is reached (30s by default) and the pod will receive another SIGTERM. This change removes the readinessProbe configuration and allows the helm-controller manager to correctly handle graceful termination without being interrupted by the readinessProbe failure. Signed-off-by: Aurel Canciu <aurelcanciu@gmail.com>
1 parent e242bb0 commit 20176bb

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

config/manager/deployment.yaml

-4
Original file line numberDiff line numberDiff line change
@@ -51,10 +51,6 @@ spec:
5151
- --log-level=info
5252
- --log-encoding=json
5353
- --enable-leader-election
54-
readinessProbe:
55-
httpGet:
56-
path: /readyz
57-
port: healthz
5854
livenessProbe:
5955
httpGet:
6056
path: /healthz

0 commit comments

Comments
 (0)