-
Notifications
You must be signed in to change notification settings - Fork 376
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
Use ownership to identify volume group snapshot members #1225
Conversation
/assign xing-yang |
0595e03
to
75845d6
Compare
75845d6
to
2f2a965
Compare
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
/assign @xing-yang |
Instead of marking the member snapshot object with a label, this PR uses an ownership reference. Member objects are looked up using a new index in the informer cache.
2f2a965
to
c70f946
Compare
/lgtm |
[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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Instead of marking the member snapshot object with a label, this PR uses an ownership reference.
Member objects are looked up using a new index in the informer cache.
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR removes the usage of the
groupsnapshot.storage.k8s.io/volumeGroupSnapshotName
label, opting for an ownership-based volume group snapshot member tracking as described in the relative comment.The patch fixes an issue in the
csi-snapshotter
sidecar that was failing to pass the snapshot ids to the DeleteGroupSnapshot RPC endpoint for statically provisioned snapshots with theDelete
retention policy.Which issue(s) this PR fixes:
Fixes #1213
Special notes for your reviewer:
With this PR applied, my smoke tests are passing.
They cover volume group snapshots (static and dynamic provisioning, both retain and delete deletion policy) and volume snapshots (static and dynamic provisioning, both retain and delete deletion policy).
I manually tested creating a volume group snapshot with a name of 73 characters and everything went fine.
Does this PR introduce a user-facing change?: