Skip to content
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

update volumegroupsnapshot to beta1 #612

Merged

Conversation

Madhu-1
Copy link
Contributor

@Madhu-1 Madhu-1 commented Jan 7, 2025

updating the volumegroupsnapshot to beta1 API

@k8s-ci-robot k8s-ci-robot added the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Jan 7, 2025
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 7, 2025
@Madhu-1
Copy link
Contributor Author

Madhu-1 commented Jan 7, 2025

/assign @xing-yang

@Madhu-1
Copy link
Contributor Author

Madhu-1 commented Jan 7, 2025

/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jan 7, 2025
```

Create a _PVC_ from a _VolumeSnapshot_ that is part of the group snapshot:
```
# In the command below, the volume snapshot name should be chosen from
# the ones listed in the output of the previous command
sed 's/new-snapshot-demo-v1/snapshot-4bcc4a322a473abf32babe3df5779d14349542b1f0eb6f9dab0466a85c59cd42-2024-06-19-12.35.17/' restore.yaml | kubectl create -f -
sed 's/new-snapshot-demo-v1/snapshot-4dc1c53a29538b36e85003503a4bcac5dbde4cff59e81f1e3bb80b6c18c3fd03/' restore.yaml | kubectl create -f -

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Madhu-1, the object name new-snapshot-demo-v1 is missing in the docs. The docs didn't mention how it is applied here.

I noticed that it references this file.

I am trying to replicate the example and I am having trouble restoring my actual snapshot. I think something may be missing, but I don't know what.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just realized that it replaces the dataSource name in the restore.yaml file with that of the snapshot.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes this is sed to replace the name in the restore.yaml from the repo

@Madhu-1 Madhu-1 force-pushed the update-csi-snap-restore-doc branch from e2fd2ee to 2302321 Compare January 13, 2025 15:23
@@ -4,7 +4,8 @@

Status | Min K8s Version | Max K8s Version | snapshot-controller Version | snapshot-validation-webhook Version | CSI external-snapshotter sidecar Version | external-provisioner Version
--|--|--|--|--|--|--
Alpha | 1.27 | - | 7.0+ | 7.0+ | 7.0+ | 4.0+
Alpha | 1.27 | 1.32 | 7.0+ | 7.0+ | 7.0+ | 4.0+
Beta | 1.32 | - | 8.2+ | 8.2+ | 8.2+ | 4.0+
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you update the provisioner version to the latest which is 5.1.0?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added 5.1+. as the same format is followed for other versions. let me know if need to be updated to have 5.1.0

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, please update other places to be consistent.

updating the volumegroupsnapshot to beta1
API
@Madhu-1 Madhu-1 force-pushed the update-csi-snap-restore-doc branch from 2302321 to fbb0eb7 Compare January 13, 2025 15:30
@xing-yang
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 14, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Madhu-1, 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 14, 2025
@k8s-ci-robot k8s-ci-robot merged commit 7ad7935 into kubernetes-csi:master Jan 14, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants