-
Notifications
You must be signed in to change notification settings - Fork 811
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
Supporting String Interpolation for Modifying Tags On Existing Volumes Through VAC #2093
Supporting String Interpolation for Modifying Tags On Existing Volumes Through VAC #2093
Conversation
Hi @mdzraf. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
Code Coverage Diff
|
/hold |
/retest |
1 similar comment
/retest |
examples/kubernetes/modify-volume/manifests/volumeattributesclass.yaml
Outdated
Show resolved
Hide resolved
/lgtm |
/retest |
Needs squash but |
/label tide/merge-method-squash |
/unhold |
/label tide/merge-method-squash |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: torredil The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm thank you
Is this a bug fix or adding new feature?
New feature
What is this PR about? / Why do we need it?
This will add the support for runtime string interpolation on tag values for a volume upon modification, which allows for customers to specify placeholder values for the PVC namespace, PVC name and PV name, which will then be dynamically computed at runtime.
What testing is done?
Unit tests were ran to ensure that input was parsed properly and manual testing was done after initial changes to
external-resizer
sidecar code were made to pass in the extra metadata necessary to the driver and ensuring that these tags were properly added at runtime.