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.
  1. 30 Aug, 2021 1 commit
  2. 26 Aug, 2021 2 commits
  3. 24 Aug, 2021 3 commits
  4. 20 Aug, 2021 2 commits
  5. 18 Aug, 2021 3 commits
  6. 17 Aug, 2021 1 commit
  7. 16 Aug, 2021 2 commits
  8. 12 Aug, 2021 2 commits
  9. 11 Aug, 2021 1 commit
    • Bridget McErlean's avatar
      Use LabelSelector in Action ResourceSelector · 368098b7
      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: default avatarBridget McErlean <bmcerlean@vmware.com>
      368098b7
  10. 10 Aug, 2021 1 commit
    • Bridget McErlean's avatar
      Skip restore of APIServices managed by Kubernetes · 984176f1
      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: default avatarBridget McErlean <bmcerlean@vmware.com>
      984176f1
  11. 06 Aug, 2021 1 commit
  12. 05 Aug, 2021 2 commits
    • JenTing Hsiao's avatar
      Add Kubernetes v1.22 CI test · 52896e80
      JenTing Hsiao authored
      Signed-off-by: default avatarJenTing Hsiao <jenting.hsiao@suse.com>
      52896e80
    • Bridget McErlean's avatar
      Use appropriate CRD API during readiness check (#4015) · d98c65f6
      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: default avatarBridget McErlean <bmcerlean@vmware.com>
      
      * Remove duplicate V1 CRD builder and update comment
      Signed-off-by: default avatarBridget McErlean <bmcerlean@vmware.com>
      d98c65f6
  13. 04 Aug, 2021 2 commits
  14. 03 Aug, 2021 1 commit
  15. 30 Jul, 2021 2 commits
  16. 29 Jul, 2021 4 commits
  17. 28 Jul, 2021 3 commits
  18. 27 Jul, 2021 7 commits