Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

update volumegroupsnapshot to beta1 #612

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Madhu-1
Copy link
Contributor

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

updating the volumegroupsnapshot to beta1 API

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
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Madhu-1
Once this PR has been reviewed and has the lgtm label, please assign xing-yang for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@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.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. 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