We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We recently had problems with vsphere-csi-driver pods going in CrashloopBackoff state because the default probe-timeout is too short.
We created a PR: kubernetes-sigs/vsphere-csi-driver#2997.
Taking a step back, we found that this timeout is increased to 3s or more in a lot of places: See here and here.
Maybe the default should be increased to 3 or 4s?
The text was updated successfully, but these errors were encountered:
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
lifecycle/rotten
You can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Sorry, something went wrong.
Not stale. Is anybody reviewing here ?
No branches or pull requests
We recently had problems with vsphere-csi-driver pods going in CrashloopBackoff state because the default probe-timeout is too short.
We created a PR: kubernetes-sigs/vsphere-csi-driver#2997.
Taking a step back, we found that this timeout is increased to 3s or more in a lot of places: See here and here.
Maybe the default should be increased to 3 or 4s?
The text was updated successfully, but these errors were encountered: