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

Update HorizontalPodAutoscaler version in velero.io 

Signed-off-by: Xun Jiang <blackpiglet@gmail.com>
pull/5967/head
Xun Jiang 2023-03-08 10:00:40 +08:00
parent 8bed159023
commit 6a295cb0bb
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.github/workflows/nightly-trivy-scan.yml vendored
View File

@ -11,9 +11,9 @@ jobs:
fail-fast: false fail-fast: false
matrix: matrix:
# maintain the versions of Velero those need security scan # maintain the versions of Velero those need security scan
versions: [main, release-1.10-dev, release-1.9-dev] versions: [main]
# list of images that need scan # list of images that need scan
images: [velero, velero-restore-helper, velero-restic-restore-helper] images: [velero, velero-restore-helper]
permissions: permissions:
security-events: write # for github/codeql-action/upload-sarif to upload SARIF results security-events: write # for github/codeql-action/upload-sarif to upload SARIF results

2
site/content/docs/main/enable-api-group-versions-feature.md
View File

@ -17,7 +17,7 @@ For the most up-to-date information on Kubernetes API version compatibility, you
## How the Enable API Group Versions Feature Works ## How the Enable API Group Versions Feature Works
When the Enable API Group Versions feature is enabled on the source cluster, Velero will not only back up Kubernetes preferred API group versions, but it will also back up all supported versions on the cluster. As an example, consider the resource `horizontalpodautoscalers` which falls under the `autoscaling` group. Without the feature flag enabled, only the preferred API group version for autoscaling, `v1` will be backed up. With the feature enabled, the remaining supported versions, `v2beta1` and `v2beta2` will also be backed up. Once the versions are stored in the backup tarball file, they will be available to be restored on the destination cluster. When the Enable API Group Versions feature is enabled on the source cluster, Velero will not only back up Kubernetes preferred API group versions, but it will also back up all supported versions on the cluster. As an example, consider the resource `horizontalpodautoscalers` which falls under the `autoscaling` group. Without the feature flag enabled, only the preferred API group version for autoscaling, `v2` will be backed up. With the feature enabled, the remaining supported versions, `v1` will also be backed up. Once the versions are stored in the backup tarball file, they will be available to be restored on the destination cluster.
When the Enable API Group Versions feature is enabled on the destination cluster, Velero restore will choose the version to restore based on an API group version priority order. When the Enable API Group Versions feature is enabled on the destination cluster, Velero restore will choose the version to restore based on an API group version priority order.