Enhancements: Extend allowed PVC DataSources

[j-griffith]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Enable specifying an existing PVC as a DataSource parameter for creating a new PVC (Cloning)

• Kubernetes Enhancement Proposal:
  https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/20181111-extend-datasource-field.md

• Primary contact (assignee):
  j-griffith

• Responsible SIGs:
  sig-storage

• Enhancement target (which target equals to which milestone):

  • Alpha: v1.15
  • Beta: v1.16
  • GA: v1.18 (target)

[msau42]

/sig-storage
/stage alpha

[msau42]

/assign @j-griffith

[craiglpeters]

/sig storage

[saad-ali]

/milestone v1.15

[craiglpeters]

@j-griffith, Kubernetes 1.15 Enhancement Freeze is 4/30/2019. To be included in the Kubernetes 1.15 milestone, KEPs are required to be in an "Implementable" state with proper test plans and graduation criteria. Please submit any PRs needed to make this KEP adhere to inclusion criteria. If this will slip from the 1.15 milestone, please let us know so we can make appropriate tracking changes.

[j-griffith]

@craiglpeters Thanks for the reminder, I've submitted a PR updating the status to implementable here:
https://github.com/kubernetes/enhancements/pull/1019

[christianh814]

Hey @j-griffith I'm the v1.15 docs shadow.

Does this enhancement require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Friday, May 31st. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions!

[j-griffith]

@christianh814 Thanks, I wasn't familiar with that, will get it submitted, thanks for pointing me to it.

[craiglpeters]

Hi @j-griffith, today is code freeze for the 1.15 release cycle. The k/k PR https://github.com/kubernetes/kubernetes/pull/76913 has not yet been merged. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. Is there high confidence this will be merged by EOD PST today? After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

[j-griffith]

Hi @j-griffith, today is code freeze for the 1.15 release cycle. The k/k PR kubernetes/kubernetes#76913 has not yet been merged. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. Is there high confidence this will be merged by EOD PST today? After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

@saad-ali @msau42 @thockin ^^ I was really hopeful that this wouldn't sit idle for another release, any chance it's going to get reviewed?

[kacole2]

Hi @j-griffith , I'm the 1.16 Enhancement Lead. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.6 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[j-griffith]

Hi @kacole2 Yes, we'd like to move this to beta fort the 1.16 release. I'll start submitting the 1.16 milestone and beta PRs.

[kacole2]

/milestone v1.16
/stage beta

[sethmccombs]

Hey @j-griffith

I'm one of the v1.16 docs shadows.
Does this enhancement (or the work planned for v1.16) require any new docs (or modifications to existing docs)? If not, can you please update the 1.16 Enhancement Tracker Sheet (or let me know and I’ll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.16) due by Friday, August 23rd, it can just be a placeholder PR at this time. Let me know if you have any questions!

[simplytunde]

@j-griffith The placeholder Docs is due this Friday Aug 23rd.

[kacole2]

@j-griffith code freeze for 1.16 is on Thursday 8/29. Are there any outstanding k/k PRs that still need to be merged for this to go Beta? I see https://github.com/kubernetes/kubernetes/pull/76913 has been merged.

[j-griffith]

Yes, the outstanding PR was here: https://github.com/kubernetes/kubernetes/pull/81792#issuecomment-523969830@kacole2

As of Friday evening it looks like this may not be promoted to beta for 1.16. I haven't heard any updates on what's been decided.

[mrbobbytables]

Hey there @j-griffith -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to alpha/beta/stable in 1.17?

The current release schedule is:

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 19 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

If you do, please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

/milestone clear

[j-griffith]

@mrbobbytables We made beta status in 1.16 after all. :)

[mrbobbytables]

@j-griffith Nice :) Are you looking to graduate to GA in 1.17?

[j-griffith]

@j-griffith Nice :) Are you looking to graduate to GA in 1.17?

I don't think so, 1.18 would be the earliest in my opinion.

[mrbobbytables]

Noted. I'll update the tracking info. Thanks for being so quick to respond! 👍

[johnbelamaric]

Hey there @j-griffith -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to stable in 1.18?

The current release schedule is:
Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release, this enhancement must have a merged KEP in the implementable status. The KEP must also have graduation criteria and a Test Plan defined.

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements
Thanks!

[johnbelamaric]

/milestone v1.18

[savitharaghunathan]

Hi, @j-griffith :) 1.18 docs shadow here.

Does this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time. Let me know if you have any questions!

Thanks,
Savitha

[jsafrane]

@j-griffith, @msau42, is anyone actually working on the tests mentioned in the last KEP update, https://github.com/kubernetes/enhancements/pull/1515/files ? What tasks are remaining?

I did not find a board on our usual CSI place, https://github.com/orgs/kubernetes-csi/projects

[johnbelamaric]

@j-griffith code freeze is March 5th. Please link any PRs that are needed to complete this for 1.18, so we can track them in the release team. Thanks!

[j-griffith]

@j-griffith, @msau42, is anyone actually working on the tests mentioned in the last KEP update, kubernetes/enhancements/pull/1515/files ? What tasks are remaining?

I did not find a board on our usual CSI place, github.com/orgs/kubernetes-csi/projects

Yep, I'm assigned and working on it. I'll get it added to the CSI boards. The only work that's needed is enhancements to the tests which I've started.

[savitharaghunathan]

@j-griffith, @msau42 - I'm one of the v1.18 docs shadow, since we're approaching the deadline for docs placeholder PR, I'd like to confirm whether you will need docs for this enhancement.

Thanks!

[johnbelamaric]

@j-griffith any PRs for this yet that we can track?

[j-griffith]

@j-griffith, @msau42 - I'm one of the v1.18 docs shadow, since we're approaching the deadline for docs placeholder PR, I'd like to confirm whether you will need docs for this enhancement.

Thanks!

Docs PR is here: https://github.com/kubernetes/website/pull/19318 Thanks again!

[palnabarun]

/close

(closing this since the KEP has been implemented)

[k8s-ci-robot]

@palnabarun: Closing this issue.

In response to this:

/close

(closing this since the KEP has been implemented)

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.