Skip to content

Readiness probe value update #38

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.

Sign up for GitHub

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

Merged
Nick-Andreano merged 2 commits into from
Jan 8, 2026
Merged

Readiness probe value update #38

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9a50525
updated probe values
Nick-Andreano Jan 7, 2026
346a379
removed path from livenessProbe
Nick-Andreano Jan 7, 2026
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
29 changes: 15 additions & 14 deletions charts/iap/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -276,10 +276,11 @@ resources:
# container does not provide a liveness probe, the default state is Success. This is an exec cmd
# directly against the container checking for the core processes that IAP needs running.
livenessProbe:
enabled: false
periodSeconds: 60
timeoutSeconds: 5
failureThreshold: 10
enabled: true
initialDelaySeconds: 90
periodSeconds: 30
timeoutSeconds: 10
failureThreshold: 3
successThreshold: 1

# The readiness probe used to determine if the container is ready to accept requests. If the
Expand All @@ -288,22 +289,22 @@ livenessProbe:
# initial delay is failure. If a container does not provide a readiness probe, the default
# state is success.
readinessProbe:
enabled: false
enabled: true
initialDelaySeconds: 90
periodSeconds: 30
timeoutSeconds: 5
failureThreshold: 20
timeoutSeconds: 10
failureThreshold: 3
successThreshold: 1
path: "/health/status?exclude-services=true"

# The startup probe used to allow some time for the application to start up. The application
# will have a maximum of 3 minutes (18 * 10 = 180s) to finish its startup. Once the startup
# The startup probe used to allow some time for the application to start up. Once the startup
# probe has succeeded once, the liveness probe takes over.
startupProbe:
enabled: false
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 30
enabled: true
initialDelaySeconds: 90
periodSeconds: 30
timeoutSeconds: 10
failureThreshold: 3
successThreshold: 1
path: "/health/status?exclude-services=true"

Expand Down