-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
Product / Portfolio Work
-
None
-
0% To Do, 0% In Progress, 100% Done
-
False
-
-
False
-
XS
-
None
-
-
-
-
-
None
-
-
None
Feature Overview (aka. Goal Summary)
Introduce a new field on PVCs called DataSourceRef that allows users to specify a custom populator that can manipulate or inject data before it is handed over to the user
https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1495-volume-populators
Goals (aka. expected user outcomes)
Productise volume populators as GA. This feature comes from upstream k8s.
Requirements (aka. Acceptance Criteria):
Feature passes CI with a basic populator.
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | both |
| Classic (standalone cluster) | y |
| Hosted control planes | y |
| Multi node, Compact (three node), or Single node (SNO), or all | all |
| Connected / Restricted Network | all |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | all |
| Operator compatibility | N/A |
| Backport needed (list applicable versions) | n |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | n |
| Other (please specify) | x |
Questions to Answer (Optional):
Do we ship any populator by default?
What populator do we use for testing?
Out of Scope
Ship / Support custom populator
Background
This is used by OCP virt to prepare VM images.
Customer Considerations
Make it clear that we support the core feature but not the custom populator they would build.
Documentation Considerations
Document what the feature is and how to build/use an "hello world" populator.
Interoperability Considerations
Not environment specific
- links to
(6 links to)
