-
Notifications
You must be signed in to change notification settings - Fork 207
feat: support Volume Group Snapshot #3028
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
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: umagnus The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @umagnus. 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. |
52b2ef9
to
aa48853
Compare
/ok-to-test |
pls also fix the sanity test failure:
|
e313841
to
ec34393
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.
set enableVolumeGroupSnapshot: true
in helm chart values
- "--leader-election-namespace={{ .Release.Namespace }}" | ||
- "--worker-threads=250" | ||
- "--retry-interval-max=30m" | ||
- "--feature-gates=CSIVolumeGroupSnapshot=true" |
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.
enableVolumeGroupSnapshot
- "--extra-create-metadata=true" | ||
- "--retry-interval-max=30m" | ||
- "--worker-threads=250" | ||
- "--feature-gates=CSIVolumeGroupSnapshot=true" |
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.
enableVolumeGroupSnapshot
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.
- "--feature-gates=CSIVolumeGroupSnapshot={{ .Values.snapshot.enableVolumeGroupSnapshot }}"
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.
done
charts/latest/azuredisk-csi-driver/templates/crd-csi-volumegroupsnapshot.yaml
Show resolved
Hide resolved
/retest |
7a2658a
to
d549219
Compare
snapshotNames := []string{} | ||
for _, sourceVolumeID := range sourceVolumeIDs { | ||
groupSnapshotUUID := strings.TrimPrefix(volumeGroupSnapshotName, "groupsnapshot-") | ||
snapshotName := fmt.Sprintf("snapshot-%x", sha256.Sum256([]byte(groupSnapshotUUID+sourceVolumeID))) |
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.
Here I use groupsnapshotuuid+sourceVolumeID to hash, since in snapshot-controller it use groupsnapshotcontentuuid+sourceVolumeID. But in CSI we can't get groupsnapshotcontent uuid
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.
@xing-yang we are generating snapshotName inside the CreateVolumeGroupSnapshot
, do you think this is the right way now? should this snapshotName be provided by CreateVolumeGroupSnapshot
request?
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.
I think we should be able to use groupSnapshotUUID in snapshot-controller as well.
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.
kubernetes-csi/external-snapshotter#1294 have a pr for this issue
d549219
to
5323ee8
Compare
/retest |
/hold |
9ea4642
to
6cd10dc
Compare
/retest |
6cd10dc
to
36a1a09
Compare
PR needs rebase. 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. |
@umagnus: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
What type of PR is this?
/kind feature
What this PR does / why we need it:
implement volume group snapshots
KEP-3476: Volume Group Snapshot
Which issue(s) this PR fixes:
Fixes #
Requirements:
Special notes for your reviewer:
Release note: