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

Add aws limitation for migration and add limitation section #4881

Merged
merged 1 commit into from
May 16, 2022

Conversation

a-mccarthy
Copy link
Contributor

Signed-off-by: Abigail McCarthy mabigail@vmware.com

Thank you for contributing to Velero!

Please add a summary of your change

This adds a note for aws and azure plugins not supporting migration between regions.

Does your change fix a particular issue?

Fixes #4500

Please indicate you've done the following:

  • Accepted the DCO. Commits without the DCO will delay acceptance.
  • Created a changelog file or added /kind changelog-not-required as a comment on this pull request.
  • Updated the corresponding documentation in site/content/docs/main.

Signed-off-by: Abigail McCarthy <mabigail@vmware.com>
@a-mccarthy a-mccarthy added the kind/changelog-not-required PR does not require a user changelog. Often for docs, website, or build changes label May 2, 2022
@github-actions github-actions bot requested review from sseago and ywk253100 May 2, 2022 17:29
@a-mccarthy
Copy link
Contributor Author

This also adds in a new section for the limitations of migration. changes in the PR are only for the requested information for 4500. there is another issue to make more improvements to this page in this issue - #2167

@ywk253100 ywk253100 merged commit 9577ded into vmware-tanzu:main May 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation kind/changelog-not-required PR does not require a user changelog. Often for docs, website, or build changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Docs: clarify that the AWS volume snapshotter does not work between AWS regions
3 participants