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/tree/master/keps/sig-storage/1495-volume-populators
• 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.23)
  • Stable release target (1.33)

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

Tracking PRs:

• Promote Beta AnyVolumeDataSource to GA kubernetes#129770
• Mark AnyVolumeDataSource as stable website#49535
• Add Blog Post for Volume Populator GA website#49542

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