Add Blog Post for Volume Populator GA #49542
Conversation
k8s-ci-robot
added
do-not-merge/hold
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
content/en/blog/_posts/2025-04-17-volume-populators-ga/index.md
Outdated
Show resolved
Hide resolved
k8s-ci-robot
removed
the
do-not-merge/hold
|
/unhold |
sunnylovestiramisu
force-pushed
the
blog-vp
branch
from
d8b0967 to
a4dd3fe
Compare
k8s-ci-robot
added
the
sig/docs
sunnylovestiramisu
force-pushed
the
blog-vp
branch
from
a4dd3fe to
c3896ae
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
sunnylovestiramisu
force-pushed
the
blog-vp
branch
from
c3896ae to
8448089
Compare
| * Populate data from multiple sources of the same provider: populate multiple different sources to one destination | ||
| * Populate data from multiple sources of the different providers: populate multiple different sources to one destination, pipelining different resources’ population | ||
|
|
||
| To ensure we're building something truly valuable, we'd love to hear about any specific use cases you have in mind for this feature. For any inquiries or specific questions related to volume populator, please reach out to the [SIG Storage community Slack channel](https://app.slack.com/client/T09NY5SBT/C09QZFCE5). |
There was a problem hiding this comment.
Not everyone reading the blog has already joined the slack. Can you add the SIG Storage community page https://github.com/kubernetes/community/tree/master/sig-storage?
content/en/blog/_posts/2025-04-17-volume-populators-ga/index.md
Outdated
Show resolved
Hide resolved
| To accommodate this, we've introduced three new plugin-based functions: | ||
| * PopulateFn(): Executes the provider-specific data population logic. | ||
| * PopulateCompleteFn(): Checks if the data population operation has finished successfully. | ||
| * PopulateCleanupFn(): Cleans up temporary resources created by the provider-specific functions after data population is completed |
There was a problem hiding this comment.
Are there any documentations on how to implement these plugin functions? Maybe in the CSI docs https://github.com/kubernetes-csi/docs? Are these functions required for other applications to integrate with VolumePopulators?
There was a problem hiding this comment.
We added an example here in this PR: kubernetes-csi/lib-volume-populator#208
|
|
||
| ### Mutator functions to modify the Kubernetes resources | ||
|
|
||
| For GA a MutatorConfig to the Volume Populator Controller is added, allowing the specification of mutator functions to modify Kubernetes resources. This enables customization of the default Kubernetes objects in the volume populator. |
There was a problem hiding this comment.
Can you elaborate why mutation is needed? What's the use case?
There was a problem hiding this comment.
If the PVC prime is not the exact copy of the PVC, you can add provider specific info to the driver, you can add to MutatorConfig. It is not required to have.
|
|
||
| Our beta phase highlighted a new requirement: the need to aggregate metrics not just from lib-volume-populator, but also from other components within the provider's codebase. | ||
|
|
||
| To address this, we've introduced a provider metric manager. This enhancement delegates the implementation of metrics logic to the provider itself, rather than relying solely on lib-volume-populator. This shift provides greater flexibility and control over metrics collection and aggregation, enabling a more comprehensive view of provider performance. |
There was a problem hiding this comment.
For an application to integrate with Volume Populators, what does it need to do to support this?
There was a problem hiding this comment.
There is no extra work you need to do for the default metrics, it is built in with lib-volume-populator. If you want to add specific metrics, for example we need prometheus specifically for GKE metrics, so we add it customized.
|
|
||
| ### Clean up temp resources | ||
|
|
||
| During the beta phase, the volume populator couldn't handle PersistentVolumeClaim (PVC) deletions that occurred while volume population was in progress due to limitations in finalizer handling. To ensure a smooth transition to GA, we've enhanced the populator to support the deletion of temporary resources if the original PVC is deleted. This prevents resource leaks and ensures a more robust and reliable system. |
There was a problem hiding this comment.
What are the temporary resources?
There was a problem hiding this comment.
Anything created by the lib-volume-populator like pvc prime is temp resources.
Co-authored-by: Dipesh Rawat <[email protected]>
sunnylovestiramisu
force-pushed
the
blog-vp
branch
from
8448089 to
832d6e3
Compare
Description
Blog post for volume populator GA, waiting for kubernetes/kubernetes#129770
Issue
#49541
Closes: #
/hold