Closed leonardoce closed 5 months ago
Hi @leonardoce. Thanks for your PR.
I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/unassign /assign xing-yang
In the release note, can you specify that this change is in the CSI snapshotter sidecar.
In the release note, can you specify that this change is in the CSI snapshotter sidecar.
Done, and removed that stray line too. Thank you @xing-yang
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leonardoce, xing-yang
The full list of commands accepted by this bot can be found here.
The pull request process is described here
This patch replace the usage of
UpdateStatus
with a patch against thestatus
subresource in theupdateSnapshotContentStatus
.The reason behind this change is to avoid conflicts that could potentially arise, as they pose a risk within the context of the calling function
createGroupSnapshotWrapper
.If
createGroupSnapshotWrapper
is called multiple times for the same GroupSnapshot, this will lead to multiple staleVolumeSnapshot
andVolumeSnapshotContent
being created.Related: #1050
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: