Portworx file in-tree to CSI driver migration

[trierra]

Enhancement Description

• One-line enhancement description (can be used as a release note):
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2589-csi-migration-portworx
• Primary contact (assignee): @trierra
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.23
  • Beta release target (x.y): 1.25 (off-by-default)
  • Beta release target (x.y): 1.31 (on-by-default)
  • Stable release target (x.y): 1.32

Parent enhancement: #625

• Alpha
  • KEP (k/enhancements) update PR(s): KEP-2589: Portworx CSI Migration #2964
  • Code (k/k) update PR(s): Csi translation portworx kubernetes#103447
  • Docs (k/website) update PR(s): CSI migration portworx in alpha state website#30445
• Beta(off-by-default)
  • KEP (k/enhancements) update PR(s): Promote Portworx CSI migration to Beta in v1.25 #3345
  • Code (k/k) update PR(s): promote the Portworx feature gate to Beta kubernetes#110411
  • Docs (k/website) update(s): Px 125 beta website#34886
• Beta(on-by-default)
  • KEP (k/enhancements) update PR(s): Promote Portworx CSI migration to Beta in 1.31 #4467
  • Code (k/k) update PR(s): Enables the Portworx in-tree driver to Portworx migration feature by default kubernetes#125016
  • Docs (k/website) update(s): update portworxVolume doc website#46506
• Stable
  • KEP (k/enhancements) update PR(s): KEP-2589: Promote Portworx CSI migration to GA in 1.33 #5011
  • Code (k/k) update PR(s): Promote Portworx CSI migration to GA kubernetes#129297
  • Docs (k/website) update(s): Update doc for Portworx CSI migration moving to stable website#49188

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[trierra]

/sig storage

[fejta-bot]

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

[trierra]

/remove-lifecycle stale

[SergeyKanzhelev]

was this enhancement approved for 1.22?

[trierra]

it was planned to get to 1.22

…

On Wed, Jul 7, 2021 at 10:18 PM Sergey Kanzhelev ***@***.***> wrote: was this enhancement approved for 1.22? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2589 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAX3S75OZLTLP4UMEZNMWXDTWUYMFANCNFSM42DXZYOA> .

-- --------- Best regards, *Oksana Naumov* // *MTS @ CNBU*

[SergeyKanzhelev]

I cannot find the KEP here: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage and this issue is not in the milestone. I'm confused.

[trierra]

Sorry for confusion, I was told KEP is not needed, I only have an open issue for that #2589

…

On Thu, Jul 8, 2021 at 10:36 AM Sergey Kanzhelev ***@***.***> wrote: I cannot find the KEP here: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage and this issue is not in the milestone <https://github.com/kubernetes/enhancements/issues?q=is%3Aissue+is%3Aopen+label%3Asig%2Fstorage+milestone%3Av1.22>. I'm confused. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2589 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAX3S73XEZXZGNCIJVCU3MLTWXO3JANCNFSM42DXZYOA> .

-- --------- Best regards, *Oksana Naumov* // *MTS @ CNBU*

[trierra]

oh, I see what you mean. Apparently, it's not approved.

[SergeyKanzhelev]

I was told KEP is not needed,

It may not be. Change seems to be quite straightforward and likely already covered with some other KEP. Either way the code freeze for 1.22 is in 40 minutes. There is still some work left on the PR