Skip to content

Issues: kubernetes-sigs/gcp-filestore-csi-driver

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.

Sign up for GitHub

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

16 Open 38 Closed
16 Open 38 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

go.mod is missing replace for k8s.io/endpointslice and dynamic-resource-allocation
#896 opened Jun 28, 2024 by dfajmon
Add support for Filestore Zonal/Regional instances with 1-10Tb volume into Filestore CSI driver
#874 opened Jun 4, 2024 by SehiiRohoza
#867 #867 #850 #853 #860
#869 opened Jun 3, 2024 by Heyitsquoracom
#867
#868 opened Jun 3, 2024 by Heyitsquoracom
1
deploy/kubernetes/driver_* should be removed lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#126 opened Jun 15, 2021 by mattcary
2
auto-detect network from cluster params rather than using fixed default lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#63 opened Oct 7, 2020 by mattcary
2
FIlestore CSI driver doesn't work on Shared VPC lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#43 opened Jun 4, 2020 by mahmoudcb
@saikat-royc
9
Take advantage of csi_secret in CSI 1.0 lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#29 opened Nov 18, 2018 by saad-ali
2
project_setup.sh unbound variable lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#26 opened Sep 18, 2018 by 0snug0
2
Add Kubernetes e2e lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#25 opened Aug 28, 2018 by msau42
2
Validate volume attributes in ValidateVolumeCapabilities lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#24 opened Aug 27, 2018 by msau42
2
Add e2es for all the CreateVolume parameters lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#22 opened Aug 18, 2018 by msau42
2
Integrate livenessprobe lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
#19 opened Aug 15, 2018 by saad-ali
3
Add corrupted mount check for Unpublish lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#14 opened Aug 2, 2018 by msau42
2
Serialize operations on the same volume lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#4 opened Jul 12, 2018 by msau42
2
Move capacity calculations to a shared repo lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#3 opened Jul 11, 2018 by msau42
2
ProTip! Follow long discussions with comments:>50.