Skip to content

OSDOCS-15215#Volume populators TP > GA #96030

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lpettyjo
Copy link
Contributor

@lpettyjo lpettyjo commented Jul 11, 2025

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 11, 2025
@lpettyjo lpettyjo added this to the Continuous Release milestone Jul 11, 2025
Copy link

openshift-ci bot commented Jul 11, 2025

@lpettyjo: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

@RomanBednar
Copy link

@lpettyjo This doc describes how to configure CR and CRD which is required for working with populators in k8s/OpenShift, however that's just a fraction of the hole feature and we're missing some crucial parts:

  1. Populator authors have to write the code to populate the volumes and deploy it. In other words, if we create just Hello CR and CRD - nothing will happen without the populator being deployed. Unfortunately, we don't have much from upstream apart from code examples: https://github.com/kubernetes-csi/lib-volume-populator/blob/master/example/hello-populator/main.go

  2. Populator authors have to create VolumePopulator CR to register their populator CR (e.g. Hello ) otherwise the validator would emit events with errors, this is quite well described in upstream enhancement: https://github.com/kubernetes/enhancements/blob/63d4f6f2aa0e2eb0b83067b067c4949643b1b24c/keps/sig-storage/1495-volume-populators/README.md?plain=1#L160-L202

Actually, you could follow most of the upstream docs since the only difference in OpenShift is that we install the validator and VolumePopulator CRD, while in k8s users have to do that themselves. However we should not reference upstream resources directly (like code examples, or deployments using upstream images), so I'm not sure how to document populator development process nicely...

@lpettyjo lpettyjo added peer-review-needed Signifies that the peer review team needs to review this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jul 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.20 size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants