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

Document and test upgrades from v1.4.3 and v1.5.3 to v1.6.0 #3562

Closed
4 tasks done
nrb opened this issue Mar 11, 2021 · 2 comments
Closed
4 tasks done

Document and test upgrades from v1.4.3 and v1.5.3 to v1.6.0 #3562

nrb opened this issue Mar 11, 2021 · 2 comments
Assignees
Labels
Area/Documentation kind/release-blocker Must fix issues for the coming release (milestone)
Milestone

Comments

@nrb
Copy link
Contributor

nrb commented Mar 11, 2021

Describe the problem/challenge you have

Full upgrade steps are not documented for v1.5.3 and v1.4.3 to v1.6.0. These should be done before final release.

Describe the solution you'd like

Documentation for upgrading to v1.6.0 which should include (but not limited to):

  • Any CRD upgrades necessary
  • Impacts on restic data

Anything else you would like to add:

v1.4.3 instructions should be included since requiring uses to move through 2 versions to get a working update is not possible in some circumstances, such as when Velero is included in a product.


  • Update v1.4 doc
  • Update v1.5 doc
  • Update v1.6 doc
  • Test upgrade to v1.6.0
@nrb nrb added Area/Documentation kind/release-blocker Must fix issues for the coming release (milestone) labels Mar 11, 2021
@nrb nrb added this to the v1.6.0 milestone Mar 11, 2021
@carlisia carlisia self-assigned this Mar 12, 2021
@carlisia carlisia mentioned this issue Mar 12, 2021
5 tasks
@carlisia
Copy link
Contributor

@vmware-tanzu/velero-owners + @jenting: closing this as it has all been done as per #3623 and coordination.

@carlisia
Copy link
Contributor

The documentation update was merged with this PR: #3568.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/Documentation kind/release-blocker Must fix issues for the coming release (milestone)
Projects
None yet
Development

No branches or pull requests

2 participants