feat: Add Original PVC context to the deployment labels. #151
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request template
Why is this PR required? What issue does it fix?:
This allows targeting the nfs workload pod using stable labels in e.g.
CiliumNetworkPolicy
rules. Currently the only label on the workload isopenebs.io/nfs-server
with the generated pvc name which cannot be deduced statically from the original pvc name.What this PR does?:
Adds the name/namespace/id labels to the pod.
Does this PR require any upgrade changes?:
No.
If the changes in this PR are manually verified, list down the scenarios covered::
Using the pod in the
CiliumNetworkPolicy
, by targeting the new labels.Any additional information for your reviewer? :
N/A
Checklist:
<type>(<scope>): <subject>