mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-01-05 04:55:22 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

update migration across different Kubernetes versions section

Browse Source 
Signed-off-by: Neha Viswanathan <itsnehavis@gmail.com>
This commit is contained in:
Neha Viswanathan
2021-12-09 20:34:51 -08:00
parent b6992101a4
commit d17db327f7
3 changed files with 3 additions and 0 deletions
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