Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix startupProbe timing comment #40412

Merged
merged 1 commit into from
Jun 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions chart/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down