-
Notifications
You must be signed in to change notification settings - Fork 6
fix(helm): add liveliness and readiness probes to helm chart #143
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -201,6 +201,33 @@ properties: | |
| description: "List of capabilities to drop" | ||
| description: "Container-level security context" | ||
|
|
||
| terminationGracePeriodSeconds: | ||
| type: integer | ||
| minimum: 1 | ||
| description: "Duration in seconds the pod needs to terminate gracefully. Must be greater than preStopSleepSeconds." | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Can we have a check for this?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Added a check for this in the |
||
| default: 30 | ||
|
|
||
| preStopSleepSeconds: | ||
| type: integer | ||
| minimum: 0 | ||
| description: "Seconds to sleep in preStop hook before SIGTERM, allowing Kubernetes endpoint propagation. Set to 0 to disable." | ||
| default: 15 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Default value below is
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How can we make these types of check in a helm chart?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Currently the schema is ignored in the checks because it is a In this PR i just changed the |
||
|
|
||
| startupProbe: | ||
| type: object | ||
| additionalProperties: true | ||
| description: "Startup probe configuration. Disables liveness/readiness probes until startup succeeds." | ||
|
|
||
| livenessProbe: | ||
| type: object | ||
| additionalProperties: true | ||
| description: "Liveness probe configuration. Determines if the container should be restarted." | ||
|
|
||
| readinessProbe: | ||
| type: object | ||
| additionalProperties: true | ||
| description: "Readiness probe configuration. Determines if the container should receive traffic." | ||
|
|
||
| nodeSelector: | ||
| type: object | ||
| additionalProperties: | ||
|
|
@@ -299,4 +326,4 @@ properties: | |
| description: "Name of the image pull secret" | ||
|
|
||
| required: | ||
| - service | ||
| - service | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we need to enable the health endpoint? Currently, when running this inside a >>> import httpx
>>> httpx.get("http://localhost:8000/healthz")
<Response [404 Not Found]>
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The healthz path DOES include the
alukach marked this conversation as resolved.
|
Uh oh!
There was an error while loading. Please reload this page.