fix: driver pod crash issue on Windows #359
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it:
Sets the
initialDelaySeconds
andtimeoutSeconds
for the node-driver-registrar livenessprobe check.timeoutSeconds
of 1s is honored starting from Kubernetes 1.20 and is aggressive. Setting the value to 15s which is appropriate for linux and windows.initialDelaySeconds
to 30s to provide time for the socket to be created and driver to be registered during startup of the driver pods.Ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes for defaults
similar to fix: kubernetes-sigs/secrets-store-csi-driver#729
Which issue(s) this PR fixes:
Fixes #
Requirements:
Special notes for your reviewer:
Release note: