From 36f334e2a636d695862eeec3f58bb44003bc8ee9 Mon Sep 17 00:00:00 2001 From: Jed Cunningham Date: Mon, 24 Jun 2024 16:45:14 -0600 Subject: [PATCH] Fix startupProbe timing comment The default config only allows for 1 minute for each component to start up. --- chart/values.yaml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/chart/values.yaml b/chart/values.yaml index c623f3e9dd939..5e4e50dfd5538 100644 --- a/chart/values.yaml +++ b/chart/values.yaml @@ -811,13 +811,14 @@ scheduler: periodSeconds: 60 command: ~ - # Wait for at most 10 minutes (6*10s) for the scheduler container to startup. - # livenessProbe kicks in after the startup + # Wait for at most 1 minute (6*10s) for the scheduler container to startup. + # livenessProbe kicks in after the first successful startupProbe startupProbe: failureThreshold: 6 periodSeconds: 10 timeoutSeconds: 20 command: ~ + # Airflow 2.0 allows users to run multiple schedulers, # However this feature is only recommended for MySQL 8+ and Postgres replicas: 1 @@ -1252,6 +1253,8 @@ _rpcServer: periodSeconds: 10 scheme: HTTP + # Wait for at most 1 minute (6*10s) for the RPC server container to startup. + # livenessProbe kicks in after the first successful startupProbe startupProbe: timeoutSeconds: 20 failureThreshold: 6 @@ -1286,6 +1289,8 @@ webserver: periodSeconds: 10 scheme: HTTP + # Wait for at most 1 minute (6*10s) for the webserver container to startup. + # livenessProbe kicks in after the first successful startupProbe startupProbe: timeoutSeconds: 20 failureThreshold: 6