-
Notifications
You must be signed in to change notification settings - Fork 135
Issues: kubernetes-csi/node-driver-registrar
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Node Driver Registrar restart at GetDriverName call
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#405
opened May 10, 2024 by
Anto74
csi-node-driver-registrar consumed ~44% cpu time to read container registry TimeZone information in Windows
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#229
opened Oct 14, 2022 by
Howard-Haiyang-Hao
Node driver registrar says "Lost connection" and do nothing
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#139
opened Mar 26, 2021 by
jim3ma
Scheme "" not registered, fallback to default scheme
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#88
opened Jun 13, 2020 by
yerzhant
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.