pwx-37435 | fix: update the snapshotschedule post adding default reclaim policy #1784
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.
What type of PR is this?
What this PR does / why we need it
In the
startVolumeSnapshot
function, we were fetching the latest copy of thesnapshotschedule
from the CR however in thehandle()
function which actually calls thestartVolumeSnapshot()
function, we were not persisting the updated defaultreclaimPolicy
toDelete
in the CR. Due to this, theownerReference
wasn't getting added to thevolumeSnapshot
resource. This PR adds the change to persist the changed defaultreclaimPolicy
to the CR as soon as it's updated in the object.Does this PR change a user-facing CRD or CLI?:
No
Is a release note needed?:
No
Does this change need to be cherry-picked to a release branch?:
Yes,
release-24.2.0
branch.Test run
snapshot-k8s-new
pipeline: https://jenkins.pwx.dev.purestorage.com/job/Users/job/strivedi/job/snapshot-k8s-new/13/consolesnapshot-csi
pipeline: https://jenkins.pwx.dev.purestorage.com/job/Users/job/strivedi/job/snapshot-csi/1/console