-
Notifications
You must be signed in to change notification settings - Fork 10
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
Windows support for aws-fsx-openzfs-csi-driver #65
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
Hi, unfortunately the aws-fsx-openzfs-csi-driver is not supported for windows based containers and there are no current workarounds for this. Keeping this issue open to track demand for windows support. |
Is your feature request related to a problem? Please describe.
The driver image details shows Linux as only supported OS. Hence the daemonset pod for fxs node wont run in windows based instances. We want to confirm if aws-fsx-openzfs-csi-driver is supported for windows based containers and if there are any workarounds for this
Describe the solution you'd like in detail
Windows support for this driver. Based on Amazon FSx for OpenZFS user-guide Amazon FSx for OpenZFS file systems are broadly accessible from Linux, Windows, and macOS compute instances and containers using the industry-standard NFS protocol (v3, v4.0, v4.1, v4.2). Hence we need this support in driver as well
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: