Skip to content

Issues: kubernetes-csi/node-driver-registrar

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

4 Open 68 Closed
4 Open 68 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Review new kubelet plugin monitoring
#484 opened Feb 17, 2025 by jsafrane
1
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
14
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
20
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
23
ProTip! Updated in the last three days: updated:>2025-02-26.