Skip to content
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

Jump to bottom

Windows CSI migration #94778

Open
msau42 opened this issue Sep 14, 2020 · 9 comments
Open

Windows CSI migration #94778

msau42 opened this issue Sep 14, 2020 · 9 comments
Assignees
@andyzhangx @jingxu97 @ddebroy
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/storage Categorizes an issue or PR as relevant to SIG Storage.

Comments

@msau42
Copy link
Member

msau42 commented Sep 14, 2020

What would you like to be added:
We have not tested csi migration with Windows, so we need to investigate if anything needs to be done.

Why is this needed:
This is a blocker for moving CSI migration to GA.

@kubernetes/sig-storage-feature-requests
@msau42 msau42 added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 14, 2020
@k8s-ci-robot k8s-ci-robot added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Sep 14, 2020
@msau42
Copy link
Member Author

msau42 commented Sep 14, 2020

/assign @jingxu97 @ddebroy @andyzhangx

@msau42 msau42 mentioned this issue Sep 14, 2020
Closed
1 task
@andyzhangx
Copy link
Member

thanks, I think at least we should enable the e2e test(with same config as Linux) for Windows CSI migration first.

@andyzhangx
Copy link
Member

already added azure disk CSI migration e2e test on Windows: https://testgrid.k8s.io/provider-azure-azuredisk-csi-driver#pr-azuredisk-csi-driver-e2e-migration-windows, it works well now.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 16, 2020
@jayunit100
Copy link
Member

Hi, curious...

By migration do we mean from in tree providers? I think there are a few... azure disk, flex (smb).... what migration paths do we need to test here ?

Sorry if I might be missing context ...

@ddebroy
Copy link
Member

ddebroy commented Jan 8, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 8, 2021
@ddebroy
Copy link
Member

ddebroy commented Jan 8, 2021

hey @jayunit100, this is referring to testing the shim infrastructure that allows operations against in-tree storage plugins to be directed towards their corresponding CSI plugins (https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/). Specifically, we need to make sure the node operation translations all works out as expected for Windows nodes with CSI plugins that do support Windows.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 8, 2021
@Jiawei0227
Copy link
Contributor

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andyzhangx andyzhangx

@jingxu97 jingxu97

@ddebroy ddebroy

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@jayunit100 @andyzhangx @Jiawei0227 @jingxu97 @k8s-ci-robot @ddebroy @msau42 @fejta-bot