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

Extend allowed PVC DataSources #989

Closed
j-griffith opened this issue Apr 23, 2019 · 33 comments
Closed

Extend allowed PVC DataSources #989

j-griffith opened this issue Apr 23, 2019 · 33 comments
Assignees
@j-griffith
Labels
sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Milestone
v1.18

Comments

@j-griffith
Copy link
Contributor

j-griffith commented Apr 23, 2019 •
edited by saad-ali
Loading

Enhancement Description
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 23, 2019
@msau42
Copy link
Member

msau42 commented Apr 23, 2019

/sig-storage
/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Apr 23, 2019
@msau42
Copy link
Member

msau42 commented Apr 23, 2019

/assign @j-griffith

@j-griffith j-griffith mentioned this issue Apr 23, 2019
Merged
@craiglpeters craiglpeters added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Apr 23, 2019
@craiglpeters
Copy link
Contributor

/sig storage

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 23, 2019
@saad-ali
Copy link
Member

/milestone v1.15

@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone Apr 24, 2019
@craiglpeters
Copy link
Contributor

@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
Copy link
Contributor Author

@craiglpeters Thanks for the reminder, I've submitted a PR updating the status to implementable here:
#1019

@christianh814
Copy link

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
Copy link
Contributor Author

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

@tamalsaha tamalsaha mentioned this issue May 13, 2019
Closed
@j-griffith j-griffith mentioned this issue May 28, 2019
Merged
@craiglpeters
Copy link
Contributor

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.

@j-griffith
Copy link
Contributor Author

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
Copy link

kacole2 commented Jul 8, 2019 •
edited
Loading

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
Copy link
Contributor Author

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
Copy link

kacole2 commented Jul 9, 2019

/milestone v1.16
/stage beta

@k8s-ci-robot k8s-ci-robot removed the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jul 9, 2019
@k8s-ci-robot k8s-ci-robot modified the milestones: v1.15, v1.16 Jul 9, 2019
@k8s-ci-robot k8s-ci-robot added the stage/beta Denotes an issue tracking an enhancement targeted for Beta status label Jul 9, 2019
@j-griffith j-griffith mentioned this issue Jul 17, 2019
Merged
@sethmccombs
Copy link

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
Copy link

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

@j-griffith
Copy link
Contributor Author

@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
Copy link
Member

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

@johnbelamaric
Copy link
Member

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 johnbelamaric added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jan 22, 2020
@johnbelamaric
Copy link
Member

/milestone v1.18

@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Jan 22, 2020
j-griffith added a commit to j-griffith/enhancements that referenced this issue Jan 27, 2020
@j-griffith
Update PVC DataSource to GA
79a16d7 
Update KEP to note graduation from Beta to GA for sig-storage cloning
feature in 1.18. Also add testing section to KEP.

issue: kubernetes#989
@j-griffith j-griffith mentioned this issue Jan 27, 2020
Merged
j-griffith added a commit to j-griffith/enhancements that referenced this issue Jan 28, 2020
@j-griffith
Update PVC DataSource to GA
0bef14a 
Update KEP to note graduation from Beta to GA for sig-storage cloning
feature in 1.18. Also add testing section to KEP.

issue: kubernetes#989
j-griffith added a commit to j-griffith/enhancements that referenced this issue Jan 28, 2020
@j-griffith
Update PVC DataSource to GA
ef01145 
Update KEP to note graduation from Beta to GA for sig-storage cloning
feature in 1.18. Also add testing section to KEP.

issue: kubernetes#989
j-griffith added a commit to j-griffith/enhancements that referenced this issue Jan 28, 2020
@j-griffith
Update PVC DataSource to GA
306ce54 
Update KEP to note graduation from Beta to GA for sig-storage cloning
feature in 1.18. Also add testing section to KEP.

issue: kubernetes#989
@savitharaghunathan
Copy link
Member

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
Copy link
Member

@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
Copy link
Member

@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
Copy link
Contributor Author

@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
Copy link
Member

@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
Copy link
Member

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

@j-griffith
Copy link
Contributor Author

@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: kubernetes/website#19318 Thanks again!

@j-griffith j-griffith mentioned this issue Mar 4, 2020
Closed
This was referenced Mar 5, 2020
Merged
Merged
SaranBalaji90 pushed a commit to SaranBalaji90/enhancements that referenced this issue Apr 5, 2020
@j-griffith @SaranBalaji90
Update PVC DataSource to GA
8fc7e1b 
Update KEP to note graduation from Beta to GA for sig-storage cloning
feature in 1.18. Also add testing section to KEP.

issue: kubernetes#989
@palnabarun palnabarun added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Apr 27, 2020
@palnabarun
Copy link
Member

/close

(closing this since the KEP has been implemented)

@k8s-ci-robot
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@j-griffith j-griffith

Labels
sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Milestone
v1.18
Development

No branches or pull requests