vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #4439 from neha-viswanathan/3940-velero-migration-doc-update 

update migration across different k8s versions section
pull/4686/head
Daniel Jiang 2022-02-22 12:10:57 +08:00 committed by GitHub
parent ea3c72310b d17db327f7
commit e08e4f380f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
site/content/docs/main/migration-case.md
View File

@ -53,6 +53,7 @@ If you encounter issues, make sure that Velero is running in the same namespace
## Migrating Workloads Across Different Kubernetes Versions
Migration across clusters that are not running the same version of Kubernetes might be possible, but some factors need to be considered: compatibility of API groups between clusters for each custom resource, and if a Kubernetes version upgrade breaks the compatibility of core/native API groups. For more information about API group versions, please see [EnableAPIGroupVersions](enable-api-group-versions-feature.md).
**Note:** Velero doesn't support restoring into a cluster with a lower Kubernetes version than where the backup was taken.
[1]: how-velero-works.md#set-a-backup-to-expire
[2]: restic.md

1
site/content/docs/v1.6/migration-case.md
View File

@ -53,6 +53,7 @@ If you encounter issues, make sure that Velero is running in the same namespace
## Migrating Workloads Across Different Kubernetes Versions
Migration across clusters that are not running the same version of Kubernetes might be possible, but some factors need to be considered: compatibility of API groups between clusters for each custom resource, and if a Kubernetes version upgrade breaks the compatibility of core/native API groups. For more information about API group versions, please see [EnableAPIGroupVersions](enable-api-group-versions-feature.md).
**Note:** Velero doesn't support restoring into a cluster with a lower Kubernetes version than where the backup was taken.
[1]: how-velero-works.md#set-a-backup-to-expire
[2]: restic.md

1
site/content/docs/v1.7/migration-case.md
View File

@ -53,6 +53,7 @@ If you encounter issues, make sure that Velero is running in the same namespace
## Migrating Workloads Across Different Kubernetes Versions
Migration across clusters that are not running the same version of Kubernetes might be possible, but some factors need to be considered: compatibility of API groups between clusters for each custom resource, and if a Kubernetes version upgrade breaks the compatibility of core/native API groups. For more information about API group versions, please see [EnableAPIGroupVersions](enable-api-group-versions-feature.md).
**Note:** Velero doesn't support restoring into a cluster with a lower Kubernetes version than where the backup was taken.
[1]: how-velero-works.md#set-a-backup-to-expire
[2]: restic.md