This project is mirrored from https://gitee.com/BiAn-MoShangHuaKai/velero.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
- 30 Aug, 2021 1 commit
-
-
Daniel Jiang authored
fixes for CVE-2021-3121 and CVE-2021-3580
-
- 26 Aug, 2021 2 commits
-
-
Scott Seago authored
Install/uninstall velero by CLI in the E2E test case
-
Wenkai Yin(尹文开) authored
Do this for two reasons: 1. Verify the functionalities for installation and uninstllation of CLI 2. We want to add upgrade test case which needs to install different versions of velero, calling libraries is impossible for this fixes #4062 Signed-off-by:
Wenkai Yin(尹文开) <yinw@vmware.com>
-
- 24 Aug, 2021 3 commits
-
-
Jack Lu authored
Signed-off-by:
jacklu1024 <jacklu1024@outlook.com>
-
kahirokunn authored
Signed-off-by:
kahirokunn <okinakahiro@gmail.com>
-
kahirokunn authored
Signed-off-by:
kahirokunn <okinakahiro@gmail.com>
-
- 20 Aug, 2021 2 commits
-
-
eleanor-millman authored
Signed-off-by:
Eleanor Millman <emillman@vmware.com>
-
Wenkai Yin(尹文开) authored
Change the base image to distroless Signed-off-by:
Wenkai Yin(尹文开) <yinw@vmware.com>
-
- 18 Aug, 2021 3 commits
-
-
Lars Lehtonen authored
Signed-off-by:
Lars Lehtonen <lars.lehtonen@gmail.com>
-
Himanshu Mehra authored
* Add document for TLS error 116 When using a custom S3 compatible server, backups/restore may fail with TLS error 116. This happens because the S3 server expects Velero to send client certificate during SSL TLS v1.3 handshake. You will need to modify your S3 server settings to turn off client certificate authentication. Signed-off-by:
Himanshu Mehra <himanshu.mehra91@gmail.com> * Add document for TLS error 116 When using a custom S3 compatible server, backups/restore may fail with TLS error 116. This happens because the S3 server expects Velero to send client certificate during SSL TLS v1.3 handshake. You will need to modify your S3 server settings to turn off client certificate authentication. Signed-off-by:
Himanshu Mehra <himanshu.mehra91@gmail.com> * Address comments from reviewers Signed-off-by:
Himanshu Mehra <himanshu.mehra91@gmail.com>
-
Dharma Bellamkonda authored
Signed-off-by:
Dharma Bellamkonda <bellamko@adobe.com>
-
- 17 Aug, 2021 1 commit
-
-
Wenkai Yin(尹文开) authored
Wait the namespace deletion completed before removing the CRDs when uninstalling the velero Fixes #3974 Signed-off-by:
Wenkai Yin(尹文开) <yinw@vmware.com>
-
- 16 Aug, 2021 2 commits
-
-
Tiger Kaovilai authored
Signed-off-by:
Tiger Kaovilai <tkaovila@redhat.com>
-
David L. Smith-Uchida authored
a timestamp. If two requests were happening very close together for the same backup, the second would fail randomly. Signed-off-by:
Dave Smith-Uchida <dsmithuchida@vmware.com>
-
- 12 Aug, 2021 2 commits
-
-
Wenkai Yin(尹文开) authored
Fix the random failure by increasing the timeout and introducing few minor refactor/bug fixes Fixes #3970 Signed-off-by:
Wenkai Yin(尹文开) <yinw@vmware.com>
-
Scott Seago authored
Skip restore of APIServices managed by Kubernetes
-
- 11 Aug, 2021 1 commit
-
-
Bridget McErlean authored
Instead of converting the unstructured item to check for the presence of the `kube-aggregator.kubernetes.io/automanaged` label, use this label in the `AppliesTo` to enable the restore logic to select the item. This means that any item that matches the selector will have restore skipped. Also add a new test case to the restore action test to check that label selectors are applied correctly. Signed-off-by:
Bridget McErlean <bmcerlean@vmware.com>
-
- 10 Aug, 2021 1 commit
-
-
Bridget McErlean authored
It was discovered during Velero 1.6.3 upgrade testing that Velero was restoring `APIService` objects for APIs that are no longer being served by Kubernetes 1.22. If these items were restored, it would break the behaviour of discovery within the cluster. This change introduces a new RestoreItemAction plugin that skips the restore of any `APIService` object which is managed by Kubernetes such as those for built-in APIs or CRDs. The `APIService`s for these will be created when the Kubernetes API server starts or when new CRDs are registered. These objects are identified by looking for the `kube-aggregator.kubernetes.io/automanaged` label. Signed-off-by:
Bridget McErlean <bmcerlean@vmware.com>
-
- 06 Aug, 2021 1 commit
-
-
Scott Seago authored
Add Kubernetes v1.22 CI test
-
- 05 Aug, 2021 2 commits
-
-
JenTing Hsiao authored
Signed-off-by:
JenTing Hsiao <jenting.hsiao@suse.com>
-
Bridget McErlean authored
* Use appropriate CRD API during readiness check The readiness check for the Velero CRDs was still using the v1beta1 API. This would cause the readiness check to fail on 1.22 clusters as the v1beta1 API is no longer available. Previously, this error would be ignored and the installation would proceed, however with #4002, we are no longer ignoring errors from this check. This change modifies the CRD readiness check to check the CRDs using the same API version that was used when submitting the CRDs to the cluster. It also introduces a new CRD builder using the V1 API for testing. This change also fixes a bug that was identified in the polling code where if the CRDs were not ready on the first polling iteration, they would be added again to the list of CRDs to check resulting in duplicates. This would cause the length check to fail on all subsequent polls and the timeout would always be reached. Signed-off-by:
Bridget McErlean <bmcerlean@vmware.com> * Remove duplicate V1 CRD builder and update comment Signed-off-by:
Bridget McErlean <bmcerlean@vmware.com>
-
- 04 Aug, 2021 2 commits
-
-
Scott Seago authored
pkg/install: fix dropped error
-
Marcel Haupt authored
* Restic Backup: Add check if Pod is successful or failed for emptyDir. Fix #3812 * Add changelog Signed-off-by:
mahaupt <marcel.haupt@gepardec.com>
-
- 03 Aug, 2021 1 commit
-
-
Lars Lehtonen authored
Signed-off-by:
Lars Lehtonen <lars.lehtonen@gmail.com>
-
- 30 Jul, 2021 2 commits
-
-
Daniel Jiang authored
Patch the resources of velero and kibishii when running E2E testing
-
Daniel Jiang authored
Signed-off-by:
Daniel Jiang <jiangd@vmware.com>
-
- 29 Jul, 2021 4 commits
-
-
Wenkai Yin(尹文开) authored
Select the velero deployment with both label and container name Fixes #3961 Signed-off-by:
Wenkai Yin(尹文开) <yinw@vmware.com>
-
David L. Smith-Uchida authored
-
Wenkai Yin(尹文开) authored
Add the image pull secret to the service account when deploying velero and kibishii to avoid the image pull limit issue of Docker Hub Fixes #3966 Signed-off-by:
Wenkai Yin(尹文开) <yinw@vmware.com>
-
Shawn Hurley authored
* also added the Q&A Discussion Board Signed-off-by:
Shawn Hurley <smhurley00@gmail.com>
-
- 28 Jul, 2021 3 commits
-
-
Wenkai Yin(尹文开) authored
enable e2e tests to choose crd apiVersion
-
Scott Seago authored
Signed-off-by:
Scott Seago <sseago@redhat.com>
-
Wenkai Yin(尹文开) authored
The backup name must be no more than 63 characters otherwise we'll get error on vSphere platform: Failed to create snapshot record: Snapshot.backupdriver.cnsdp.vmware.com \"snap-8945e7df-069e-4f56-aeb5-75b1dd87547f\" is invalid: metadata.labels: Invalid value: \"backup-bsl-e7a1d0f3-2f29-4d80-9184-6214dac91d96-e7a1d0f3-2f29-4d80-9184-6214dac91d96\": must be no more than 63 characters" Signed-off-by:
Wenkai Yin(尹文开) <yinw@vmware.com>
-
- 27 Jul, 2021 7 commits
-
-
Bridget McErlean authored
Bump CRD API version to v1
-
JenTing Hsiao authored
Signed-off-by:
JenTing Hsiao <jenting.hsiao@suse.com>
-
JenTing Hsiao authored
Signed-off-by:
JenTing Hsiao <jenting.hsiao@suse.com>
-
JenTing Hsiao authored
Signed-off-by:
JenTing Hsiao <jenting.hsiao@suse.com>
-
JenTing Hsiao authored
Signed-off-by:
JenTing Hsiao <jenting.hsiao@suse.com>
-
JenTing Hsiao authored
update the path of crds.go to ignore it. Signed-off-by:
JenTing Hsiao <jenting.hsiao@suse.com>
-
JenTing Hsiao authored
Signed-off-by:
JenTing Hsiao <jenting.hsiao@suse.com>
-