-
Notifications
You must be signed in to change notification settings - Fork 183
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
CSI driver support on Windows #45
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
you could refer to https://github.com/kubernetes/enhancements/blob/master/keps/sig-windows/20190714-windows-csi-support.md |
@andyzhangx: GitHub didn't allow me to assign the following users: kkmsft. Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @ritazh for Windows CSI support |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @kkmsft |
/assign @kkmsft |
reopen since PR #247 is only part of this work |
…kubernetes-sigs#45) * Fix for test run * Adding fake crd provisioner * Link fix * Fixes for unit test cases * Adding test case work with v1 and v2 * Setting up the complete flow from fake crdprovisioner to cloudprovisioner * Lint fixes
OCPBUGS-15658: Update to v1.28.1
Is your feature request related to a problem? Please describe.
Currently CSI driver is linux based, cannot run on Windows. The main difficulty is design difference between Linux and Windows, all devices are files while it's not true for Windows.
Here is a issue link in moby talking about this issue: moby/moby#38479
Describe the solution you'd like in detail
We could make the attacher and azure disk csi driver running as a standalone process on Windows, that could work. (could refer to kube-proxy and kubelet implementation in aks-engine: https://github.com/Azure/aks-engine/blob/master/parts/k8s/kuberneteswindowssetup.ps1#L129-L130)
For the provision part, it could still run on Linux(on master node?). That would make it a little easier to implement.
Describe alternatives you've considered
Additional context
https://github.com/kubernetes/enhancements/blob/master/keps/sig-windows/20190714-windows-csi-support.md
node-driver-registrar support on Windows
The text was updated successfully, but these errors were encountered: