Enhancements: Generic data populators

[bswartz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow generic data populators by permitting any object to be the data sources for a PVC
• Kubernetes Enhancement Proposal:https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/20200120-generic-data-populators.md
• Primary contact (assignee): @bswartz
• Responsible SIGs: sig-storage, sig-api-machinery
• Enhancement target (which target equals to which milestone):
  
  
  
  • Alpha release target (1.18)
  
  
  • Beta release target (1.20)
  
  
  • Stable release target (x.y)
  
  

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

[bswartz]

/sig storage

[jeremyrickard]

Hey @bswartz, I see you've targeted this going Alpha in 1.18. This is a friendly notice that to be included in 1.18, you'll need to have the KEP merged as implementable and it will need to have graduation criteria and a test plan. Your KEP PR looks like it's missing both of those and is marked as provisional. If you could please confirm that you plan on making this go alpha in 1.18, we can conditionally track it but you will need to have the KEP updated before Enhancement Freeze, on January 28th (end of day Pacific time).

[bswartz]

@jeremyrickard Thanks I do hope for this KEP to be targeted at 1.18, but that depends mostly on the reviewers agreeing with the approach in general. I will update the document itself to include graduation criteria and a test plan.

[bswartz]

@jeremyrickard I filled in the missing sections. Still working with approvers on getting approval. Let me know if there's anything else essential you think I should add.

[bswartz]

@jeremyrickard Got the KEP approved, and you please track this now?

[jeremyrickard]

/milestone v1.18

Hey @bswartz the KEP needs to be updated to implementable. Can you do a quick PR to update the status to implementable? We can file an exception tomorrow to make sure it gets in, but the KEP will need that status.

[VineethReddy02]

Hello, @bswartz, I'm 1.18 docs lead.
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!

[bswartz]

@VineethReddy02 Yes there will be at least a small docs update with this change.

[kikisdeliveryservice]

Hi @bswartz !

As a reminder that the Code Freeze is Thursday 5th March. Can you please link all the k/k PRs or any other PRs that should be tracked for this enhancement?

Thanks!
The 1.18 Enhancements Team

[VineethReddy02]

Hello @bswartz
We are close to the docs placeholder PR deadline against the dev-1.18 branch. Having a placeholder PR in place will definitely help us in tracking enhancements much better.

Thanks! :)

[jeremyrickard]

Hi @bswartz !

As a reminder that the Code Freeze is Thursday 5th March. Can you please link all the k/k PRs or any other PRs that should be tracked for this enhancement?

Thanks!
The 1.18 Enhancements Team

[bswartz]

https://github.com/kubernetes/website/pull/19315

[bswartz]

Will add k/k PR next

[bswartz]

https://github.com/kubernetes/kubernetes/pull/88636

[kikisdeliveryservice]

@bswartz As a reminder code freeze is March 5th. Is this still on track for 1.18? Thank you!

[bswartz]

@kikisdeliveryservice Yes, completely on track! I just need some reviews on my PR and for it to merge. I'm working on docs in parallel. Is there anything missing that you're aware of?

[kikisdeliveryservice]

@bswartz Just wanted to check in to make sure your work got in by the deadline :)

[kikisdeliveryservice]

As a reminder code freeze is tomorrow for 1.18 and all PRs should be merged by then.

-Enhancements Team

[palnabarun]

/milestone clear

(removing from 1.18 since it didn't go into that release)

[palnabarun]

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

---

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 @bswartz, pinging back as a reminder for the above. :slightly_smiling_face:

[bswartz]

We're trying to make progress towards beta, but at this point I'm forced to admit this will likely remain alpha in 1.19 and we will try to move to beta in 1.20.

[palnabarun]

@bswartz -- Thank you for the update. I have updated the tracking sheet. :+1:

[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

[bswartz]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @bswartz

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[bswartz]

I expect to get back to work on this and aim for beta in 1.20. I'll update the KEP with the design changes first and aim for implementation during this cycle.

[kikisdeliveryservice]

Thanks @bswartz !

As a note, the existing KEP is using the old format. If you could, during your update please ensure that the KEP format is up to date as per: https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template we'd appreciate it. Also if you could update the description to reflect the milestone changes, that would be great.

Let me know if you have any questions or if anything changes.

Best,
Kirsten

/milestone v1.20

[kendallroden]

Hey @bswartz ! Just checking in, as the Enhancements Freeze is coming up next Tuesday, October 6th. @kikisdeliveryservice has already moved the stage to beta and marked this as tracked, but wanted to remind you to update to the new KEP template before then, if possible.

Appreciate your help - feel free to reach out with any questions or updates on this KEP.

Thanks,

Kendall (1.20 Enhancements Team)

[kendallroden]

Hi @bswartz!

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Thanks so much,

Kendall

[eagleusb]

Hello @bswartz :wave:, 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo.

This PR can be just a placeholder at this time and must be created before Nov 6th

Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[eagleusb]

Hi @bswartz :wave:

The docs placeholder deadline is almost here.

Please make sure to create a placeholder PR against the dev-1.20 branch in the k/website before the deadline.

Also, please keep in mind the important upcoming dates:

• Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
• Thursday, Nov 12th: Week 9 - Code Freeze
• Monday, Nov 23rd: Week 11 - Docs PR Ready for Review

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

Thanks !

[annajung]

@kendallroden @kikisdeliveryservice @eagleusb please note that this enhancement is no longer being tracked for 1.20
ref slack

[bswartz]

Thanks for the reminders, this work is continuing but probably targeting a 1.21 beta at this point because the KEP is not properly updated and the code is not ready to merge.