feat: add optional healthcheck for node-driver-registrar#1026
feat: add optional healthcheck for node-driver-registrar#1026k8s-ci-robot merged 4 commits intokubernetes-csi:masterfrom
Conversation
|
Welcome @ajhetherington! |
|
Hi @ajhetherington. Thanks for your PR. I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Pull Request Test Coverage Report for Build 21511840528Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
andyzhangx
left a comment
There was a problem hiding this comment.
could you set --nodeDriverRegistrar.livenessProbe.enabled=true here? so e2e test would run with livenessProbe enabled:
Line 45 in 94d48f6
|
/ok-to-test |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ajhetherington, andyzhangx The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Add optional liveness probe support for node-driver-registrar container in the node DaemonSet. When enabled, node-driver-registrar exposes an HTTP health endpoint that Kubernetes can use to detect and restart unhealthy registrar processes. New Helm values: - nodeDriverRegistrar.healthPort (default: 19809) - nodeDriverRegistrar.livenessProbe.enabled (default: false) - nodeDriverRegistrar.livenessProbe.initialDelaySeconds (default: 20) - nodeDriverRegistrar.livenessProbe.timeoutSeconds (default: 10) - nodeDriverRegistrar.livenessProbe.periodSeconds (default: 5) - nodeDriverRegistrar.livenessProbe.failureThreshold (default: 2) Ref: kubernetes-csi/csi-driver-nfs#1026
What type of PR is this?
/kind feature
Also technically an api change
What this PR does / why we need it:
This PR adds an optional healthcheck for the
node-driver-registrarcontainer, using it's healthcheck by enabling--http-endpoint(https://github.com/kubernetes-csi/node-driver-registrar?tab=readme-ov-file#health-check-with-the-http-server) & calling it with a livenessProbe.Which issue(s) this PR fixes:
Fixes #1025
See #1025 (comment) for example of how it has resolved the issue.
Special notes for your reviewer:
This just changes the latest helm chart to use a feature added in
node-driver-registrar, by default it will be disabled so won't have any changes for those using latest. Will need a new release (likely 4.13.0 as it changes the api)Does this PR introduce a user-facing change?: