Enhancements: Cinder in-tree to CSI driver migration

[davidz627]

Enhancement Description

• One-line enhancement description (can be used as a release note): Migrate the internals of in-tree Cinder Plugin to call out to the Cinder Driver while maintaining the original API
• Design proposal link (community repo): https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/csi-migration.md
• KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/20190129-csi-migration.md
• Primary contact (assignee): @adisky @dims
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  
  
  
  • Alpha release: 1.14
  
  
  • Beta release target: 1.18
  
  
  • Stable release target (x.y): 1.19
  
  

Parent enhancement: https://github.com/kubernetes/enhancements/issues/625
Public Migration testing CI: LINK

TODO

• [ ] Replace design/KEP with specific one if needed
• [ ] Link public migration testing CI

[davidz627]

/sig storage

[jeremyrickard]

@davidz627 @dims @adisky I assume this is also being targeted for 1.18? The KEP currently doesn't have a Test Plan defined, it only references what is in the original design proposal. The release team would like to see the KEP updated to actually contain the test plan before enhancement freeze. We'll conditionally track this for 1.18 with that in mind if you're planning on going to beta in 1.18.

Thanks!

[jeremyrickard]

/milestone v1.19

[dims]

This is already done, please see https://github.com/kubernetes/kubernetes/pull/85637#issuecomment-602734721

[msau42]

/reopen
We should keep this issue open to track to GA

[k8s-ci-robot]

@msau42: Reopened this issue.

In response to this:

/reopen
We should keep this issue open to track to GA

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.

[palnabarun]

Hi @msau42 @davidz627 -- 1.19 Enhancements Lead here, I wanted to check in if you think this enhancement would graduate in 1.19?

As Jeremy mentioned above, it would be great if a test plan can be added before moving it to GA.

---

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

[palnabarun]

Hi @msau42 @davidz627, pinging back as a reminder for the above. :slightly_smiling_face:

[msau42]

I think we should remain in beta for 1.19 and work towards stabilizing the feature as well as getting it bundled with the openstack cloud controller. @adisky do you plan to continue working on this?

[palnabarun]

Thank you @msau42 for the update. I will update the tracking sheet accordingly. :+1:

[palnabarun]

/milestone clear

[adisky]

I think we should remain in beta for 1.19 and work towards stabilizing the feature as well as getting it bundled with the openstack cloud controller. @adisky do you plan to continue working on this?

@msau42 I am no longer working on this, @chrigl @ramineni would be primary contacts.

[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-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[palnabarun]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @chrigl @ramineni @msau42

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[ramineni]

@kikisdeliveryservice Let me check on this on what needs to be done , will get back.

[msau42]

cc @jsafrane

[kikisdeliveryservice]

Following up: 1.20 Enhancements Freeze is October 6th. Could you let us know if you have plans for 1.20? To be included in the milestone:

The KEP must be merged in an implementable state
The KEP must have test plans (missing: need this for beta->GA)
The KEP must have graduation criteria

If you could please update to the new template and include the missing sections noted above that would be great. See for ref: https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template

I also note that the implementation history of the KEP also needs to be updated.

Thanks!
Kirsten

[ramineni]

@kikisdeliveryservice Sorry for the delay . Looks like it wont be possible for 1.20 , will target for next.
Thanks.

[kikisdeliveryservice]

Thanks for the update @ramineni !