Merge pull request #8304 from shubham-pampattiwar/fix-err-str-cp-1.14

[cherry-pick Release-1.14] Remove multiple single quotes from Velero backup.status.validationErrors field

.github/auto-assignees.yml

@@ -13,10 +13,10 @@ reviewers:
       - reasonerjt
       - ywk253100
       - blackpiglet
+      - qiuming-best
       - shubham-pampattiwar
       - Lyndon-Li
       - anshulahuja98
-      - kaovilai
 
     tech-writer:
       - sseago

.github/pull_request_template.md

@@ -9,5 +9,5 @@ Fixes #(issue)
 # Please indicate you've done the following:
 
 - [ ] [Accepted the DCO](https://velero.io/docs/v1.5/code-standards/#dco-sign-off). Commits without the DCO will delay acceptance.
-- [ ] [Created a changelog file (`make new-changelog`)](https://velero.io/docs/main/code-standards/#adding-a-changelog) or comment `/kind changelog-not-required` on this PR.
+- [ ] [Created a changelog file](https://velero.io/docs/v1.5/code-standards/#adding-a-changelog) or added `/kind changelog-not-required` as a comment on this pull request.
 - [ ] Updated the corresponding documentation in `site/content/docs/main`.

.github/workflows/crds-verify-kind.yaml

@@ -0,0 +1,93 @@
+name: "Verify Velero CRDs across k8s versions"
+on:
+  pull_request:
+    # Do not run when the change only includes these directories.
+    paths-ignore:
+      - "site/**"
+      - "design/**"
+
+jobs:
+  # Build the Velero CLI once for all Kubernetes versions, and cache it so the fan-out workers can get it.
+  build-cli:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version: '1.22.6'
+        id: go
+      # Look for a CLI that's made for this PR
+      - name: Fetch built CLI
+        id: cache
+        uses: actions/cache@v4
+        env:
+          cache-name: cache-velero-cli
+        with:
+          path: ./_output/bin/linux/amd64/velero
+          # The cache key a combination of the current PR number, and a SHA256 hash of the Velero binary
+          key: velero-${{ github.event.pull_request.number }}-${{ hashFiles('./_output/bin/linux/amd64/velero') }}
+          # This key controls the prefixes that we'll look at in the cache to restore from
+          restore-keys: |
+            velero-${{ github.event.pull_request.number }}-
+
+      - name: Fetch cached go modules
+        uses: actions/cache@v4
+        if: steps.cache.outputs.cache-hit != 'true'
+        with:
+          path: ~/go/pkg/mod
+          key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
+          restore-keys: |
+            ${{ runner.os }}-go-
+
+      - name: Check out the code
+        uses: actions/checkout@v4
+        if: steps.cache.outputs.cache-hit != 'true'
+
+      # If no binaries were built for this PR, build it now.
+      - name: Build Velero CLI
+        if: steps.cache.outputs.cache-hit != 'true'
+        run: |
+          make local
+
+  # Check the common CLI against all Kubernetes versions
+  crd-check:
+    needs: build-cli
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        # Latest k8s versions. There's no series-based tag, nor is there a latest tag.
+        k8s:
+          - 1.23.17
+          - 1.24.17
+          - 1.25.16
+          - 1.26.13
+          - 1.27.10
+          - 1.28.6
+          - 1.29.1
+    # All steps run in parallel unless otherwise specified.
+    # See https://docs.github.com/en/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs
+    steps:
+      - name: Fetch built CLI
+        id: cache
+        uses: actions/cache@v4
+        env:
+          cache-name: cache-velero-cli
+        with:
+          path: ./_output/bin/linux/amd64/velero
+          # The cache key a combination of the current PR number, and a SHA256 hash of the Velero binary
+          key: velero-${{ github.event.pull_request.number }}-${{ hashFiles('./_output/bin/linux/amd64/velero') }}
+          # This key controls the prefixes that we'll look at in the cache to restore from
+          restore-keys: |
+            velero-${{ github.event.pull_request.number }}-
+      - uses: engineerd/setup-kind@v0.5.0
+        with:
+          version: "v0.21.0"
+          image: "kindest/node:v${{ matrix.k8s }}"
+      - name: Install CRDs
+        run: |
+          kubectl cluster-info
+          kubectl get pods -n kube-system
+          kubectl version
+          echo "current-context:" $(kubectl config current-context)
+          echo "environment-kubeconfig:" ${KUBECONFIG}
+          ./_output/bin/linux/amd64/velero install --crds-only --dry-run -oyaml | kubectl apply -f -

.github/workflows/e2e-test-kind.yaml

@@ -6,28 +6,16 @@ on:
     paths-ignore:
       - "site/**"
       - "design/**"
-      - "**/*.md"
 jobs:
-  get-go-version:
-    uses: ./.github/workflows/get-go-version.yaml
-    with:
-      ref: ${{ github.event.pull_request.base.ref }}
-
   # Build the Velero CLI and image once for all Kubernetes versions, and cache it so the fan-out workers can get it.
   build:
     runs-on: ubuntu-latest
-    needs: get-go-version
-    outputs:
-      minio-dockerfile-sha: ${{ steps.minio-version.outputs.dockerfile_sha }}
     steps:
-      - name: Check out the code
-        uses: actions/checkout@v5
-      
-      - name: Set up Go version
-        uses: actions/setup-go@v6
+      - name: Set up Go
+        uses: actions/setup-go@v5
         with:
-          go-version: ${{ needs.get-go-version.outputs.version }}
-
+          go-version: '1.22.6'
+        id: go
       # Look for a CLI that's made for this PR
       - name: Fetch built CLI
         id: cli-cache
@@ -43,6 +31,17 @@ jobs:
           path: ./velero.tar
           # The cache key a combination of the current PR number and the commit SHA
           key: velero-image-${{ github.event.pull_request.number }}-${{ github.sha }}
+      - name: Fetch cached go modules
+        uses: actions/cache@v4
+        if: steps.cli-cache.outputs.cache-hit != 'true'
+        with:
+          path: ~/go/pkg/mod
+          key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
+          restore-keys: |
+            ${{ runner.os }}-go-
+      - name: Check out the code
+        uses: actions/checkout@v4
+        if: steps.cli-cache.outputs.cache-hit != 'true' || steps.image-cache.outputs.cache-hit != 'true'
       # If no binaries were built for this PR, build it now.
       - name: Build Velero CLI
         if: steps.cli-cache.outputs.cache-hit != 'true'
@@ -52,91 +51,47 @@ jobs:
       - name: Build Velero Image
         if: steps.image-cache.outputs.cache-hit != 'true'
         run: |
-          IMAGE=velero VERSION=pr-test BUILD_OUTPUT_TYPE=docker make container
-          docker save velero:pr-test-linux-amd64 -o ./velero.tar
-      # Check and build MinIO image once for all e2e tests
-      - name: Check Bitnami MinIO Dockerfile version
-        id: minio-version
-        run: |
-          DOCKERFILE_SHA=$(curl -s https://api.github.com/repos/bitnami/containers/commits?path=bitnami/minio/2025/debian-12/Dockerfile\&per_page=1 | jq -r '.[0].sha')
-          echo "dockerfile_sha=${DOCKERFILE_SHA}" >> $GITHUB_OUTPUT
-      - name: Cache MinIO Image
-        uses: actions/cache@v4
-        id: minio-cache
-        with:
-          path: ./minio-image.tar
-          key: minio-bitnami-${{ steps.minio-version.outputs.dockerfile_sha }}
-      - name: Build MinIO Image from Bitnami Dockerfile
-        if: steps.minio-cache.outputs.cache-hit != 'true'
-        run: |
-          echo "Building MinIO image from Bitnami Dockerfile..."
-          git clone --depth 1 https://github.com/bitnami/containers.git /tmp/bitnami-containers
-          cd /tmp/bitnami-containers/bitnami/minio/2025/debian-12
-          docker build -t bitnami/minio:local .
-          docker save bitnami/minio:local > ${{ github.workspace }}/minio-image.tar
-  # Create json of k8s versions to test
-  # from guide: https://stackoverflow.com/a/65094398/4590470
-  setup-test-matrix:
-    runs-on: ubuntu-latest
-    env:
-      GH_TOKEN: ${{ github.token }}
-    outputs:
-      matrix: ${{ steps.set-matrix.outputs.matrix }}
-    steps:
-      - name: Set k8s versions
-        id: set-matrix
-        # everything excluding older tags. limits needs to be high enough to cover all latest versions
-        # and test labels
-        # grep -E "v[1-9]\.(2[5-9]|[3-9][0-9])" filters for v1.25 to v9.99
-        # and removes older patches of the same minor version
-        # awk -F. '{if(!a[$1"."$2]++)print $1"."$2"."$NF}'
-        run: |
-          echo "matrix={\
-            \"k8s\":$(wget -q -O - "https://hub.docker.com/v2/namespaces/kindest/repositories/node/tags?page_size=50" | grep -o '"name": *"[^"]*' | grep -o '[^"]*$' | grep -v -E "alpha|beta" | grep -E "v[1-9]\.(2[5-9]|[3-9][0-9])" | awk -F. '{if(!a[$1"."$2]++)print $1"."$2"."$NF}' | sort -r | sed s/v//g | jq -R -c -s 'split("\n")[:-1]'),\
-            \"labels\":[\
-              \"Basic && (ClusterResource || NodePort || StorageClass)\", \
-              \"ResourceFiltering && !Restic\", \
-              \"ResourceModifier || (Backups && BackupsSync) || PrivilegesMgmt || OrderedResources\", \
-              \"(NamespaceMapping && Single && Restic) || (NamespaceMapping && Multiple && Restic)\"\
-            ]}" >> $GITHUB_OUTPUT
-
+          IMAGE=velero VERSION=pr-test make container
+          docker save velero:pr-test -o ./velero.tar
   # Run E2E test against all Kubernetes versions on kind
   run-e2e-test:
-    needs:
-      - build
-      - setup-test-matrix
-      - get-go-version
+    needs: build
     runs-on: ubuntu-latest
     strategy:
-      matrix: ${{fromJson(needs.setup-test-matrix.outputs.matrix)}}
+      matrix:
+        k8s:
+          - 1.23.17
+          - 1.24.17
+          - 1.25.16
+          - 1.26.13
+          - 1.27.10
+          - 1.28.6
+          - 1.29.1
+        focus:
+          # tests to focus on, use `|` to concatenate multiple regexes to run on the same job
+          # ordered according to e2e_suite_test.go order
+          - Basic\]\[ClusterResource
+          - ResourceFiltering
+          - ResourceModifier|Backups|PrivilegesMgmt\]\[SSR
+          - Schedule\]\[OrderedResources
+          - NamespaceMapping\]\[Single\]\[Restic|NamespaceMapping\]\[Multiple\]\[Restic
+          - Basic\]\[Nodeport
+          - Basic\]\[StorageClass
       fail-fast: false
     steps:
+      - name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version: '1.22.6'
+        id: go
       - name: Check out the code
-        uses: actions/checkout@v5
-
-      - name: Set up Go version
-        uses: actions/setup-go@v6
-        with:
-          go-version: ${{ needs.get-go-version.outputs.version }}
-
-      # Fetch the pre-built MinIO image from the build job
-      - name: Fetch built MinIO Image
-        uses: actions/cache@v4
-        id: minio-cache
-        with:
-          path: ./minio-image.tar
-          key: minio-bitnami-${{ needs.build.outputs.minio-dockerfile-sha }}
-      - name: Load MinIO Image
-        run: |
-          echo "Loading MinIO image..."
-          docker load < ./minio-image.tar
+        uses: actions/checkout@v4
       - name: Install MinIO
-        run: |
-          docker run -d --rm -p 9000:9000 -e "MINIO_ROOT_USER=minio" -e "MINIO_ROOT_PASSWORD=minio123" -e "MINIO_DEFAULT_BUCKETS=bucket,additional-bucket" bitnami/minio:local
-      - uses: engineerd/setup-kind@v0.6.2
+        run:
+          docker run -d --rm -p 9000:9000 -e "MINIO_ACCESS_KEY=minio" -e "MINIO_SECRET_KEY=minio123" -e "MINIO_DEFAULT_BUCKETS=bucket,additional-bucket" bitnami/minio:2021.6.17-debian-10-r7
+      - uses: engineerd/setup-kind@v0.5.0
         with:
-          skipClusterLogsExport: true
-          version: "v0.27.0"
+          version: "v0.21.0"
           image: "kindest/node:v${{ matrix.k8s }}"
       - name: Fetch built CLI
         id: cli-cache
@@ -153,6 +108,14 @@ jobs:
       - name: Load Velero Image
         run:
           kind load image-archive velero.tar
+      # always try to fetch the cached go modules as the e2e test needs it either
+      - name: Fetch cached go modules
+        uses: actions/cache@v4
+        with:
+          path: ~/go/pkg/mod
+          key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
+          restore-keys: |
+            ${{ runner.os }}-go-
       - name: Run E2E test
         run: |
           cat << EOF > /tmp/credential
@@ -165,22 +128,13 @@ jobs:
           curl -LO https://dl.k8s.io/release/v${{ matrix.k8s }}/bin/linux/amd64/kubectl
           sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl
 
-          git clone https://github.com/vmware-tanzu-experiments/distributed-data-generator.git -b main /tmp/kibishii
-
-          GOPATH=~/go \
-              CLOUD_PROVIDER=kind \
-              OBJECT_STORE_PROVIDER=aws \
-              BSL_CONFIG=region=minio,s3ForcePathStyle="true",s3Url=http://$(hostname -i):9000 \
-              CREDS_FILE=/tmp/credential \
-              BSL_BUCKET=bucket \
-              ADDITIONAL_OBJECT_STORE_PROVIDER=aws \
-              ADDITIONAL_BSL_CONFIG=region=minio,s3ForcePathStyle="true",s3Url=http://$(hostname -i):9000 \
-              ADDITIONAL_CREDS_FILE=/tmp/credential \
-              ADDITIONAL_BSL_BUCKET=additional-bucket \
-              VELERO_IMAGE=velero:pr-test-linux-amd64 \
-              PLUGINS=velero/velero-plugin-for-aws:latest \
-              GINKGO_LABELS="${{ matrix.labels }}" \
-              KIBISHII_DIRECTORY=/tmp/kibishii/kubernetes/yaml/ \
+          GOPATH=~/go CLOUD_PROVIDER=kind \
+              OBJECT_STORE_PROVIDER=aws BSL_CONFIG=region=minio,s3ForcePathStyle="true",s3Url=http://$(hostname -i):9000 \
+              CREDS_FILE=/tmp/credential BSL_BUCKET=bucket \
+              ADDITIONAL_OBJECT_STORE_PROVIDER=aws ADDITIONAL_BSL_CONFIG=region=minio,s3ForcePathStyle="true",s3Url=http://$(hostname -i):9000 \
+              ADDITIONAL_CREDS_FILE=/tmp/credential ADDITIONAL_BSL_BUCKET=additional-bucket \
+              GINKGO_FOCUS='${{ matrix.focus }}' VELERO_IMAGE=velero:pr-test \
+              GINKGO_SKIP='SKIP_KIND|pv-backup|Restic|Snapshot|LongTime' \
               make -C test/ run-e2e
         timeout-minutes: 30
       - name: Upload debug bundle
@@ -188,4 +142,4 @@ jobs:
         uses: actions/upload-artifact@v4
         with:
           name: DebugBundle
-          path: /home/runner/work/velero/velero/test/e2e/debug-bundle*
+          path: /home/runner/work/velero/velero/test/e2e/debug-bundle*

.github/workflows/get-go-version.yaml

@@ -1,33 +0,0 @@
-on:
-  workflow_call:
-    inputs:
-      ref:
-        description: "The target branch's ref"
-        required: true
-        type: string
-    outputs:
-      version: 
-        description: "The expected Go version"
-        value: ${{ jobs.extract.outputs.version }}
-
-jobs:
-  extract:
-      runs-on: ubuntu-latest
-      outputs:
-        version: ${{ steps.pick-version.outputs.version }}
-      steps:
-        - name: Check out the code
-          uses: actions/checkout@v5
-
-        - id: pick-version
-          run: |
-            if [ "${{ inputs.ref }}" == "main" ]; then
-              version=$(grep '^go ' go.mod | awk '{print $2}' | cut -d. -f1-2)
-            else
-              goDirectiveVersion=$(grep '^go ' go.mod | awk '{print $2}')
-              toolChainVersion=$(grep '^toolchain ' go.mod | awk '{print $2}')
-              version=$(printf "%s\n%s\n" "$goDirectiveVersion" "$toolChainVersion" | sort -V | tail -n1)
-            fi
-
-            echo "version=$version"
-            echo "version=$version" >> $GITHUB_OUTPUT

.github/workflows/nightly-trivy-scan.yml

@@ -13,13 +13,13 @@ jobs:
         # maintain the versions of Velero those need security scan
         versions: [main]
         # list of images that need scan
-        images: [velero, velero-plugin-for-aws, velero-plugin-for-gcp, velero-plugin-for-microsoft-azure]
+        images: [velero, velero-restore-helper]
     permissions:
       security-events: write  # for github/codeql-action/upload-sarif to upload SARIF results
 
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v4
 
       - name: Run Trivy vulnerability scanner
         uses: aquasecurity/trivy-action@master
@@ -31,6 +31,6 @@ jobs:
           output: 'trivy-results.sarif'
 
       - name: Upload Trivy scan results to GitHub Security tab
-        uses: github/codeql-action/upload-sarif@v4
+        uses: github/codeql-action/upload-sarif@v3
         with:
           sarif_file: 'trivy-results.sarif'

.github/workflows/pr-changelog-check.yml

@@ -12,7 +12,7 @@ jobs:
     steps:
 
     - name: Check out the code
-      uses: actions/checkout@v5
+      uses: actions/checkout@v4
 
     - name: Changelog check
       if: ${{ !(contains(github.event.pull_request.labels.*.name, 'kind/changelog-not-required') || contains(github.event.pull_request.labels.*.name, 'Design') || contains(github.event.pull_request.labels.*.name, 'Website') || contains(github.event.pull_request.labels.*.name, 'Documentation'))}}

.github/workflows/pr-ci-check.yml

@@ -1,30 +1,30 @@
 name: Pull Request CI Check
 on: [pull_request]
 jobs:
-  get-go-version:
-    uses: ./.github/workflows/get-go-version.yaml
-    with:
-      ref: ${{ github.event.pull_request.base.ref }}
-
   build:
     name: Run CI
-    needs: get-go-version
     runs-on: ubuntu-latest
     strategy:
       fail-fast: false
     steps:
-      - name: Check out the code
-        uses: actions/checkout@v5
-
-      - name: Set up Go version
-        uses: actions/setup-go@v6
+      - name: Set up Go
+        uses: actions/setup-go@v5
         with:
-          go-version: ${{ needs.get-go-version.outputs.version }}      
-
+          go-version: '1.22.6'
+        id: go
+      - name: Check out the code
+        uses: actions/checkout@v4
+      - name: Fetch cached go modules
+        uses: actions/cache@v4
+        with:
+          path: ~/go/pkg/mod
+          key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
+          restore-keys: |
+            ${{ runner.os }}-go-
       - name: Make ci
         run: make ci
       - name: Upload test coverage
-        uses: codecov/codecov-action@v5
+        uses: codecov/codecov-action@v4
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           files: coverage.out

.github/workflows/pr-codespell.yml

@@ -8,14 +8,14 @@ jobs:
     steps:
 
     - name: Check out the code
-      uses: actions/checkout@v5
+      uses: actions/checkout@v4
 
     - name: Codespell
       uses: codespell-project/actions-codespell@master
       with:
-        # ignore the config/.../crd.go file as it's generated binary data that is edited elsewhere.
+        # ignore the config/.../crd.go file as it's generated binary data that is edited elswhere.
         skip: .git,*.png,*.jpg,*.woff,*.ttf,*.gif,*.ico,./config/crd/v1beta1/crds/crds.go,./config/crd/v1/crds/crds.go,./config/crd/v2alpha1/crds/crds.go,./go.sum,./LICENSE
-        ignore_words_list: iam,aks,ist,bridget,ue,shouldnot,atleast,notin,sme,optin,sie
+        ignore_words_list: iam,aks,ist,bridget,ue,shouldnot,atleast,notin,sme
         check_filenames: true
         check_hidden: true
 

.github/workflows/pr-containers.yml

@@ -13,7 +13,7 @@ jobs:
     name: Build
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v5
+    - uses: actions/checkout@v4
       name: Checkout
 
     - name: Set up QEMU

.github/workflows/pr-goreleaser.yml

@@ -14,7 +14,7 @@ jobs:
     name: Build
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v5
+    - uses: actions/checkout@v4
       name: Checkout
 
     - name: Verify .goreleaser.yml and try a dryrun release.

.github/workflows/pr-linter-check.yml

@@ -1,32 +1,20 @@
 name: Pull Request Linter Check
-on:
-  pull_request:
-    # Do not run when the change only includes these directories.
-    paths-ignore:
-      - "site/**"
-      - "design/**"
-      - "**/*.md"
+on: [pull_request]
 jobs:
-  get-go-version:
-    uses: ./.github/workflows/get-go-version.yaml
-    with:
-      ref: ${{ github.event.pull_request.base.ref }}
 
   build:
     name: Run Linter Check
     runs-on: ubuntu-latest
-    needs: get-go-version
     steps:
       - name: Check out the code
-        uses: actions/checkout@v5
-
-      - name: Set up Go version
-        uses: actions/setup-go@v6
+        uses: actions/checkout@v4
+      - name: Set up Go
+        uses: actions/setup-go@v5
         with:
-          go-version: ${{ needs.get-go-version.outputs.version }}
-
+          go-version-file: 'go.mod'
+        id: go
       - name: Linter check
-        uses: golangci/golangci-lint-action@v8
+        uses: golangci/golangci-lint-action@v6
         with:
-          version: v2.1.1
+          version: v1.57.2
           args: --verbose

.github/workflows/push-builder.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
 
-    - uses: actions/checkout@v5
+    - uses: actions/checkout@v4
       with:
         # The default value is "1" which fetches only a single commit. If we merge PR without squash or rebase,
         # there are at least two commits: the first one is the merge commit and the second one is the real commit

.github/workflows/push.yml

@@ -9,55 +9,95 @@ on:
       - '*'
 
 jobs:
-  get-go-version:
-    uses: ./.github/workflows/get-go-version.yaml
-    with:
-      ref: ${{ github.ref }}
 
   build:
     name: Build
     runs-on: ubuntu-latest
-    needs: get-go-version
     steps:
-      - name: Check out the code
-        uses: actions/checkout@v5
 
-      - name: Set up Go version
-        uses: actions/setup-go@v6
-        with:
-          go-version: ${{ needs.get-go-version.outputs.version }}
+    - name: Set up Go
+      uses: actions/setup-go@v5
+      with:
+        go-version: '1.22.6'
+      id: go
 
-      - name: Set up QEMU
-        id: qemu
-        uses: docker/setup-qemu-action@v3
-        with:
-          platforms: all
-      - name: Set up Docker Buildx
-        id: buildx
-        uses: docker/setup-buildx-action@v3
-        with:
-          version: latest
-      - name: Build
-        run: |
-          make local
-          # Clean go cache to ease the build environment storage pressure.
-          go clean -modcache -cache
-      - name: Test
-        run: make test
-      - name: Upload test coverage
-        uses: codecov/codecov-action@v5
-        with:
-          token: ${{ secrets.CODECOV_TOKEN }}
-          files: coverage.out
-          verbose: true
-      # Only try to publish the container image from the root repo; forks don't have permission to do so and will always get failures.
-      - name: Publish container image
-        if: github.repository == 'vmware-tanzu/velero'
-        run: |
-          sudo swapoff -a
-          sudo rm -f /mnt/swapfile
-          docker system prune -a --force
+    - uses: actions/checkout@v4
+
+    - id: 'auth'
+      uses: google-github-actions/auth@v2
+      with:
+        credentials_json: '${{ secrets.GCS_SA_KEY }}'
+
+    - name: 'set up GCloud SDK'
+      uses: google-github-actions/setup-gcloud@v2
+
+    - name: 'use gcloud CLI'
+      run: |
+        gcloud info
+
+    - name: Set up QEMU
+      id: qemu
+      uses: docker/setup-qemu-action@v3
+      with:
+        platforms: all
+
+    - name: Set up Docker Buildx
+      id: buildx
+      uses: docker/setup-buildx-action@v3
+      with:
+        version: latest
+
+    - name: Build
+      run: |
+        make local
+        # Clean go cache to ease the build environment storage pressure.
+        go clean -modcache -cache
+
+    - name: Test
+      run: make test
+
+    - name: Upload test coverage
+      uses: codecov/codecov-action@v4
+      with:
+        token: ${{ secrets.CODECOV_TOKEN }}
+        files: coverage.out
+        verbose: true
+
+    # Use the JSON key in secret to login gcr.io
+    - uses: 'docker/login-action@v3'
+      with:
+        registry: 'gcr.io' # or REGION.docker.pkg.dev
+        username: '_json_key'
+        password: '${{ secrets.GCR_SA_KEY }}'
+
+    # Only try to publish the container image from the root repo; forks don't have permission to do so and will always get failures.
+    - name: Publish container image
+      if: github.repository == 'vmware-tanzu/velero'
+      run: |
+        sudo swapoff -a
+        sudo rm -f /mnt/swapfile
+        docker system prune -a --force
               
-          # Build and push Velero image to docker registry
-          docker login -u ${{ secrets.DOCKER_USER }} -p ${{ secrets.DOCKER_PASSWORD }}
-          ./hack/docker-push.sh
+        # Build and push Velero image to docker registry
+        docker login -u ${{ secrets.DOCKER_USER }} -p ${{ secrets.DOCKER_PASSWORD }}
+        VERSION=$(./hack/docker-push.sh | grep 'VERSION:' | awk -F: '{print $2}' | xargs)
+
+        # Upload Velero image package to GCS
+        source hack/ci/build_util.sh
+        BIN=velero
+        RESTORE_HELPER_BIN=velero-restore-helper
+        GCS_BUCKET=velero-builds
+        VELERO_IMAGE=${BIN}-${VERSION}
+        VELERO_RESTORE_HELPER_IMAGE=${RESTORE_HELPER_BIN}-${VERSION}
+        VELERO_IMAGE_FILE=${VELERO_IMAGE}.tar.gz
+        VELERO_RESTORE_HELPER_IMAGE_FILE=${VELERO_RESTORE_HELPER_IMAGE}.tar.gz
+        VELERO_IMAGE_BACKUP_FILE=${VELERO_IMAGE}-'build.'${GITHUB_RUN_NUMBER}.tar.gz
+        VELERO_RESTORE_HELPER_IMAGE_BACKUP_FILE=${VELERO_RESTORE_HELPER_IMAGE}-'build.'${GITHUB_RUN_NUMBER}.tar.gz
+
+        cp ${VELERO_IMAGE_FILE} ${VELERO_IMAGE_BACKUP_FILE}
+        cp ${VELERO_RESTORE_HELPER_IMAGE_FILE} ${VELERO_RESTORE_HELPER_IMAGE_BACKUP_FILE}
+
+        uploader ${VELERO_IMAGE_FILE} ${GCS_BUCKET}
+        uploader ${VELERO_RESTORE_HELPER_IMAGE_FILE} ${GCS_BUCKET}
+        uploader ${VELERO_IMAGE_BACKUP_FILE} ${GCS_BUCKET}
+        uploader ${VELERO_RESTORE_HELPER_IMAGE_BACKUP_FILE} ${GCS_BUCKET}

.github/workflows/rebase.yml

@@ -9,7 +9,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - name: Checkout the latest code
-      uses: actions/checkout@v5
+      uses: actions/checkout@v4
       with:
         fetch-depth: 0
     - name: Automatic Rebase

.github/workflows/stale-issues.yml

@@ -7,7 +7,7 @@ jobs:
   stale:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@v10.0.0
+      - uses: actions/stale@v9.0.0
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           stale-issue-message: "This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands."
@@ -20,4 +20,4 @@ jobs:
           days-before-pr-close: -1
           # Only issues made after Feb 09 2021.
           start-date: "2021-09-02T00:00:00"
-          exempt-issue-labels: "Epic,Area/CLI,Area/Cloud/AWS,Area/Cloud/Azure,Area/Cloud/GCP,Area/Cloud/vSphere,Area/CSI,Area/Design,Area/Documentation,Area/Plugins,Bug,Enhancement/User,kind/requirement,kind/refactor,kind/tech-debt,limitation,Needs investigation,Needs triage,Needs Product,P0 - Hair on fire,P1 - Important,P2 - Long-term important,P3 - Wouldn't it be nice if...,Product Requirements,Restic - GA,Restic,release-blocker,Security,backlog"
+          exempt-issue-labels: "Epic,Area/CLI,Area/Cloud/AWS,Area/Cloud/Azure,Area/Cloud/GCP,Area/Cloud/vSphere,Area/CSI,Area/Design,Area/Documentation,Area/Plugins,Bug,Enhancement/User,kind/requirement,kind/refactor,kind/tech-debt,limitation,Needs investigation,Needs triage,Needs Product,P0 - Hair on fire,P1 - Important,P2 - Long-term important,P3 - Wouldn't it be nice if...,Product Requirements,Restic - GA,Restic,release-blocker,Security"

.gitignore

@@ -53,13 +53,4 @@ tilt-resources/cloud
 # test generated files
 test/e2e/report.xml
 coverage.out
-__debug_bin*
-debug.test*
-
-# make lint cache
-.cache/
-
-# Go telemetry directory created when container sets HOME to working directory
-# This happens because Makefile uses 'docker run -w /github.com/vmware-tanzu/velero'
-# and Go's os.UserConfigDir() falls back to $HOME/.config when XDG_CONFIG_HOME is unset
-.config/
+__debug_bin*

.golangci.yaml

@@ -6,12 +6,17 @@ run:
   # default concurrency is a available CPU number
   concurrency: 4
 
-  # timeout for analysis, e.g. 30s, 5m, default is 0
+  # timeout for analysis, e.g. 30s, 5m, default is 1m
   timeout: 20m
 
   # exit code when at least one issue was found, default is 1
   issues-exit-code: 1
 
+
+  # default is true. Enables skipping of directories:
+  #   vendor$, third_party$, testdata$, examples$, Godeps$, builtin$
+  skip-dirs-use-default: true
+
   # by default isn't set. If set we pass it to "go list -mod={option}". From "go help modules":
   # If invoked with -mod=readonly, the go command is disallowed from the implicit
   # automatic updating of go.mod described above. Instead, it fails when any changes
@@ -27,403 +32,378 @@ run:
   # If false (default) - golangci-lint acquires file lock on start.
   allow-parallel-runners: false
 
+
 # output configuration options
 output:
+  # colored-line-number|line-number|json|tab|checkstyle|code-climate, default is "colored-line-number"
   formats:
-    text:
+    - format: colored-line-number
       path: stdout
 
-      # print lines of code with issue, default is true
-      print-issued-lines: true
+  # print lines of code with issue, default is true
+  print-issued-lines: true
 
-      # print linter name in the end of issue text, default is true
-      print-linter-name: true
+  # print linter name in the end of issue text, default is true
+  print-linter-name: true
 
-  # Show statistics per linter.      
-  show-stats: false
-
-linters:
-  # all available settings of specific linters
-  settings:
-    depguard:
-      rules:
-        main:
-          deny:
-            # specify an error message to output when a denylisted package is used
-            - pkg: github.com/sirupsen/logrus
-              desc: "logging is allowed only by logutils.Log"
-
-    dogsled:
-      # checks assignments with too many blank identifiers; default is 2
-      max-blank-identifiers: 2
-
-    dupl:
-      # tokens count to trigger issue, 150 by default
-      threshold: 100
-
-    errcheck:
-      # report about not checking of errors in type assertions: `a := b.(MyStruct)`;
-      # default is false: such cases aren't reported by default.
-      check-type-assertions: false
-
-      # report about assignment of errors to blank identifier: `num, _ := strconv.Atoi(numStr)`;
-      # default is false: such cases aren't reported by default.
-      check-blank: false
+  # make issues output unique by line, default is true
+  uniq-by-line: true
 
 
-    exhaustive:
-      # indicates that switch statements are to be considered exhaustive if a
-      # 'default' case is present, even if all enum members aren't listed in the
-      # switch
-      default-signifies-exhaustive: false
+# all available settings of specific linters
+linters-settings:
+  dogsled:
+    # checks assignments with too many blank identifiers; default is 2
+    max-blank-identifiers: 2
+  dupl:
+    # tokens count to trigger issue, 150 by default
+    threshold: 100
+  errcheck:
+    # report about not checking of errors in type assertions: `a := b.(MyStruct)`;
+    # default is false: such cases aren't reported by default.
+    check-type-assertions: false
 
-    funlen:
-      lines: 60
-      statements: 40
+    # report about assignment of errors to blank identifier: `num, _ := strconv.Atoi(numStr)`;
+    # default is false: such cases aren't reported by default.
+    check-blank: false
 
-    gocognit:
-      # minimal code complexity to report, 30 by default (but we recommend 10-20)
-      min-complexity: 10
+    # [deprecated] comma-separated list of pairs of the form pkg:regex
+    # the regex is used to ignore names within pkg. (default "fmt:.*").
+    # see https://github.com/kisielk/errcheck#the-deprecated-method for details
+    # ignore: fmt:.*,io/ioutil:^Read.*
 
-    nestif:
-      # minimal complexity of if statements to report, 5 by default
-      min-complexity: 4
+    # path to a file containing a list of functions to exclude from checking
+    # see https://github.com/kisielk/errcheck#excluding-functions for details
+    # exclude: /path/to/file.txt
+  exhaustive:
+    # indicates that switch statements are to be considered exhaustive if a
+    # 'default' case is present, even if all enum members aren't listed in the
+    # switch
+    default-signifies-exhaustive: false
+  funlen:
+    lines: 60
+    statements: 40
+  gocognit:
+    # minimal code complexity to report, 30 by default (but we recommend 10-20)
+    min-complexity: 10
+  nestif:
+    # minimal complexity of if statements to report, 5 by default
+    min-complexity: 4
+  goconst:
+    # minimal length of string constant, 3 by default
+    min-len: 3
+    # minimal occurrences count to trigger, 3 by default
+    min-occurrences: 5
+  gocritic:
+    # Which checks should be enabled; can't be combined with 'disabled-checks';
+    # See https://go-critic.github.io/overview#checks-overview
+    # To check which checks are enabled run `GL_DEBUG=gocritic golangci-lint run`
+    # By default list of stable checks is used.
+    # enabled-checks:
+    #  - rangeValCopy
 
-    goconst:
-      # minimal length of string constant, 3 by default
-      min-len: 3
-      # minimal occurrences count to trigger, 3 by default
-      min-occurrences: 5
+    # Which checks should be disabled; can't be combined with 'enabled-checks'; default is empty
+    # disabled-checks:
+    #  - regexpMust
 
-    gocritic:
-      # Which checks should be enabled; can't be combined with 'disabled-checks';
-      # See https://go-critic.github.io/overview#checks-overview
-      # To check which checks are enabled run `GL_DEBUG=gocritic golangci-lint run`
-      # By default list of stable checks is used.
-      settings: # settings passed to gocritic
-        captLocal: # must be valid enabled check name
-          paramsOnly: true
+    # Enable multiple checks by tags, run `GL_DEBUG=gocritic golangci-lint run` to see all tags and checks.
+    # Empty list by default. See https://github.com/go-critic/go-critic#usage -> section "Tags".
+    # enabled-tags:
+    #  - performance
+    # disabled-tags:
+    #  - experimental
 
-    gocyclo:
-      # minimal code complexity to report, 30 by default (but we recommend 10-20)
-      min-complexity: 10
+    settings: # settings passed to gocritic
+      captLocal: # must be valid enabled check name
+        paramsOnly: true
+    #  rangeValCopy:
+    #    sizeThreshold: 32
+  gocyclo:
+    # minimal code complexity to report, 30 by default (but we recommend 10-20)
+    min-complexity: 10
+  godot:
+    # check all top-level comments, not only declarations
+    check-all: false
+  godox:
+    # report any comments starting with keywords, this is useful for TODO or FIXME comments that
+    # might be left in the code accidentally and should be resolved before merging
+    keywords: # default keywords are TODO, BUG, and FIXME, these can be overwritten by this setting
+      - NOTE
+      - OPTIMIZE # marks code that should be optimized before merging
+      - HACK # marks hack-arounds that should be removed before merging
+  gofmt:
+    # simplify code: gofmt with `-s` option, true by default
+    simplify: true
+  goimports:
+    # put imports beginning with prefix after 3rd-party packages;
+    # it's a comma-separated list of prefixes
+    local-prefixes: github.com/org/project
+  golint:
+    # minimal confidence for issues, default is 0.8
+    min-confidence: 0.8
+  gomnd:
+    # the list of enabled checks, see https://github.com/tommy-muehle/go-mnd/#checks for description.
+    checks: argument,case,condition,operation,return,assign
+  gomodguard:
+    allowed:
+      modules:                                                        # List of allowed modules
+        # - gopkg.in/yaml.v2
+      domains:                                                        # List of allowed module domains
+        # - golang.org
+    blocked:
+      modules:                                                        # List of blocked modules
+        # - github.com/uudashr/go-module:                             # Blocked module
+        #     recommendations:                                        # Recommended modules that should be used instead (Optional)
+        #       - golang.org/x/mod
+        #     reason: "`mod` is the official go.mod parser library."  # Reason why the recommended module should be used (Optional)
+      versions:                                                       # List of blocked module version constraints
+        # - github.com/mitchellh/go-homedir:                          # Blocked module with version constraint
+        #     version: "< 1.1.0"                                      # Version constraint, see https://github.com/Masterminds/semver#basic-comparisons
+        #     reason: "testing if blocked version constraint works."  # Reason why the version constraint exists. (Optional)
+  govet:
+    # report about shadowed variables
+    # check-shadowing: true
 
-    godot:
-      # check all top-level comments, not only declarations
-      check-all: false
+    # settings per analyzer
+    settings:
+      printf: # analyzer name, run `go tool vet help` to see all analyzers
+        funcs: # run `go tool vet help printf` to see available settings for `printf` analyzer
+          - (github.com/golangci/golangci-lint/pkg/logutils.Log).Infof
+          - (github.com/golangci/golangci-lint/pkg/logutils.Log).Warnf
+          - (github.com/golangci/golangci-lint/pkg/logutils.Log).Errorf
+          - (github.com/golangci/golangci-lint/pkg/logutils.Log).Fatalf
 
-    godox:
-      # report any comments starting with keywords, this is useful for TODO or FIXME comments that
-      # might be left in the code accidentally and should be resolved before merging
-      keywords: # default keywords are TODO, BUG, and FIXME, these can be overwritten by this setting
-        - NOTE
-        - OPTIMIZE # marks code that should be optimized before merging
-        - HACK # marks hack-arounds that should be removed before merging
-
-    gosec:
-      excludes:
-        - G115
-
-    govet:
-      # enable or disable analyzers by name
-      enable:
-        - atomicalign
-      enable-all: false
-      disable:
-        - shadow
-      disable-all: false
-  
-    importas:
-       alias:
-        - alias: appsv1api
-          pkg: k8s.io/api/apps/v1
-        - alias: corev1api
-          pkg: k8s.io/api/core/v1
-        - alias: rbacv1
-          pkg: k8s.io/api/rbac/v1
-        - alias: apierrors
-          pkg: k8s.io/apimachinery/pkg/api/errors
-        - alias: apiextv1
-          pkg: k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1
-        - alias: metav1
-          pkg: k8s.io/apimachinery/pkg/apis/meta/v1
-        - alias: storagev1api
-          pkg: k8s.io/api/storage/v1
-        - alias: batchv1api
-          pkg: k8s.io/api/batch/v1
-
-    lll:
+    # enable or disable analyzers by name
+    enable:
+      - atomicalign
+    enable-all: false
+    disable:
+      - shadow
+    disable-all: false
+  depguard:
+    list-type: blacklist # Velero.io word list : ignore
+    include-go-root: false
+    packages:
+      - github.com/sirupsen/logrus
+    packages-with-error-message:
+      # specify an error message to output when a denylisted package is used
+      - github.com/sirupsen/logrus: "logging is allowed only by logutils.Log"
+  lll:
     # max line length, lines longer will be reported. Default is 120.
     # '\t' is counted as 1 character by default, and can be changed with the tab-width option
-      line-length: 120
-      # tab width in spaces. Default to 1.
-      tab-width: 1
+    line-length: 120
+    # tab width in spaces. Default to 1.
+    tab-width: 1
+  maligned:
+    # print struct with more effective memory layout or not, false by default
+    suggest-new: true
+  misspell:
+    # Correct spellings using locale preferences for US or UK.
+    # Default is to use a neutral variety of English.
+    # Setting locale to US will correct the British spelling of 'colour' to 'color'.
+    locale: US
+    ignore-words:
+      - someword
+  nakedret:
+    # make an issue if func has more lines of code than this setting and it has naked returns; default is 30
+    max-func-lines: 30
+  prealloc:
+    # XXX: we don't recommend using this linter before doing performance profiling.
+    # For most programs usage of prealloc will be a premature optimization.
 
-    misspell:
-      # Correct spellings using locale preferences for US or UK.
-      # Default is to use a neutral variety of English.
-      # Setting locale to US will correct the British spelling of 'colour' to 'color'.
-      locale: US
-      ignore-rules:
-        - someword
-
-    nakedret:
-      # make an issue if func has more lines of code than this setting and it has naked returns; default is 30
-      max-func-lines: 30
-
-    prealloc:
-      # XXX: we don't recommend using this linter before doing performance profiling.
-      # For most programs usage of prealloc will be a premature optimization.
-
-      # Report preallocation suggestions only on simple loops that have no returns/breaks/continues/gotos in them.
-      # True by default.
-      simple: true
-      range-loops: true # Report preallocation suggestions on range loops, true by default
-      for-loops: false # Report preallocation suggestions on for loops, false by default
-
-    nolintlint:
-      # Enable to ensure that nolint directives are all used. Default is true.
-      allow-unused: false
-      # Exclude following linters from requiring an explanation.  Default is [].
-      allow-no-explanation: []
-      # Enable to require an explanation of nonzero length after each nolint directive. Default is false.
-      require-explanation: true
-      # Enable to require nolint directives to mention the specific linter being suppressed. Default is false.
-      require-specific: true
-
-    perfsprint:
-      strconcat: false
-      sprintf1: false
-      errorf: false
-      int-conversion: true
-
-    revive:
-      rules:
-        - name: blank-imports
-          disabled: true
-        - name: context-as-argument
-          disabled: true
-        - name: context-keys-type
-        - name: dot-imports
-          disabled: true
-        - name: early-return
-          disabled: true
-          arguments:
-            - "preserveScope"
-        - name: empty-block
-          disabled: true
-        - name: error-naming
-          disabled: true
-        - name: error-return
-          disabled: true
-        - name: error-strings
-          disabled: true
-        - name: errorf
-          disabled: true
-        - name: increment-decrement
-        - name: indent-error-flow
-          disabled: true
-        - name: range
-        - name: receiver-naming
-          disabled: true
-        - name: redefines-builtin-id
-          disabled: true
-        - name: superfluous-else
-          disabled: true
-          arguments:
-            - "preserveScope"
-        - name: time-naming
-        - name: unexported-return
-          disabled: true
-        - name: unnecessary-stmt
-        - name: unreachable-code
-        - name: unused-parameter
-          disabled: true
-        - name: use-any
-        - name: var-declaration
-        - name: var-naming
-          disabled: true
-
-    rowserrcheck:
-      packages:
-        - github.com/jmoiron/sqlx
-
-    staticcheck:
-      checks:
-        - all
-        - -QF1001 # FIXME
-        - -QF1003 # FIXME
-        - -QF1004 # FIXME
-        - -QF1007 # FIXME
-        - -QF1008 # FIXME
-        - -QF1009 # FIXME
-        - -QF1012 # FIXME
-
-    testifylint:
+    # Report preallocation suggestions only on simple loops that have no returns/breaks/continues/gotos in them.
+    # True by default.
+    simple: true
+    range-loops: true # Report preallocation suggestions on range loops, true by default
+    for-loops: false # Report preallocation suggestions on for loops, false by default
+  nolintlint:
+    # Enable to ensure that nolint directives are all used. Default is true.
+    allow-unused: false
+    # Disable to ensure that nolint directives don't have a leading space. Default is true.
+    allow-leading-space: true
+    # Exclude following linters from requiring an explanation.  Default is [].
+    allow-no-explanation: []
+    # Enable to require an explanation of nonzero length after each nolint directive. Default is false.
+    require-explanation: true
+    # Enable to require nolint directives to mention the specific linter being suppressed. Default is false.
+    require-specific: true
+  revive:
+    rules:
+      - name: unexported-return
+        disabled: true
+    
+  rowserrcheck:
+    packages:
+      - github.com/jmoiron/sqlx
+  testifylint:
       # TODO: enable them all
       disable:
-        - float-compare
+        - bool-compare
+        - compares
+        - error-is-as
+        - error-nil
+        - expected-actual
         - go-require
-      enable-all: true
+        - float-compare
+        - require-error
+        - suite-dont-use-pkg
+        - suite-extra-assert-call
+        - suite-thelper
+      enable:
+        - empty
+        - len
+        - nil-compare
+  testpackage:
+    # regexp pattern to skip files
+    skip-regexp: (export|internal)_test\.go
+  unparam:
+    # Inspect exported functions, default is false. Set to true if no external program/library imports your code.
+    # XXX: if you enable this setting, unparam will report a lot of false-positives in text editors:
+    # if it's called for subdir of a project it can't find external interfaces. All text editor integrations
+    # with golangci-lint call it on a directory with the changed file.
+    check-exported: false
+  unused:
+    # treat code as a program (not a library) and report unused exported identifiers; default is false.
+    # XXX: if you enable this setting, unused will report a lot of false-positives in text editors:
+    # if it's called for subdir of a project it can't find funcs usages. All text editor integrations
+    # with golangci-lint call it on a directory with the changed file.
+    check-exported: false
+  whitespace:
+    multi-if: false   # Enforces newlines (or comments) after every multi-line if statement
+    multi-func: false # Enforces newlines (or comments) after every multi-line function signature
+  wsl:
+    # If true append is only allowed to be cuddled if appending value is
+    # matching variables, fields or types on line above. Default is true.
+    strict-append: true
+    # Allow calls and assignments to be cuddled as long as the lines have any
+    # matching variables, fields or types. Default is true.
+    allow-assign-and-call: true
+    # Allow multiline assignments to be cuddled. Default is true.
+    allow-multiline-assign: true
+    # Allow declarations (var) to be cuddled.
+    allow-cuddle-declarations: false
+    # Allow trailing comments in ending of blocks
+    allow-trailing-comment: false
+    # Force newlines in end of case at this limit (0 = never).
+    force-case-trailing-whitespace: 0
+    # Force cuddling of err checks with err var assignment
+    force-err-cuddling: false
+    # Allow leading comments to be separated with empty liens
+    allow-separated-leading-comment: false
 
-    testpackage:
-      # regexp pattern to skip files
-      skip-regexp: (export|internal)_test\.go
-    unparam:
-      # Inspect exported functions, default is false. Set to true if no external program/library imports your code.
-      # XXX: if you enable this setting, unparam will report a lot of false-positives in text editors:
-      # if it's called for subdir of a project it can't find external interfaces. All text editor integrations
-      # with golangci-lint call it on a directory with the changed file.
-      check-exported: false
-
-    usetesting:
-      os-setenv: false
-
-    whitespace:
-      multi-if: false # Enforces newlines (or comments) after every multi-line if statement
-      multi-func: false # Enforces newlines (or comments) after every multi-line function signature
-
-    wsl:
-      # If true append is only allowed to be cuddled if appending value is
-      # matching variables, fields or types on line above. Default is true.
-      strict-append: true
-      # Allow calls and assignments to be cuddled as long as the lines have any
-      # matching variables, fields or types. Default is true.
-      allow-assign-and-call: true
-      # Allow multiline assignments to be cuddled. Default is true.
-      allow-multiline-assign: true
-      # Allow declarations (var) to be cuddled.
-      allow-cuddle-declarations: false
-      # Allow trailing comments in ending of blocks
-      allow-trailing-comment: false
-      # Force newlines in end of case at this limit (0 = never).
-      force-case-trailing-whitespace: 0
-      # Force cuddling of err checks with err var assignment
-      force-err-cuddling: false
-      # Allow leading comments to be separated with empty lines
-      allow-separated-leading-comment: false
-
-  default: none
+linters:
+  disable-all: true
   enable:
     - asasalint
     - asciicheck
     - bidichk
     - bodyclose
-    - copyloopvar
     - dogsled
-    - dupword
     - durationcheck
+    - dupword
     - errcheck
+    - exportloopref
     - errchkjson
-    - exptostd
-    - ginkgolinter
     - goconst
+    - gofmt
     - goheader
+    - goimports
     - goprintffuncname
     - gosec
+    - gosimple
     - govet
+    - ginkgolinter
     - importas
     - ineffassign
     - misspell
     - nakedret
+    - nosprintfhostport
     - nilerr
     - noctx
     - nolintlint
-    - nosprintfhostport
-    - perfsprint
     - revive
     - staticcheck
+    - stylecheck
     - testifylint
-    - thelper
+    - typecheck
     - unconvert
     - unparam
     - unused
     - usestdlibvars
-    - usetesting
     - whitespace
+  fast: false
 
-  exclusions:
-    # which dirs to skip: issues from them won't be reported;
-    # can use regexp here: generated.*, regexp is applied on full path;
-    # default value is empty list, but default dirs are skipped independently
-    # from this option's value (see skip-dirs-use-default).
-    # "/" will be replaced by current OS file path separator to properly work
-    # on Windows.
-    paths:
-      - pkg/plugin/generated/*
-      - third_party
-
-    rules:
-      - linters:
-          - staticcheck
-        text: "DefaultVolumesToRestic" # No need to report deprecate for DefaultVolumesToRestic.
-      - path: ".*_test.go$"
-        linters:
-          - errcheck
-          - goconst
-          - gosec
-          - govet
-          - staticcheck
-          - unparam
-          - unused
-      - path: test/
-        linters:
-          - errcheck
-          - goconst
-          - gosec
-          - nilerr
-          - staticcheck
-          - unparam
-          - unused
-      - path: ".*data_upload_controller_test.go$"
-        linters:
-          - dupword
-        text: "type"
-      - path: ".*config_test.go$"
-        linters:
-          - dupword
-        text: "bucket"
-
-    generated: lax
-    presets:
-      - comments
-      - common-false-positives
-      - legacy
-      - std-error-handling
 
 issues:
+  exclude-rules:
+    - linters:
+        - staticcheck
+      text: "github.com/golang/protobuf/proto" # grpc-go still uses github.com/golang/protobuf/proto.
+    - linters:
+        - staticcheck
+      text: "DefaultVolumesToRestic" # No need to report deprecate for DefaultVolumesToRestic.
+    - path: ".*_test.go$"
+      linters:
+        - dupword
+        - errcheck
+        - goconst
+        - gosec
+        - govet
+        - staticcheck
+        - stylecheck
+        - unconvert
+        - unparam
+        - unused
+    - path: test/
+      linters:
+        - dupword
+        - errcheck
+        - goconst
+        - gosec
+        - gosimple
+        - nilerr
+        - staticcheck
+        - stylecheck
+        - unconvert
+        - unparam
+        - unused
+
+  # The list of ids of default excludes to include or disable. By default it's empty.
+  include:
+    - EXC0002 # disable excluding of issues about comments from golint
+
   # Maximum issues count per one linter. Set to 0 to disable. Default is 50.
   max-issues-per-linter: 0
 
   # Maximum count of issues with the same text. Set to 0 to disable. Default is 3.
   max-same-issues: 0
 
-  # make issues output unique by line, default is true
-  uniq-by-line: true
+  # Show only new issues created after git revision `REV`
+  # new-from-rev: origin/main
 
-# This file contains all available configuration options
-# with their default values.
-formatters:
-  enable:
-    - gofmt
-    - goimports
-
-  exclusions:
-    generated: lax
-    paths:
-      - pkg/plugin/generated/*
-      - third_party
-
-  settings:
-    gofmt:
-      # simplify code: gofmt with `-s` option, true by default
-      simplify: true
-    goimports:
-      local-prefixes:
-        - github.com/vmware-tanzu/velero
+  # which dirs to skip: issues from them won't be reported;
+  # can use regexp here: generated.*, regexp is applied on full path;
+  # default value is empty list, but default dirs are skipped independently
+  # from this option's value (see skip-dirs-use-default).
+  # "/" will be replaced by current OS file path separator to properly work
+  # on Windows.
+  exclude-dirs:
+    - pkg/plugin/generated/*
 
 severity:
-  default: error
+  # Default value is empty string.
+  # Set the default severity for issues. If severity rules are defined and the issues 
+  # do not match or no severity is provided to the rule this will be the default 
+  # severity applied. Severities should match the supported severity names of the 
+  # selected out format.
+  # - Code climate: https://docs.codeclimate.com/docs/issues#issue-severity
+  # -   Checkstyle: https://checkstyle.sourceforge.io/property_types.html#severity
+  # -       Github: https://help.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-an-error-message
+  default-severity: error
+
+  # The default value is false. 
+  # If set to true severity-rules regular expressions become case sensitive.
+  case-sensitive: false
 
   # Default value is empty list.
   # When a list of severity rules are provided, severity information will be added to lint
@@ -432,7 +412,5 @@ severity:
   # Only affects out formats that support setting severity information.
   rules:
     - linters:
-        - dupl
+      - dupl
       severity: info
-
-version: "2"

.goreleaser.yml

@@ -26,23 +26,18 @@ builds:
       - arm
       - arm64
       - ppc64le
-      - s390x
     ignore:
       # don't build arm for darwin and arm/arm64 for windows
       - goos: darwin
         goarch: arm
       - goos: darwin
         goarch: ppc64le
-      - goos: darwin
-        goarch: s390x
       - goos: windows
         goarch: arm
       - goos: windows
         goarch: arm64
       - goos: windows
         goarch: ppc64le
-      - goos: windows
-        goarch: s390x
     ldflags:
       - -X "github.com/vmware-tanzu/velero/pkg/buildinfo.Version={{ .Tag }}" -X "github.com/vmware-tanzu/velero/pkg/buildinfo.GitSHA={{ .FullCommit }}" -X "github.com/vmware-tanzu/velero/pkg/buildinfo.GitTreeState={{ .Env.GIT_TREE_STATE }}" -X "github.com/vmware-tanzu/velero/pkg/buildinfo.ImageRegistry={{ .Env.REGISTRY }}"
 archives:
@@ -51,6 +46,9 @@ archives:
     files:
       - LICENSE
       - examples/**/*
+    # Add the setting to resolve the DEPRECATED warning. Actually, Velero's case is not affected by the rlcp behavior change.
+    # https://github.com/orgs/goreleaser/discussions/3659#discussioncomment-4587257
+    rlcp: true 
 checksum:
   name_template: 'CHECKSUM'
 release:
@@ -65,4 +63,4 @@ git:
   # tags if there are more than one tag in the same commit.
   #
   # Default: `-version:refname`
-  tag_sort: -version:creatordate
+  tag_sort: -version:creatordate

CHANGELOG.md

@@ -1,8 +1,7 @@
 ## Current release:
-  * [CHANGELOG-1.15.md][25]
+  * [CHANGELOG-1.14.md][24]
 
 ## Older releases:
-  * [CHANGELOG-1.14.md][24]
   * [CHANGELOG-1.13.md][23]
   * [CHANGELOG-1.12.md][22]
   * [CHANGELOG-1.11.md][21]
@@ -28,7 +27,6 @@
   * [CHANGELOG-0.3.md][1]
 
 
-[25]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.15.md
 [24]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.14.md
 [23]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.13.md
 [22]: https://github.com/vmware-tanzu/velero/blob/main/changelogs/CHANGELOG-1.12.md

Dockerfile

@@ -13,7 +13,7 @@
 # limitations under the License.
 
 # Velero binary build section
-FROM --platform=$BUILDPLATFORM golang:1.24-bookworm AS velero-builder
+FROM --platform=$BUILDPLATFORM golang:1.22.6-bookworm as velero-builder
 
 ARG GOPROXY
 ARG BIN
@@ -42,16 +42,13 @@ RUN mkdir -p /output/usr/bin && \
     export GOARM=$( echo "${GOARM}" | cut -c2-) && \
     go build -o /output/${BIN} \
     -ldflags "${LDFLAGS}" ${PKG}/cmd/${BIN} && \
-    go build -o /output/velero-restore-helper \
-    -ldflags "${LDFLAGS}" ${PKG}/cmd/velero-restore-helper && \
     go build -o /output/velero-helper \
     -ldflags "${LDFLAGS}" ${PKG}/cmd/velero-helper && \
     go clean -modcache -cache
 
 # Restic binary build section
-FROM --platform=$BUILDPLATFORM golang:1.24-bookworm AS restic-builder
+FROM --platform=$BUILDPLATFORM golang:1.22.6-bookworm as restic-builder
 
-ARG GOPROXY
 ARG BIN
 ARG TARGETOS
 ARG TARGETARCH
@@ -73,7 +70,7 @@ RUN mkdir -p /output/usr/bin && \
     go clean -modcache -cache
 
 # Velero image packing section
-FROM paketobuildpacks/run-jammy-tiny:latest
+FROM paketobuildpacks/run-jammy-tiny:0.2.46
 
 LABEL maintainer="Xun Jiang <jxun@vmware.com>"
 

Dockerfile-Windows

@@ -1,57 +0,0 @@
-# Copyright the Velero contributors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-ARG OS_VERSION=1809
-
-# Velero binary build section
-FROM --platform=$BUILDPLATFORM golang:1.24-bookworm AS velero-builder
-
-ARG GOPROXY
-ARG BIN
-ARG PKG
-ARG VERSION
-ARG REGISTRY
-ARG GIT_SHA
-ARG GIT_TREE_STATE
-ARG TARGETOS
-ARG TARGETARCH
-ARG TARGETVARIANT
-
-ENV CGO_ENABLED=0 \
-    GO111MODULE=on \
-    GOPROXY=${GOPROXY} \
-    GOOS=${TARGETOS} \
-    GOARCH=${TARGETARCH} \
-    GOARM=${TARGETVARIANT} \
-    LDFLAGS="-X ${PKG}/pkg/buildinfo.Version=${VERSION} -X ${PKG}/pkg/buildinfo.GitSHA=${GIT_SHA} -X ${PKG}/pkg/buildinfo.GitTreeState=${GIT_TREE_STATE} -X ${PKG}/pkg/buildinfo.ImageRegistry=${REGISTRY}"
-
-WORKDIR /go/src/github.com/vmware-tanzu/velero
-
-COPY . /go/src/github.com/vmware-tanzu/velero
-
-RUN mkdir -p /output/usr/bin && \
-    export GOARM=$( echo "${GOARM}" | cut -c2-) && \
-    go build -o /output/${BIN}.exe \
-    -ldflags "${LDFLAGS}" ${PKG}/cmd/${BIN} && \
-    go build -o /output/velero-restore-helper.exe \
-    -ldflags "${LDFLAGS}" ${PKG}/cmd/velero-restore-helper && \    
-    go build -o /output/velero-helper.exe \
-    -ldflags "${LDFLAGS}" ${PKG}/cmd/velero-helper && \
-    go clean -modcache -cache
-
-# Velero image packing section
-FROM mcr.microsoft.com/windows/nanoserver:${OS_VERSION}
-COPY --from=velero-builder /output /
-
-USER ContainerUser

GOVERNANCE.md

@@ -107,29 +107,6 @@ Lazy consensus does _not_ apply to the process of:
 
 * Removal of maintainers from Velero
 
-## Deprecation Policy
-
-### Deprecation Process
-
-Any contributor may introduce a request to deprecate a feature or an option of a feature by opening a feature request issue in the vmware-tanzu/velero GitHub project. The issue should describe why the feature is no longer needed or has become detrimental to Velero, as well as whether and how it has been superseded. The submitter should give as much detail as possible.
-
-Once the issue is filed, a one-month discussion period begins. Discussions take place within the issue itself as well as in the community meetings. The person who opens the issue, or a maintainer, should add the date and time marking the end of the discussion period in a comment on the issue as soon as possible after it is opened. A decision on the issue needs to be made within this one-month period.
-
-The feature will be deprecated by a supermajority vote of 50% plus one of the project maintainers at the time of the vote tallying, which is 72 hours after the end of the community meeting that is the end of the comment period. (Maintainers are permitted to vote in advance of the deadline, but should hold their votes until as close as possible to hear all possible discussion.) Votes will be tallied in comments on the issue. 
-
-Non-maintainers may add non-binding votes in comments to the issue as well; these are opinions to be taken into consideration by maintainers, but they do not count as votes. 
-
-If the vote passes, the deprecation window takes effect in the subsequent release, and the removal follows the schedule. 
-
-### Schedule
-If depreciation proposal passes by supermajority votes, the feature is deprecated in the next minor release and the feature can be removed completely after two minor version or equivalent major version e.g., if feature gets deprecated in Nth minor version, then feature can be removed after N+2 minor version or its equivalent if the major version number changes.
-
-### Deprecation Window
-
-The deprecation window is the period from the release in which the deprecation takes effect through the release in which the feature is removed. During this period, only critical security vulnerabilities and catastrophic bugs should be fixed.
-
-**Note:** If a backup relies on a deprecated feature, then backups made with the last Velero release before this feature is removed must still be restorable in version `n+2`. For instance, something like restic feature support, that might mean that restic is removed from the list of supported uploader types in version `n` but the underlying implementation required to restore from a restic backup won't be removed until release `n+2`.
-
 ## Updating Governance
 
 All substantive changes in Governance require a supermajority agreement by all maintainers.

MAINTAINERS.md

@@ -10,10 +10,10 @@
 | Daniel Jiang        | [reasonerjt](https://github.com/reasonerjt)                   | [VMware](https://www.github.com/vmware/)         |
 | Wenkai Yin          | [ywk253100](https://github.com/ywk253100)                     | [VMware](https://www.github.com/vmware/)         |
 | Xun Jiang           | [blackpiglet](https://github.com/blackpiglet)                 | [VMware](https://www.github.com/vmware/)         |
+| Ming Qiu            | [qiuming-best](https://github.com/qiuming-best)               | [VMware](https://www.github.com/vmware/)         |
 | Shubham Pampattiwar | [shubham-pampattiwar](https://github.com/shubham-pampattiwar) | [OpenShift](https://github.com/openshift)        |
 | Yonghui Li          | [Lyndon-Li](https://github.com/Lyndon-Li)                     | [VMware](https://www.github.com/vmware/)         |
 | Anshul Ahuja        | [anshulahuja98](https://github.com/anshulahuja98)             | [Microsoft Azure](https://www.github.com/azure/) |
-| Tiger Kaovilai      | [kaovilai](https://github.com/kaovilai)                       | [OpenShift](https://github.com/openshift)        |
 
 ## Emeritus Maintainers
 * Adnan Abdulhussein ([prydonius](https://github.com/prydonius))
@@ -26,8 +26,7 @@
 * Bridget McErlean ([zubron](https://github.com/zubron))
 * JenTing Hsiao ([jenting](https://github.com/jenting))
 * Dave Smith-Uchida ([dsu-igeek](https://github.com/dsu-igeek))
-* Ming Qiu ([qiuming-best](https://github.com/qiuming-best))
-
+  
 ## Velero Contributors & Stakeholders
 
 | Feature Area           |                                         Lead                                         |

Makefile

@@ -22,26 +22,15 @@ PKG := github.com/vmware-tanzu/velero
 
 # Where to push the docker image.
 REGISTRY ?= velero
-# In order to push images to an insecure registry, follow the two steps:
-#   1. Set "INSECURE_REGISTRY=true" 
-#   2. Provide your own buildx builder instance by setting "BUILDX_INSTANCE=your-own-builder-instance"
-#      The builder can be created with the following command:
-#        cat << EOF > buildkitd.toml
-#        [registry."insecure-registry-ip:port"]
-#        http = true
-#        insecure = true
-#        EOF
-#        docker buildx create --name=velero-builder --driver=docker-container --bootstrap --use --config ./buildkitd.toml
-#      Refer to https://github.com/docker/buildx/issues/1370#issuecomment-1288516840 for more details
-INSECURE_REGISTRY ?= false
+GCR_REGISTRY ?= gcr.io/velero-gcp
 
 # Image name
 IMAGE ?= $(REGISTRY)/$(BIN)
+GCR_IMAGE ?= $(GCR_REGISTRY)/$(BIN)
 
 # We allow the Dockerfile to be configurable to enable the use of custom Dockerfiles
 # that pull base images from different registries.
 VELERO_DOCKERFILE ?= Dockerfile
-VELERO_DOCKERFILE_WINDOWS ?= Dockerfile-Windows
 BUILDER_IMAGE_DOCKERFILE ?= hack/build-image/Dockerfile
 
 # Calculate the realpath of the build-image Dockerfile as we `cd` into the hack/build
@@ -65,7 +54,7 @@ endif
 BUILDER_IMAGE := $(REGISTRY)/build-image:$(BUILDER_IMAGE_TAG)
 BUILDER_IMAGE_CACHED := $(shell docker images -q ${BUILDER_IMAGE} 2>/dev/null )
 
-HUGO_IMAGE := ghcr.io/gohugoio/hugo
+HUGO_IMAGE := hugo-builder
 
 # Which architecture to build - see $(ALL_ARCH) for options.
 # if the 'local' rule is being run, detect the ARCH from 'go env'
@@ -79,8 +68,10 @@ TAG_LATEST ?= false
 
 ifeq ($(TAG_LATEST), true)
 	IMAGE_TAGS ?= $(IMAGE):$(VERSION) $(IMAGE):latest
+	GCR_IMAGE_TAGS ?= $(GCR_IMAGE):$(VERSION) $(GCR_IMAGE):latest
 else
 	IMAGE_TAGS ?= $(IMAGE):$(VERSION)
+	GCR_IMAGE_TAGS ?= $(GCR_IMAGE):$(VERSION)
 endif
 
 # check buildx is enabled only if docker is in path
@@ -103,32 +94,13 @@ define BUILDX_ERROR
 buildx not enabled, refusing to run this recipe
 see: https://velero.io/docs/main/build-from-source/#making-images-and-updating-velero for more info
 endef
-# comma cannot be escaped and can only be used in Make function arguments by putting into variable
-comma=,
+
 # The version of restic binary to be downloaded
 RESTIC_VERSION ?= 0.15.0
 
-CLI_PLATFORMS ?= linux-amd64 linux-arm linux-arm64 darwin-amd64 darwin-arm64 windows-amd64 linux-ppc64le linux-s390x
-BUILD_OUTPUT_TYPE ?= docker
-BUILD_OS ?= linux
-BUILD_ARCH ?= amd64
-BUILD_WINDOWS_VERSION ?= ltsc2022
-
-ifeq ($(BUILD_OUTPUT_TYPE), docker)
-	ALL_OS = linux
-	ALL_ARCH.linux = $(word 2, $(subst -, ,$(shell go env GOOS)-$(shell go env GOARCH)))
-else
-	ALL_OS = $(subst $(comma), ,$(BUILD_OS))
-	ALL_ARCH.linux = $(subst $(comma), ,$(BUILD_ARCH))
-endif
-
-ALL_ARCH.windows = $(if $(filter windows,$(ALL_OS)),amd64,)
-ALL_OSVERSIONS.windows = $(if $(filter windows,$(ALL_OS)),$(BUILD_WINDOWS_VERSION),)
-ALL_OS_ARCH.linux =  $(foreach os, $(filter linux,$(ALL_OS)), $(foreach arch, ${ALL_ARCH.linux}, ${os}-$(arch)))
-ALL_OS_ARCH.windows = $(foreach os, $(filter windows,$(ALL_OS)), $(foreach arch, $(ALL_ARCH.windows), $(foreach osversion, ${ALL_OSVERSIONS.windows}, ${os}-${osversion}-${arch})))
-ALL_OS_ARCH = $(ALL_OS_ARCH.linux)$(ALL_OS_ARCH.windows)
-
-ALL_IMAGE_TAGS = $(IMAGE_TAGS)
+CLI_PLATFORMS ?= linux-amd64 linux-arm linux-arm64 darwin-amd64 darwin-arm64 windows-amd64 linux-ppc64le
+BUILDX_PLATFORMS ?= $(subst -,/,$(ARCH))
+BUILDX_OUTPUT_TYPE ?= docker
 
 # set git sha and tree state
 GIT_SHA = $(shell git rev-parse HEAD)
@@ -152,14 +124,17 @@ GOBIN=$$(pwd)/.go/bin
 # If you want to build all containers, see the 'all-containers' rule.
 all:
 	@$(MAKE) build
+	@$(MAKE) build BIN=velero-restore-helper
 
 build-%:
 	@$(MAKE) --no-print-directory ARCH=$* build
+	@$(MAKE) --no-print-directory ARCH=$* build BIN=velero-restore-helper
 
 all-build: $(addprefix build-, $(CLI_PLATFORMS))
 
 all-containers:
 	@$(MAKE) --no-print-directory container
+	@$(MAKE) --no-print-directory container BIN=velero-restore-helper
 
 local: build-dirs
 # Add DEBUG=1 to enable debug locally
@@ -221,38 +196,11 @@ container:
 ifneq ($(BUILDX_ENABLED), true)
 	$(error $(BUILDX_ERROR))
 endif
-
-ifeq ($(BUILDX_INSTANCE),)
-	@echo creating a buildx instance
-	-docker buildx rm velero-builder || true
-	@docker buildx create --use --name=velero-builder
-else
-	@echo using a specified buildx instance $(BUILDX_INSTANCE)
-	@docker buildx use $(BUILDX_INSTANCE)
-endif
-
-	@mkdir -p _output
-
-	@for osarch in $(ALL_OS_ARCH); do \
-		$(MAKE) container-$${osarch}; \
-	done
-
-ifeq ($(BUILD_OUTPUT_TYPE), registry)
-	@for tag in $(ALL_IMAGE_TAGS); do \
-		IMAGE_TAG=$${tag} $(MAKE) push-manifest; \
-	done
-endif
-
-container-linux-%:
-	@BUILDX_ARCH=$* $(MAKE) container-linux
-
-container-linux:
-	@echo "building container: $(IMAGE):$(VERSION)-linux-$(BUILDX_ARCH)"
-
 	@docker buildx build --pull \
-	--output="type=$(BUILD_OUTPUT_TYPE)$(if $(findstring tar, $(BUILD_OUTPUT_TYPE)),$(comma)dest=_output/$(BIN)-$(VERSION)-linux-$(BUILDX_ARCH).tar,)" \
-	--platform="linux/$(BUILDX_ARCH)" \
-	$(addprefix -t , $(addsuffix "-linux-$(BUILDX_ARCH)",$(ALL_IMAGE_TAGS))) \
+	--output=type=$(BUILDX_OUTPUT_TYPE) \
+	--platform $(BUILDX_PLATFORMS) \
+	$(addprefix -t , $(IMAGE_TAGS)) \
+	$(addprefix -t , $(GCR_IMAGE_TAGS)) \
 	--build-arg=GOPROXY=$(GOPROXY) \
 	--build-arg=PKG=$(PKG) \
 	--build-arg=BIN=$(BIN) \
@@ -261,54 +209,14 @@ container-linux:
 	--build-arg=GIT_TREE_STATE=$(GIT_TREE_STATE) \
 	--build-arg=REGISTRY=$(REGISTRY) \
 	--build-arg=RESTIC_VERSION=$(RESTIC_VERSION) \
-	--provenance=false \
-	--sbom=false \
 	-f $(VELERO_DOCKERFILE) .
-
-	@echo "built container: $(IMAGE):$(VERSION)-linux-$(BUILDX_ARCH)"
-
-container-windows-%:
-	@BUILDX_OSVERSION=$(firstword $(subst -, ,$*)) BUILDX_ARCH=$(lastword $(subst -, ,$*)) $(MAKE) container-windows
-
-container-windows:
-	@echo "building container: $(IMAGE):$(VERSION)-windows-$(BUILDX_OSVERSION)-$(BUILDX_ARCH)"
-
-	@docker buildx build --pull \
-	--output="type=$(BUILD_OUTPUT_TYPE)$(if $(findstring tar, $(BUILD_OUTPUT_TYPE)),$(comma)dest=_output/$(BIN)-$(VERSION)-windows-$(BUILDX_OSVERSION)-$(BUILDX_ARCH).tar,)" \
-	--platform="windows/$(BUILDX_ARCH)" \
-	$(addprefix -t , $(addsuffix "-windows-$(BUILDX_OSVERSION)-$(BUILDX_ARCH)",$(ALL_IMAGE_TAGS))) \
-	--build-arg=GOPROXY=$(GOPROXY) \
-	--build-arg=PKG=$(PKG) \
-	--build-arg=BIN=$(BIN) \
-	--build-arg=VERSION=$(VERSION) \
-	--build-arg=OS_VERSION=$(BUILDX_OSVERSION) \
-	--build-arg=GIT_SHA=$(GIT_SHA) \
-    --build-arg=GIT_TREE_STATE=$(GIT_TREE_STATE) \
-	--build-arg=REGISTRY=$(REGISTRY) \
-	--provenance=false \
-	--sbom=false \
-	-f $(VELERO_DOCKERFILE_WINDOWS) .
-
-	@echo "built container: $(IMAGE):$(VERSION)-windows-$(BUILDX_OSVERSION)-$(BUILDX_ARCH)"
-
-push-manifest:
-	@echo "building manifest: $(IMAGE_TAG) for $(foreach osarch, $(ALL_OS_ARCH), $(IMAGE_TAG)-${osarch})"
-	@docker manifest create --amend --insecure=$(INSECURE_REGISTRY) $(IMAGE_TAG) $(foreach osarch, $(ALL_OS_ARCH), $(IMAGE_TAG)-${osarch})
-
-	@set -x; \
-	for arch in $(ALL_ARCH.windows); do \
-		for osversion in $(ALL_OSVERSIONS.windows); do \
-			BASEIMAGE=mcr.microsoft.com/windows/nanoserver:$${osversion}; \
-			full_version=`docker manifest inspect --insecure=$(INSECURE_REGISTRY) $${BASEIMAGE} | jq -r '.manifests[0].platform["os.version"]'`; \
-			docker manifest annotate --os windows --arch $${arch} --os-version $${full_version} $(IMAGE_TAG) $(IMAGE_TAG)-windows-$${osversion}-$${arch}; \
-		done; \
-	done
-
-	@echo "pushing manifest $(IMAGE_TAG)"
-	@docker manifest push --purge --insecure=$(INSECURE_REGISTRY) $(IMAGE_TAG)
-
-	@echo "pushed manifest $(IMAGE_TAG):"
-	@docker manifest inspect --insecure=$(INSECURE_REGISTRY) $(IMAGE_TAG)
+	@echo "container: $(IMAGE):$(VERSION)"
+ifeq ($(BUILDX_OUTPUT_TYPE)_$(REGISTRY), registry_velero)
+	docker pull $(IMAGE):$(VERSION)
+	rm -f $(BIN)-$(VERSION).tar
+	docker save $(IMAGE):$(VERSION) -o $(BIN)-$(VERSION).tar
+	gzip -f $(BIN)-$(VERSION).tar
+endif
 
 SKIP_TESTS ?=
 test: build-dirs
@@ -451,7 +359,7 @@ release:
 serve-docs: build-image-hugo
 	docker run \
 	--rm \
-	-v "$$(pwd)/site:/project" \
+	-v "$$(pwd)/site:/srv/hugo" \
 	-it -p 1313:1313 \
 	$(HUGO_IMAGE) \
 	server --bind=0.0.0.0 --enableGitInfo=false
@@ -469,22 +377,4 @@ test-perf: local
 	$(MAKE) -e VERSION=$(VERSION) -C test/ run-perf
 
 go-generate:
-	go generate ./pkg/...
-
-# requires an authenticated gh cli
-# gh: https://cli.github.com/
-# First create a PR
-# gh pr create --title 'Title name' --body 'PR body'
-# by default uses PR title as changelog body but can be overwritten like so
-# make new-changelog CHANGELOG_BODY="Changes you have made"
-new-changelog: GH_LOGIN ?= $(shell gh pr view --json author --jq .author.login 2> /dev/null)
-new-changelog: GH_PR_NUMBER ?= $(shell gh pr view --json number --jq .number 2> /dev/null)
-new-changelog: CHANGELOG_BODY ?= '$(shell gh pr view --json title --jq .title)'
-new-changelog:
-	@if [ "$(GH_LOGIN)" = "" ]; then \
-		echo "branch does not have PR or cli not logged in, try 'gh auth login' or 'gh pr create'"; \
-		exit 1; \
-	fi
-	@mkdir -p ./changelogs/unreleased/ && \
-	echo $(CHANGELOG_BODY) > ./changelogs/unreleased/$(GH_PR_NUMBER)-$(GH_LOGIN) && \
-	echo \"$(CHANGELOG_BODY)\" added to "./changelogs/unreleased/$(GH_PR_NUMBER)-$(GH_LOGIN)"
+	go generate ./pkg/...

README.md

@@ -42,13 +42,11 @@ The following is a list of the supported Kubernetes versions for each Velero ver
 
 | Velero version | Expected Kubernetes version compatibility | Tested on Kubernetes version        |
 |----------------|-------------------------------------------|-------------------------------------|
-| 1.17           | 1.18-latest                               | 1.31.7, 1.32.3, 1.33.1, and 1.34.0          |
-| 1.16           | 1.18-latest                               | 1.31.4, 1.32.3, and 1.33.0          |
-| 1.15           | 1.18-latest                               | 1.28.8, 1.29.8, 1.30.4 and 1.31.1   |
 | 1.14           | 1.18-latest                               | 1.27.9, 1.28.9, and 1.29.4          |
 | 1.13           | 1.18-latest                               | 1.26.5, 1.27.3, 1.27.8, and 1.28.3  |
 | 1.12           | 1.18-latest                               | 1.25.7, 1.26.5, 1.26.7, and 1.27.3  |
 | 1.11           | 1.18-latest                               | 1.23.10, 1.24.9, 1.25.5, and 1.26.1 |
+| 1.10           | 1.18-latest                               | 1.22.5, 1.23.8, 1.24.6 and 1.25.1   |
 
 Velero supports IPv4, IPv6, and dual stack environments. Support for this was tested against Velero v1.8.
 

SECURITY.md

@@ -12,13 +12,13 @@ The Velero project maintains the following [governance document](https://github.
 
 Security is of the highest importance and all security vulnerabilities or suspected security vulnerabilities should be reported to Velero privately, to minimize attacks against current users of Velero before they are fixed. Vulnerabilities will be investigated and patched on the next patch (or minor) release as soon as possible. This information could be kept entirely internal to the project.  
 
-If you know of a publicly disclosed security vulnerability for Velero, please **IMMEDIATELY** contact the Security Team (velero-security.pdl@broadcom.com).
+If you know of a publicly disclosed security vulnerability for Velero, please **IMMEDIATELY** contact the VMware Security Team (security@vmware.com).
 
  
 
 **IMPORTANT: Do not file public issues on GitHub for security vulnerabilities**
 
-To report a vulnerability or a security-related issue, please contact the email address with the details of the vulnerability. The email will be fielded by the Security Team and then shared with the Velero maintainers who have committer and release permissions. Emails will be addressed within 3 business days, including a detailed plan to investigate the issue and any potential workarounds to perform in the meantime. Do not report non-security-impacting bugs through this channel. Use [GitHub issues](https://github.com/vmware-tanzu/velero/issues/new/choose) instead.
+To report a vulnerability or a security-related issue, please contact the VMware email address with the details of the vulnerability. The email will be fielded by the VMware Security Team and then shared with the Velero maintainers who have committer and release permissions. Emails will be addressed within 3 business days, including a detailed plan to investigate the issue and any potential workarounds to perform in the meantime. Do not report non-security-impacting bugs through this channel. Use [GitHub issues](https://github.com/vmware-tanzu/velero/issues/new/choose) instead.
 
 
 ## Proposed Email Content
@@ -29,7 +29,7 @@ Provide a descriptive subject line and in the body of the email include the foll
 
 *   Basic identity information, such as your name and your affiliation or company.
 *   Detailed steps to reproduce the vulnerability  (POC scripts, screenshots, and logs are all helpful to us).
-*   Description of the effects of the vulnerability on Velero and the related hardware and software configurations, so that the Security Team can reproduce it.
+*   Description of the effects of the vulnerability on Velero and the related hardware and software configurations, so that the VMware Security Team can reproduce it.
 *   How the vulnerability affects Velero usage and an estimation of the attack surface, if there is one.
 *   List other projects or dependencies that were used in conjunction with Velero to produce the vulnerability.
 
@@ -49,7 +49,7 @@ Provide a descriptive subject line and in the body of the email include the foll
 
 ## Patch, Release, and Disclosure
 
-The Security Team will respond to vulnerability reports as follows:
+The VMware Security Team will respond to vulnerability reports as follows:
 
  
 
@@ -62,7 +62,7 @@ The Security Team will respond to vulnerability reports as follows:
 5. The Security Team will also create a [CVSS](https://www.first.org/cvss/specification-document) using the [CVSS Calculator](https://www.first.org/cvss/calculator/3.0). The Security Team makes the final call on the calculated CVSS; it is better to move quickly than making the CVSS perfect. Issues may also be reported to [Mitre](https://cve.mitre.org/) using this [scoring calculator](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator). The CVE will initially be set to private.
 6. The Security Team will work on fixing the vulnerability and perform internal testing before preparing to roll out the fix.
 7. The Security Team will provide early disclosure of the vulnerability by emailing the [Velero Distributors](https://groups.google.com/u/1/g/projectvelero-distributors) mailing list. Distributors can initially plan for the vulnerability patch ahead of the fix, and later can test the fix and provide feedback to the Velero team. See the section **Early Disclosure to Velero Distributors List** for details about how to join this mailing list. 
-8. A public disclosure date is negotiated by the SecurityTeam, the bug submitter, and the distributors list. We prefer to fully disclose the bug as soon as possible once a user mitigation or patch is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for distributor coordination. The timeframe for disclosure is from immediate (especially if it’s already publicly known) to a few weeks. For a critical vulnerability with a straightforward mitigation, we expect the report date for the public disclosure date to be on the order of 14 business days. The Security Team holds the final say when setting a public disclosure date.
+8. A public disclosure date is negotiated by the VMware SecurityTeam, the bug submitter, and the distributors list. We prefer to fully disclose the bug as soon as possible once a user mitigation or patch is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for distributor coordination. The timeframe for disclosure is from immediate (especially if it’s already publicly known) to a few weeks. For a critical vulnerability with a straightforward mitigation, we expect the report date for the public disclosure date to be on the order of 14 business days. The VMware Security Team holds the final say when setting a public disclosure date.
 9. Once the fix is confirmed, the Security Team will patch the vulnerability in the next patch or minor release, and backport a patch release into all earlier supported releases. Upon release of the patched version of Velero, we will follow the **Public Disclosure Process**.
 
 
@@ -79,7 +79,7 @@ The Security Team will also publish any mitigating steps users can take until th
 
 
 
-*   Use velero-security.pdl@broadcom.com to report security concerns to the Security Team, who uses the list to privately discuss security issues and fixes prior to disclosure.
+*   Use security@vmware.com to report security concerns to the VMware Security Team, who uses the list to privately discuss security issues and fixes prior to disclosure.
 *   Join the [Velero Distributors](https://groups.google.com/u/1/g/projectvelero-distributors) mailing list for early private information and vulnerability disclosure. Early disclosure may include mitigating steps and additional information on security patch releases. See below for information on how Velero distributors or vendors can apply to join this list.
 
 
@@ -107,11 +107,11 @@ To be eligible to join the [Velero Distributors](https://groups.google.com/u/1/g
 
 ## Embargo Policy
 
-The information that members receive on the Velero Distributors mailing list must not be made public, shared, or even hinted at anywhere beyond those who need to know within your specific team, unless you receive explicit approval to do so from the Security Team. This remains true until the public disclosure date/time agreed upon by the list. Members of the list and others cannot use the information for any reason other than to get the issue fixed for your respective distribution's users.
+The information that members receive on the Velero Distributors mailing list must not be made public, shared, or even hinted at anywhere beyond those who need to know within your specific team, unless you receive explicit approval to do so from the VMware Security Team. This remains true until the public disclosure date/time agreed upon by the list. Members of the list and others cannot use the information for any reason other than to get the issue fixed for your respective distribution's users.
 
 Before you share any information from the list with members of your team who are required to fix the issue, these team members must agree to the same terms, and only be provided with information on a need-to-know basis.
 
-In the unfortunate event that you share information beyond what is permitted by this policy, you must urgently inform the Security Team (velero-security.pdl@broadcom.com) of exactly what information was leaked and to whom. If you continue to leak information and break the policy outlined here, you will be permanently removed from the list.
+In the unfortunate event that you share information beyond what is permitted by this policy, you must urgently inform the VMware Security Team (security@vmware.com) of exactly what information was leaked and to whom. If you continue to leak information and break the policy outlined here, you will be permanently removed from the list.
 
  
 
@@ -123,6 +123,6 @@ Send new membership requests to projectvelero-distributors@googlegroups.com. In
 
 ## Confidentiality, integrity and availability
 
-We consider vulnerabilities leading to the compromise of data confidentiality, elevation of privilege, or integrity to be our highest priority concerns. Availability, in particular in areas relating to DoS and resource exhaustion, is also a serious security concern. The Security Team takes all vulnerabilities, potential vulnerabilities, and suspected vulnerabilities seriously and will investigate them in an urgent and expeditious manner.
+We consider vulnerabilities leading to the compromise of data confidentiality, elevation of privilege, or integrity to be our highest priority concerns. Availability, in particular in areas relating to DoS and resource exhaustion, is also a serious security concern. The VMware Security Team takes all vulnerabilities, potential vulnerabilities, and suspected vulnerabilities seriously and will investigate them in an urgent and expeditious manner.
 
 Note that we do not currently consider the default settings for Velero to be secure-by-default. It is necessary for operators to explicitly configure settings, role based access control, and other resource related features in Velero to provide a hardened Velero environment. We will not act on any security disclosure that relates to a lack of safe defaults. Over time, we will work towards improved safe-by-default configuration, taking into account backwards compatibility.

Tiltfile

@@ -52,7 +52,7 @@ git_sha = str(local("git rev-parse HEAD", quiet = True, echo_off = True)).strip(
 
 tilt_helper_dockerfile_header = """
 # Tilt image
-FROM golang:1.24 as tilt-helper
+FROM golang:1.22.6 as tilt-helper
 
 # Support live reloading with Tilt
 RUN wget --output-document /restart.sh --quiet https://raw.githubusercontent.com/windmilleng/rerun-process-wrapper/master/restart.sh  && \

changelogs/CHANGELOG-1.14.md

@@ -1,3 +1,29 @@
+## v1.14.1
+
+### Download
+https://github.com/vmware-tanzu/velero/releases/tag/v1.14.1
+
+### Container Image
+`velero/velero:v1.14.1`
+
+### Documentation
+https://velero.io/docs/v1.14/
+
+### Upgrading
+https://velero.io/docs/v1.14/upgrade-to-1.14/
+
+### All Changes
+  * Avoid wrapping failed PVB status with empty message. (#8037, @mrnold)
+  * Make PVPatchMaximumDuration timeout configurable (#8035, @shubham-pampattiwar)
+  * Reuse existing plugin manager for get/put volume info (#8016, @sseago)
+  * Skip PV patch step in Restoe workflow for WaitForFirstConsumer VolumeBindingMode Pending state PVCs (#8006, @shubham-pampattiwar)
+  * Check whether the namespaces specified in namespace filter exist. (#7998, @blackpiglet)
+  * Check whether the volume's source is PVC before fetching its PV. (#7976, @blackpiglet)
+  * Fix issue #7904, add the limitation clarification for change PVC selected-node feature (#7949, @Lyndon-Li)
+  * Expose the VolumeHelper to third-party plugins. (#7944, @blackpiglet)
+  * Don't consider unschedulable pods unrecoverable (#7926, @sseago)
+
+
 ## v1.14
 
 ### Download

changelogs/CHANGELOG-1.15.md

@@ -1,145 +0,0 @@
-## v1.15
-
-### Download
-https://github.com/vmware-tanzu/velero/releases/tag/v1.15.0
-
-### Container Image
-`velero/velero:v1.15.0`
-
-### Documentation
-https://velero.io/docs/v1.15/
-
-### Upgrading
-https://velero.io/docs/v1.15/upgrade-to-1.15/
-
-### Highlights
-#### Data mover micro service
-Data transfer activities for CSI Snapshot Data Movement are moved from node-agent pods to dedicate backupPods or restorePods. This brings many benefits such as:  
-- This avoids to access volume data through host path, while host path access is privileged and may involve security escalations, which are concerned by users.
-- This enables users to to control resource (i.e., cpu, memory) allocations in a granular manner, e.g., control them per backup/restore of a volume.
-- This enhances the resilience, crash of one data movement activity won't affect others.
-- This prevents unnecessary full backup because of host path changes after workload pods restart.
-- For more information, check the design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/vgdp-micro-service/vgdp-micro-service.md.
-
-#### Item Block concepts and ItemBlockAction (IBA) plugin
-Item Block concepts are introduced for resource backups to help to achieve multiple thread backups. Specifically, correlated resources are categorized in the same item block and item blocks could be processed concurrently in multiple threads.  
-ItemBlockAction plugin is introduced to help Velero to categorize resources into item blocks. At present, Velero provides built-in IBAs for pods and PVCs and Velero also supports customized IBAs for any resources.  
-In v1.15, Velero doesn't support multiple thread process of item blocks though item block concepts and IBA plugins are fully supported. The multiple thread support will be delivered in future releases.  
-For more information, check the design https://github.com/vmware-tanzu/velero/blob/main/design/backup-performance-improvements.md.  
-
-#### Node selection for repository maintenance job
-Repository maintenance are resource consuming tasks, Velero now allows you to configure the nodes to run repository maintenance jobs, so that you can run repository maintenance jobs in idle nodes or avoid them to run in nodes hosting critical workloads.  
-To support the configuration, a new repository maintenance configuration configMap is introduced.  
-For more information, check the document https://velero.io/docs/v1.15/repository-maintenance/.  
-
-#### Backup PVC read-only configuration
-In 1.15, Velero allows you to configure the data mover backupPods to read-only mount the backupPVCs. In this way, the data mover expose process could be significantly accelerated for some storages (i.e., ceph).  
-To support the configuration, a new backup PVC configuration configMap is introduced.  
-For more information, check the document https://velero.io/docs/v1.15/data-movement-backup-pvc-configuration/.  
-
-#### Backup PVC storage class configuration
-In 1.15, Velero allows you to configure the storageclass used by the data mover backupPods. In this way, the provision of backupPVCs don't need to adhere to the same pattern as workload PVCs, e.g., for a backupPVC, it only needs one replica, whereas, the a workload PVC may have multiple replicas.  
-To support the configuration, the same backup PVC configuration configMap is used.  
-For more information, check the document https://velero.io/docs/v1.15/data-movement-backup-pvc-configuration/.  
-
-#### Backup repository data cache configuration
-The backup repository may need to cache data on the client side during various repository operations, i.e., read, write, maintenance, etc. The cache consumes the root file system space of the pod where the repository access happens.  
-In 1.15, Velero allows you to configure the total size of the cache per repository. In this way, if your pod doesn't have enough space in its root file system, the pod won't be evicted due to running out of ephemeral storage.  
-To support the configuration, a new backup repository configuration configMap is introduced.  
-For more information, check the document https://velero.io/docs/v1.15/backup-repository-configuration/.  
-
-#### Performance improvements
-In 1.15, several performance related issues/enhancements are included, which makes significant performance improvements in specific scenarios:  
-- There was a memory leak of Velero server after plugin calls, now it is fixed, see issue https://github.com/vmware-tanzu/velero/issues/7925
-- The `client-burst/client-qps` parameters are automatically inherited to plugins, so that you can use the same velero server parameters to accelerate the plugin executions when large number of API server calls happen, see issue https://github.com/vmware-tanzu/velero/issues/7806
-- Maintenance of Kopia repository takes huge memory in scenarios that huge number of files have been backed up, Velero 1.15 has included the Kopia upstream enhancement to fix the problem, see issue https://github.com/vmware-tanzu/velero/issues/7510
-
-### Runtime and dependencies
-Golang runtime: v1.22.8  
-kopia: v0.17.0
-
-### Limitations/Known issues
-#### Read-only backup PVC may not work on SELinux environments
-Due to an issue of Kubernetes upstream, if a volume is mounted as read-only in SELinux environments, the read privilege is not granted to any user, as a result, the data mover backup will fail. On the other hand, the backupPVC must be mounted as read-only in order to accelerate the data mover expose process.  
-Therefore, a user option is added in the same backup PVC configuration configMap, once the option is enabled, the backupPod container will run as a super privileged container and disable SELinux access control. If you have concern in this super privileged container or you have configured [pod security admissions](https://kubernetes.io/docs/concepts/security/pod-security-admission/) and don't allow super privileged containers, you will not be able to use this read-only backupPVC feature and lose the benefit to accelerate the data mover expose process.  
-
-### Breaking changes
-#### Deprecation of Restic
-Restic path for fs-backup is in deprecation process starting from 1.15. According to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy), for 1.15, if Restic path is used the backup/restore of fs-backup still creates and succeeds, but you will see warnings in below scenarios:  
-- When `--uploader-type=restic` is used in Velero installation
-- When Restic path is used to create backup/restore of fs-backup
-
-#### node-agent configuration name is configurable
-Previously, a fixed name is searched for node-agent configuration configMap. Now in 1.15, Velero allows you to customize the name of the configMap, on the other hand, the name must be specified by node-agent server parameter `node-agent-configmap`.  
-
-#### Repository maintenance job configurations in Velero server parameter are moved to repository maintenance job configuration configMap
-In 1.15, below Velero server parameters for repository maintenance jobs are moved to the repository maintenance job configuration configMap. While for back compatibility reason, the same Velero sever parameters are preserved as is. But the configMap is recommended and the same values in the configMap take preference if they exist in both places:  
-```
---keep-latest-maintenance-jobs
---maintenance-job-cpu-request
---maintenance-job-mem-request
---maintenance-job-cpu-limit
---maintenance-job-mem-limit
-```
-
-#### Changing PVC selected-node feature is deprecated
-In 1.15, the [Changing PVC selected-node feature](https://velero.io/docs/v1.15/restore-reference/#changing-pvc-selected-node) enters deprecation process and will be removed in future releases according to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/v1.15/GOVERNANCE.md#deprecation-policy). Usage of this feature for any purpose is not recommended.  
-
-### All Changes
-  * add no-relabeling option to backupPVC configmap (#8288, @sseago)
-  * only set spec.volumes readonly if PVC is readonly for datamover (#8284, @sseago)
-  * Add labels to maintenance job pods (#8256, @shubham-pampattiwar)
-  * Add the Carvel package related resources to the restore priority list (#8228, @ywk253100)
-  * Reduces indirect imports for plugin/framework importers (#8208, @kaovilai)
-  * Add controller name to periodical_enqueue_source. The logger parameter now includes an additional field with the value of reflect.TypeOf(objList).String() and another field with the value of controllerName. (#8198, @kaovilai)
-  * Update Openshift SCC docs link (#8170, @shubham-pampattiwar)
-  * Partially fix issue #8138, add doc for node-agent memory preserve (#8167, @Lyndon-Li)
-  * Pass Velero server command args to the plugins (#8166, @ywk253100)
-  * Fix issue #8155, Merge Kopia upstream commits for critical issue fixes and performance improvements (#8158, @Lyndon-Li)
-  * Implement the Repo maintenance Job configuration. (#8145, @blackpiglet)
-  * Add document for data mover micro service (#8144, @Lyndon-Li)
-  * Fix issue #8134, allow to config resource request/limit for data mover micro service pods (#8143, @Lyndon-Li)
-  * Apply backupPVCConfig to backupPod volume spec (#8141, @shubham-pampattiwar)
-  * Add resource modifier for velero restore describe CLI (#8139, @blackpiglet)
-  * Fix issue #7620, add doc for backup repo config (#8131, @Lyndon-Li)
-  * Modify E2E and perf test report generated directory (#8129, @blackpiglet)
-  * Add docs for backup pvc config support (#8119, @shubham-pampattiwar)
-  * Delete generated k8s client and informer. (#8114, @blackpiglet)
-  * Add support for backup PVC configuration (#8109, @shubham-pampattiwar)
-  * ItemBlock model and phase 1 (single-thread) workflow changes (#8102, @sseago)
-  * Fix issue #8032, make node-agent configMap name configurable (#8097, @Lyndon-Li)
-  * Fix issue #8072, add the warning messages for restic deprecation (#8096, @Lyndon-Li)
-  * Fix issue #7620, add backup repository configuration implementation and support cacheLimit configuration for Kopia repo (#8093, @Lyndon-Li)
-  * Patch dbr's status when error happens (#8086, @reasonerjt)
-  * According to design #7576, after node-agent restarts, if a DU/DD is in InProgress status, re-capture the data mover ms pod and continue the execution (#8085, @Lyndon-Li)
-  * Updates to IBM COS documentation to match current version (#8082, @gjanders)
-  * Data mover micro service DUCR/DDCR controller refactor according to design #7576 (#8074, @Lyndon-Li)
-  * add retries with timeout to existing patch calls that moves a backup/restore from InProgress/Finalizing to a final status phase. (#8068, @kaovilai)
-  * Data mover micro service restore according to design #7576 (#8061, @Lyndon-Li)
-  * Internal ItemBlockAction plugins (#8054, @sseago)
-  * Data mover micro service backup according to design #7576 (#8046, @Lyndon-Li)
-  * Avoid wrapping failed PVB status with empty message. (#8028, @mrnold)
-  * Created new ItemBlockAction (IBA) plugin type (#8026, @sseago)
-  * Make PVPatchMaximumDuration timeout configurable (#8021, @shubham-pampattiwar)
-  * Reuse existing plugin manager for get/put volume info (#8012, @sseago)
-  * Data mover ms watcher according to design #7576 (#7999, @Lyndon-Li)
-  * New data path for data mover ms according to design #7576 (#7988, @Lyndon-Li)
-  * For issue #7700 and #7747, add the design for backup PVC configurations (#7982, @Lyndon-Li)
-  * Only get VolumeSnapshotClass when DataUpload exists. (#7974, @blackpiglet)
-  * Fix issue #7972, sync the backupPVC deletion in expose clean up (#7973, @Lyndon-Li)
-  * Expose the VolumeHelper to third-party plugins. (#7969, @blackpiglet)
-  * Check whether the volume's source is PVC before fetching its PV. (#7967, @blackpiglet)
-  * Check whether the namespaces specified in namespace filter exist. (#7965, @blackpiglet)
-  * Add design for backup repository configurations for issue #7620, #7301 (#7963, @Lyndon-Li)
-  * New data path for data mover ms according to design #7576 (#7955, @Lyndon-Li)
-  * Skip PV patch step in Restoe workflow for WaitForFirstConsumer VolumeBindingMode Pending state PVCs (#7953, @shubham-pampattiwar)
-  * Fix issue #7904, add the deprecation and limitation clarification for change PVC selected-node feature (#7948, @Lyndon-Li)
-  * Expose the VolumeHelper to third-party plugins. (#7944, @blackpiglet)
-  * Don't consider unschedulable pods unrecoverable (#7899, @sseago)
-  * Upgrade to robfig/cron/v3 to support time zone specification. (#7793, @kaovilai)
-  * Add the result in the backup's VolumeInfo. (#7775, @blackpiglet)
-  * Migrate from github.com/golang/protobuf to google.golang.org/protobuf (#7593, @mmorel-35)
-  * Add the design for data mover micro service (#7576, @Lyndon-Li)
-  * Descriptive restore error when restoring into a terminating namespace. (#7424, @kaovilai)
-  * Ignore missing path error in conditional match (#7410, @seanblong)
-  * Propose a deprecation process for velero (#5532, @shubham-pampattiwar)

changelogs/CHANGELOG-1.16.md

@@ -1,156 +0,0 @@
-## v1.16
-
-### Download
-https://github.com/vmware-tanzu/velero/releases/tag/v1.16.0
-
-### Container Image
-`velero/velero:v1.16.0`
-
-### Documentation
-https://velero.io/docs/v1.16/
-
-### Upgrading
-https://velero.io/docs/v1.16/upgrade-to-1.16/
-
-### Highlights
-#### Windows cluster support
-In v1.16, Velero supports to run in Windows clusters and backup/restore Windows workloads, either stateful or stateless:
- * Hybrid build and all-in-one image: the build process is enhanced to build an all-in-one image for hybrid CPU architecture and hybrid platform. For more information, check the design https://github.com/vmware-tanzu/velero/blob/main/design/multiple-arch-build-with-windows.md
- * Deployment in Windows clusters: Velero node-agent, data mover pods and maintenance jobs now support to run in both linux and Windows nodes
- * Data mover backup/restore Windows workloads: Velero built-in data mover supports Windows workloads throughout its full cycle, i.e., discovery, backup, restore, pre/post hook, etc. It automatically identifies Windows workloads and schedules data mover pods to the right group of nodes
-
-Check the epic issue https://github.com/vmware-tanzu/velero/issues/8289 for more information.  
-
-#### Parallel Item Block backup
-v1.16 now supports to back up item blocks in parallel. Specifically, during backup, correlated resources are grouped in item blocks and Velero backup engine creates a thread pool to back up the item blocks in parallel. This significantly improves the backup throughput, especially when there are large scale of resources.  
-Pre/post hooks also belongs to item blocks, so will also run in parallel along with the item blocks.  
-Users are allowed to configure the parallelism through the `--item-block-worker-count` Velero server parameter. If not configured, the default parallelism is 1.  
-
-For more information, check issue https://github.com/vmware-tanzu/velero/issues/8334.  
-
-#### Data mover restore enhancement in scalability
-In previous releases, for each volume of WaitForFirstConsumer mode, data mover restore is only allowed to happen in the node that the volume is attached. This severely degrades the parallelism and the balance of node resource(CPU, memory, network bandwidth) consumption for data mover restore (https://github.com/vmware-tanzu/velero/issues/8044).  
-
-In v1.16, users are allowed to configure data mover restores running and spreading evenly across all nodes in the cluster. The configuration is done through a new flag `ignoreDelayBinding` in node-agent configuration (https://github.com/vmware-tanzu/velero/issues/8242).  
-
-#### Data mover enhancements in observability 
-In 1.16, some observability enhancements are added:
- * Output various statuses of intermediate objects for failures of data mover backup/restore (https://github.com/vmware-tanzu/velero/issues/8267)
- * Output the errors when Velero fails to delete intermediate objects during clean up (https://github.com/vmware-tanzu/velero/issues/8125)
-
-The outputs are in the same node-agent log and enabled automatically.  
-
-#### CSI snapshot backup/restore enhancement in usability
-In previous releases, a unnecessary VolumeSnapshotContent object is retained for each backup and synced to other clusters sharing the same backup storage location. And during restore, the retained VolumeSnapshotContent is also restored unnecessarily.  
-
-In 1.16, the retained VolumeSnapshotContent is removed from the backup, so no unnecessary CSI objects are synced or restored.  
-
-For more information, check issue https://github.com/vmware-tanzu/velero/issues/8725.  
-
-#### Backup Repository Maintenance enhancement in resiliency and observability
-In v1.16, some enhancements of backup repository maintenance are added to improve the observability and resiliency:
- * A new backup repository maintenance history section, called `RecentMaintenance`, is added to the BackupRepository CR. Specifically, for each BackupRepository, including start/completion time, completion status and error message. (https://github.com/vmware-tanzu/velero/issues/7810)
- * Running maintenance jobs are now recaptured after Velero server restarts. (https://github.com/vmware-tanzu/velero/issues/7753)
- * The maintenance job will not be launched for readOnly BackupStorageLocation. (https://github.com/vmware-tanzu/velero/issues/8238)
- * The backup repository will not try to initialize a new repository for readOnly BackupStorageLocation. (https://github.com/vmware-tanzu/velero/issues/8091)
- * Users now are allowed to configure the intervals of an effective maintenance in the way of `normalGC`, `fastGC` and `eagerGC`, through the `fullMaintenanceInterval` parameter in backupRepository configuration. (https://github.com/vmware-tanzu/velero/issues/8364)
-
-#### Volume Policy enhancement of filtering volumes by PVC labels
-In v1.16, Volume Policy is extended to support filtering volumes by PVC labels. (https://github.com/vmware-tanzu/velero/issues/8256).   
-
-#### Resource Status restore per object
-In v1.16, users are allowed to define whether to restore resource status per object through an annotation `velero.io/restore-status` set on the object. (https://github.com/vmware-tanzu/velero/issues/8204).  
-
-#### Velero Restore Helper binary is merged into Velero image 
-In v1.16, Velero banaries, i.e., velero, velero-helper and velero-restore-helper, are all included into the single Velero image. (https://github.com/vmware-tanzu/velero/issues/8484).  
-
-### Runtime and dependencies
-Golang runtime: 1.23.7  
-kopia: 0.19.0
-
-### Limitations/Known issues
-#### Limitations of Windows support
-  * fs-backup is not supported for Windows workloads and so fs-backup runs only in linux nodes for linux workloads
-  * Backup/restore of NTFS extended attributes/advanced features are not supported, i.e., Security Descriptors, System/Hidden/ReadOnly attributes, Creation Time, NTFS Streams, etc.
-
-### All Changes
-  * Add third party annotation support for maintenance job, so that the declared third party annotations could be added to the maintenance job pods (#8812, @Lyndon-Li)
-  * Fix issue #8803, use deterministic name to create backupRepository (#8808, @Lyndon-Li)
-  * Refactor restoreItem and related functions to differentiate the backup resource name and the restore target resource name. (#8797, @blackpiglet)
-  * ensure that PV is removed before VS is deleted (#8777, @ix-rzi)
-  * host_pods should not be mandatory to node-agent (#8774, @mpryc)
-  * Log doesn't show pv name, but displays %!s(MISSING) instead (#8771, @hu-keyu)
-  * Fix issue #8754, add third party annotation support for data mover (#8770, @Lyndon-Li)
-  * Add docs for volume policy with labels as a criteria (#8759, @shubham-pampattiwar)
-  * Move pvc annotation removal from CSI RIA to regular PVC RIA (#8755, @sseago)
-  * Add doc for maintenance history (#8747, @Lyndon-Li)
-  * Fix issue #8733, add doc for restorePVC (#8737, @Lyndon-Li)
-  * Fix issue #8426, add doc for Windows support (#8736, @Lyndon-Li)
-  * Fix issue #8475, refactor build-from-source doc for hybrid image build (#8729, @Lyndon-Li)
-  * Return directly if no pod volme backup are tracked (#8728, @ywk253100)
-  * Fix issue #8706, for immediate volumes, there is no selected-node annotation on PVC, so deduce the attached node from VolumeAttachment CRs (#8715, @Lyndon-Li)
-  * Add labels as a criteria for volume policy (#8713, @shubham-pampattiwar)
-  * Copy SecurityContext from Containers[0] if present for PVR (#8712, @sseago)
-  * Support pushing images to an insecure registry (#8703, @ywk253100)
-  * Modify golangci configuration to make it work. (#8695, @blackpiglet)
-  * Run backup post hooks inside ItemBlock synchronously (#8694, @ywk253100)
-  * Add docs for object level status restore (#8693, @shubham-pampattiwar)
-  * Clean artifacts generated during CSI B/R. (#8684, @blackpiglet)
-  * Don't run maintenance on the ReadOnly BackupRepositories. (#8681, @blackpiglet)
-  * Fix #8657: WaitGroup panic issue (#8679, @ywk253100)
-  * Fixes issue #8214, validate `--from-schedule` flag in create backup command to prevent empty or whitespace-only values. (#8665, @aj-2000)
-  * Implement parallel ItemBlock processing via backup_controller goroutines (#8659, @sseago)
-  * Clean up leaked CSI snapshot for incomplete backup (#8637, @raesonerjt)
-  * Handle update conflict when restoring the status (#8630, @ywk253100)
-  * Fix issue #8419, support repo maintenance job to run on Windows nodes (#8626, @Lyndon-Li)
-  * Always create DataUpload configmap in restore namespace (#8621, @sseago)
-  * Fix issue #8091, avoid to create new repo when BSL is readonly (#8615, @Lyndon-Li)
-  * Fix issue #8242, distribute dd evenly across nodes (#8611, @Lyndon-Li)
-  * Fix issue #8497, update du/dd progress on completion (#8608, @Lyndon-Li)
-  * Fix issue #8418, add Windows toleration to data mover pods (#8606, @Lyndon-Li)
-  * Check the PVB status via podvolume Backupper rather than calling API server to avoid API server issue (#8603, @ywk253100)
-  * Fix issue #8067, add tmp folder (/tmp for linux, C:\Windows\Temp for Windows) as an alternative of udmrepo's config file location (#8602, @Lyndon-Li)
-  * Data mover restore for Windows (#8594, @Lyndon-Li)
-  * Skip patching the PV in finalization for failed operation (#8591, @reasonerjt)
-  * Fix issue #8579, set event burst to block event broadcaster from filtering events (#8590, @Lyndon-Li)
-  * Configurable Kopia Maintenance Interval. backup-repository-configmap adds an option for configurable`fullMaintenanceInterval` where fastGC (12 hours), and eagerGC (6 hours) allowing for faster removal of deleted velero backups from kopia repo. (#8581, @kaovilai)
-  * Fix issue #7753, recall repo maintenance history on Velero server restart (#8580, @Lyndon-Li)
-  * Clear validation errors when schedule is valid (#8575, @ywk253100)
-  * Merge restore helper image into Velero server image (#8574, @ywk253100)
-  * Don't include excluded items in ItemBlocks (#8572, @sseago)
-  * fs uploader and block uploader support Windows nodes (#8569, @Lyndon-Li)
-  * Fix issue #8418, support data mover backup for Windows nodes (#8555, @Lyndon-Li)
-  * Fix issue #8044, allow users to ignore delay binding the restorePVC of data mover when it is in WaitForFirstConsumer mode (#8550, @Lyndon-Li)
-  * Fix issue #8539, validate uploader types when o.CRDsOnly is set to false only since CRD installation doesn't rely on uploader types (#8538, @Lyndon-Li)
-  * Fix issue #7810, add maintenance history for backupRepository CRs (#8532, @Lyndon-Li)
-  * Make fs-backup work on linux nodes with the new Velero deployment and disable fs-backup if the source/target pod is running in non-linux node (#8424) (#8518, @Lyndon-Li)
-  * Fix issue: backup schedule pause/unpause doesn't work (#8512, @ywk253100)
-  * Fix backup post hook issue #8159 (caused by #7571): always execute backup post hooks after PVBs are handled (#8509, @ywk253100)
-  * Fix issue #8267, enhance the error message when expose fails (#8508, @Lyndon-Li)
-  * Fix issue #8416, #8417, deploy Velero server and node-agent in linux/Windows hybrid env (#8504, @Lyndon-Li)
-  * Design to add label selector as a criteria for volume policy (#8503, @shubham-pampattiwar)
-  * Related to issue #8485, move the acceptedByNode and acceptedTimestamp to Status of DU/DD CRD (#8498, @Lyndon-Li)
-  * Add SecurityContext to restore-helper (#8491, @reasonerjt)
-  * Fix issue #8433, add third party labels to data mover pods when the same labels exist in node-agent pods (#8487, @Lyndon-Li)
-  * Fix issue #8485, add an accepted time so as to count the prepare timeout (#8486, @Lyndon-Li)
-  * Fix issue #8125, log diagnostic info for data mover exposers when expose timeout (#8482, @Lyndon-Li)
-  * Fix issue #8415, implement multi-arch build and Windows build (#8476, @Lyndon-Li)
-  * Pin kopia to 0.18.2 (#8472, @Lyndon-Li)
-  * Add nil check for updating DataUpload VolumeInfo in finalizing phase (#8471, @blackpiglet)
-  * Allowing Object-Level Resource Status Restore (#8464, @shubham-pampattiwar)
-  * For issue #8429. Add the design for multi-arch build and windows build (#8459, @Lyndon-Li)
-  * Upgrade go.mod k8s.io/ go.mod to v0.31.3 and implemented proper logger configuration for both client-go and controller-runtime libraries. This change ensures that logging format and level settings are properly applied throughout the codebase. The update improves logging consistency and control across the Velero system. (#8450, @kaovilai)
-  * Add Design for Allowing Object-Level Resource Status Restore (#8403, @shubham-pampattiwar)
-  * Fix issue #8391, check ErrCancelled from suffix of data mover pod's termination message (#8396, @Lyndon-Li)
-  * Fix issue #8394, don't call closeDataPath in VGDP callbacks, otherwise, the VGDP cleanup will hang (#8395, @Lyndon-Li)
-  * Adding support in velero Resource Policies for filtering PVs based on additional VolumeAttributes properties under CSI PVs (#8383, @mayankagg9722)
-  * Add --item-block-worker-count flag to velero install and server (#8380, @sseago)
-  * Make BackedUpItems thread safe (#8366, @sseago)
-  * Include --annotations flag in backup and restore create commands (#8354, @alromeros)
-  * Use aggregated discovery API to discovery API groups and resources (#8353, @ywk253100)
-  * Copy "envFrom" from Velero server when creating maintenance jobs (#8343, @evhan)
-  * Set hinting region to use for GetBucketRegion() in pkg/repository/config/aws.go (#8297, @kaovilai)
-  * Bump up version of client-go and controller-runtime (#8275, @ywk253100)
-  * fix(pkg/repository/maintenance): don't panic when there's no container statuses (#8271, @mcluseau)
-  * Add Backup warning for inclusion of NS managed by ArgoCD (#8257, @shubham-pampattiwar)
-  * Added tracking for deleted namespace status check in restore flow. (#8233, @sangitaray2021)

changelogs/CHANGELOG-1.17.md

@@ -1,143 +0,0 @@
-## v1.17
-
-### Download
-https://github.com/vmware-tanzu/velero/releases/tag/v1.17.0
-
-### Container Image
-`velero/velero:v1.17.0`
-
-### Documentation
-https://velero.io/docs/v1.17/
-
-### Upgrading
-https://velero.io/docs/v1.17/upgrade-to-1.17/
-
-### Highlights
-#### Modernized fs-backup
-In v1.17, Velero fs-backup is modernized to the micro-service architecture, which brings below benefits:  
-- Many features that were absent to fs-backup are now available, i.e., load concurrency control, cancel, resume on restart, etc.
-- fs-backup is more robust, the running backup/restore could survive from node-agent restart; and the resource allocation is in a more granular manner, the failure of one backup/restore won't impact others.  
-- The resource usage of node-agent is steady, especially, the node-agent pods won't request huge memory and hold it for a long time.  
-
-Check design https://github.com/vmware-tanzu/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details.  
-
-#### fs-backup support Windows cluster
-In v1.17, Velero fs-backup supports to backup/restore Windows workloads. By leveraging the new micro-service architecture for fs-backup, data mover pods could run in Windows nodes and backup/restore Windows volumes. Together with CSI snapshot data movement for Windows which is delivered in 1.16, Velero now supports Windows workload backup/restore in full scenarios.  
-Check design https://github.com/vmware-tanzu/velero/blob/main/design/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md for more details.  
-
-#### Volume group snapshot support
-In v1.17, Velero supports [volume group snapshots](https://kubernetes.io/blog/2024/12/18/kubernetes-1-32-volume-group-snapshot-beta/) which is a beta feature in Kubernetes upstream, for both CSI snapshot backup and CSI snapshot data movement. This allows a snapshot to be taken from multiple volumes at the same point-in-time to achieve write order consistency, which is helpful to achieve better data consistency when multiple volumes being backed up are correlated.  
-Check the document https://velero.io/docs/main/volume-group-snapshots/ for more details.  
-
-#### Priority class support
-In v1.17, [Kubernetes priority class](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass) is supported for all modules across Velero. Specifically, users are allowed to configure priority class to Velero server, node-agent, data mover pods, backup repository maintenance jobs separately.  
-Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/priority-class-name-support_design.md for more details.  
-
-#### Scalability and Resiliency improvements of data movers
-##### Reduce excessive number of data mover pods in Pending state
-In v1.17, Velero allows users to set a `PrepareQueueLength` in the node-agent configuration, data mover pods and volumes out of this number won't be created until data path quota is available, so that excessive number cluster resources won't  be taken unnecessarily, which is particularly helpful for large scale environments. This improvement applies to all kinds of data movements, including fs-backup and CSI snapshot data movement.  
-Check design https://github.com/vmware-tanzu/velero/blob/main/design/node-agent-load-soothing.md for more details.  
-
-##### Enhancement on node-agent restart handling for data movements
-In v1.17, data movements in all phases could survive from node-agent restart and resume themselves; when a data movement gets orphaned in special cases, e.g., cluster node absent, it could also be canceled appropriately after the restart. This improvement applies to all kinds of data movements, including fs-backup and CSI snapshot data movement.  
-Check issue https://github.com/vmware-tanzu/velero/issues/8534 for more details.  
-
-##### CSI snapshot data movement restore node-selection and node-selection by storage class
-In v1.17, CSI snapshot data movement restore acquires the same node-selection capability as backup, that is, users could specify which nodes can/cannot run data mover pods for both backup and restore now. And users are also allowed to configure the node-selection per storage class, which is particularly helpful to the environments where a storage class are not usable by all cluster nodes.  
-Check issue https://github.com/vmware-tanzu/velero/issues/8186 and https://github.com/vmware-tanzu/velero/issues/8223 for more details.  
-
-#### Include/exclude policy support for resource policy
-In v1.17, Velero resource policy supports `includeExcludePolicy` besides the existing `volumePolicy`. This allows users to set include/exclude filters for resources in a resource policy configmap, so that these filters are reusable among multiple backups.  
-Check the document https://velero.io/docs/main/resource-filtering/#creating-resource-policies:~:text=resources%3D%22*%22-,Resource%20policies,-Velero%20provides%20resource for more details.  
-
-### Runtime and dependencies
-Golang runtime: 1.24.6  
-kopia: 0.21.1  
-
-### Limitations/Known issues
-
-### Breaking changes
-#### Deprecation of Restic
-According to [Velero deprecation policy](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md#deprecation-policy), backup of fs-backup under Restic path is removed in v1.17, so `--uploader-type=restic` is not a valid installation configuration anymore. This means you cannot create a backup under Restic path, but you can still restore from the previous backups under Restic path until v1.19.  
-
-#### Repository maintenance job configurations are removed from Velero server parameter
-Since the repository maintenance job configurations are moved to repository maintenance job configMap, in v1.17 below Velero sever parameters are removed:
-- --keep-latest-maintenance-jobs
-- --maintenance-job-cpu-request
-- --maintenance-job-mem-request
-- --maintenance-job-cpu-limit
-- --maintenance-job-mem-limit
-
-### All Changes
-  * Add ConfigMap parameters validation for install CLI and server start. (#9200, @blackpiglet)
-  * Add priorityclasses to high priority restore list (#9175, @kaovilai)
-  * Introduced context-based logger for backend implementations (Azure, GCS, S3, and Filesystem) (#9168, @priyansh17)
-  * Fix issue #9140, add os=windows:NoSchedule toleration for Windows pods (#9165, @Lyndon-Li)
-  * Remove the repository maintenance job parameters from velero server. (#9147, @blackpiglet)
-  * Add include/exclude policy to resources policy (#9145, @reasonerjt)
-  * Add ConfigMap support for keepLatestMaintenanceJobs with CLI parameter fallback (#9135, @shubham-pampattiwar)
-  * Fix the dd and du's node affinity issue. (#9130, @blackpiglet)
-  * Remove the WaitUntilVSCHandleIsReady from vs BIA. (#9124, @blackpiglet)
-  * Add comprehensive Volume Group Snapshots documentation with workflow diagrams and examples (#9123, @shubham-pampattiwar)
-  * Fix issue #9065, add doc for node-agent prepare queue length (#9118, @Lyndon-Li)
-  * Fix issue #9095, update restore doc for PVC selected-node (#9117, @Lyndon-Li)
-  * Update CSI Snapshot Data Movement doc for issue #8534, #8185 (#9113, @Lyndon-Li)
-  * Fix issue #8986, refactor fs-backup doc after VGDP Micro Service for fs-backup (#9112, @Lyndon-Li)
-  * Return error if timeout when checking server version (#9111, @ywk253100)
-  * Update "Default Volumes to Fs Backup" to "File System Backup (Default)" (#9105, @shubham-pampattiwar)
-  * Fix issue #9077, don't block backup deletion on list VS error (#9100, @Lyndon-Li)
-  * Bump up Kopia to v0.21.1 (#9098, @Lyndon-Li)
-  * Add imagePullSecrets inheritance for VGDP pod and maintenance job. (#9096, @blackpiglet)
-  * Avoid checking the VS and VSC status in the backup finalizing phase. (#9092, @blackpiglet)
-  * Fix issue #9053, Always remove selected-node annotation during PVC restore when no node mapping exists. Breaking change: Previously, the annotation was preserved if the node existed. (#9076, @Lyndon-Li)
-  * Enable parameterized kubelet mount path during node-agent installation (#9074, @longxiucai)
-  * Fix issue #8857, support third party tolerations for data mover pods (#9072, @Lyndon-Li)
-  * Fix issue #8813, remove restic from the valid uploader type (#9069, @Lyndon-Li)
-  * Fix issue #8185, allow users to disable pod volume host path mount for node-agent (#9068, @Lyndon-Li)
-  * Fix #8344, add the design for a mechanism to soothe creation of data mover pods for DataUpload, DataDownload, PodVolumeBackup and PodVolumeRestore (#9067, @Lyndon-Li)
-  * Fix #8344, add a mechanism to soothe creation of data mover pods for DataUpload, DataDownload, PodVolumeBackup and PodVolumeRestore (#9064, @Lyndon-Li)
-  * Add Gauge metric for BSL availability (#9059, @reasonerjt)
-  * Fix missing defaultVolumesToFsBackup flag output in Velero describe backup cmd (#9056, @shubham-pampattiwar)
-  * Allow for proper tracking of multiple hooks per container (#9048, @sseago)
-  * Make the backup repository controller doesn't invalidate the BSL on restart (#9046, @blackpiglet)
-  * Removed username/password credential handling from newConfigCredential as azidentity.UsernamePasswordCredentialOptions is reported as deprecated. (#9041, @priyansh17)
-  * Remove dependency with VolumeSnapshotClass in DataUpload. (#9040, @blackpiglet)
-  * Fix issue #8961, cancel PVB/PVR on Velero server restart (#9031, @Lyndon-Li)
-  * Fix issue #8962, resume PVB/PVR during node-agent restarts (#9030, @Lyndon-Li)
-  * Bump kopia v0.20.1 (#9027, @Lyndon-Li)
-  * Fix issue #8965, support PVB/PVR's cancel state in the backup/restore (#9026, @Lyndon-Li)
-  * Fix Issue 8816 When specifying LabelSelector on restore, related items such as PVC and VolumeSnapshot are not included (#9024, @amastbau)
-  * Fix issue #8963, add legacy PVR controller for Restic path (#9022, @Lyndon-Li)
-  * Fix issue #8964, add Windows support for VGDP MS for fs-backup (#9021, @Lyndon-Li)
-  * Accommodate VGS workflows in PVC CSI plugin (#9019, @shubham-pampattiwar)
-  * Fix issue #8958, add VGDP MS PVB controller (#9015, @Lyndon-Li)
-  * Fix issue #8959, add VGDP MS PVR controller (#9014, @Lyndon-Li)
-  * Fix issue #8988, add data path for VGDP ms PVR (#9005, @Lyndon-Li)
-  * Fix issue #8988, add data path for VGDP ms pvb (#8998, @Lyndon-Li)
-  * Skip VS and VSC not created by backup. (#8990, @blackpiglet)
-  * Make ResticIdentifier optional for kopia BackupRepositories (#8987, @kaovilai)
-  * Fix issue #8960, implement PodVolume exposer for PVB/PVR (#8985, @Lyndon-Li)
-  * fix: update mc command in minio-deployment example (#8982, @vishal-chdhry)
-  * Fix issue #8957, add design for VGDP MS for fs-backup (#8979, @Lyndon-Li)
-  * Add BSL status check for backup/restore operations. (#8976, @blackpiglet)
-  * Mark BackupRepository not ready when BSL changed (#8975, @ywk253100)
-  * Add support for [distributed snapshotting](https://github.com/kubernetes-csi/external-snapshotter/tree/4cedb3f45790ac593ebfa3324c490abedf739477?tab=readme-ov-file#distributed-snapshotting) (#8969, @flx5)
-  * Fix issue #8534, refactor dm controllers to tolerate cancel request in more cases, e.g., node restart, node drain (#8952, @Lyndon-Li)
-  * The backup and restore VGDP affinity enhancement implementation. (#8949, @blackpiglet)
-  * Remove CSI VS and VSC metadata from backup. (#8946, @blackpiglet)
-  * Extend PVCAction itemblock plugin to support grouping PVCs under VGS label key (#8944, @shubham-pampattiwar)
-  * Copy security context from origin pod (#8943, @farodin91)
-  * Add support for configuring VGS label key (#8938, @shubham-pampattiwar)
-  * Add VolumeSnapshotContent into the RIA and the mustHave resource list. (#8924, @blackpiglet)
-  * Mounted cloud credentials should not be world-readable (#8919, @sseago)
-  * Warn for not found error in patching managed fields (#8902, @sseago)
-  * Fix issue 8878, relief node os deduction error checks (#8891, @Lyndon-Li)
-  * Skip namespace in terminating state in backup resource collection. (#8890, @blackpiglet)
-  * Implement PriorityClass Support (#8883, @kaovilai)
-  * Fix Velero adding restore-wait init container when not needed. (#8880, @kaovilai)
-  * Pass the logger in kopia related operations. (#8875, @hu-keyu)
-  * Inherit the dnsPolicy and dnsConfig from the node agent pod. This is done so that the kopia task uses the same configuration. (#8845, @flx5)
-  * Add design for VolumeGroupSnapshot support (#8778, @shubham-pampattiwar)
-  * Inherit k8s default volumeSnapshotClass. (#8719, @hu-keyu)
-  * CLI automatically discovers and uses cacert from BSL for download requests (#8557, @kaovilai)
-  * This PR aims to add s390x support to Velero binary. (#7505, @pandurangkhandeparker)

changelogs/unreleased/8304-shubham-pampattiwar

@@ -0,0 +1 @@
+Remove multiple single quotes from Velero backup.status.validationErrors field

changelogs/unreleased/9173-clementnuss

@@ -1 +0,0 @@
-feat: Permit specifying annotations for the BackupPVC

changelogs/unreleased/9226-sseago

@@ -1 +0,0 @@
-Get pod list once per namespace in pvc IBA

changelogs/unreleased/9233-Lyndon-Li

@@ -1 +0,0 @@
-Fix issue #9229, don't attach backupPVC to the source node

changelogs/unreleased/9244-priyansh17

@@ -1 +0,0 @@
-Update AzureAD Microsoft Authentication Library to v1.5.0

changelogs/unreleased/9248-0xLeo258

@@ -1 +0,0 @@
-Protect VolumeSnapshot field from race condition during multi-thread backup

changelogs/unreleased/9256-shubham-pampattiwar

@@ -1 +0,0 @@
-Fix repository maintenance jobs to inherit allowlisted tolerations from Velero deployment

changelogs/unreleased/9264-shubham-pampattiwar

@@ -1 +0,0 @@
-Fix schedule controller to prevent backup queue accumulation during extended blocking scenarios by properly handling empty backup phases

changelogs/unreleased/9281-0xLeo258

@@ -1 +0,0 @@
-Implement concurrency control for cache of native VolumeSnapshotter plugin.

changelogs/unreleased/9295-sseago

@@ -1 +0,0 @@
-Add option for privileged fs-backup pod

changelogs/unreleased/9296-Lyndon-Li

@@ -1 +0,0 @@
-Fix issue #9267, add events to data mover prepare diagnostic

changelogs/unreleased/9302-blackpiglet

@@ -1 +0,0 @@
-VerifyJSONConfigs verify every elements in Data.

changelogs/unreleased/9329-T4iFooN-IX

@@ -1 +0,0 @@
-Fix typos in documentation

config/crd/v1/bases/velero.io_backuprepositories.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: backuprepositories.velero.io
 spec:
   group: velero.io
@@ -54,13 +54,6 @@ spec:
                 description: MaintenanceFrequency is how often maintenance should
                   be run.
                 type: string
-              repositoryConfig:
-                additionalProperties:
-                  type: string
-                description: RepositoryConfig is for repository-specific configuration
-                  fields.
-                nullable: true
-                type: object
               repositoryType:
                 description: RepositoryType indicates the type of the backend repository
                 enum:
@@ -71,7 +64,7 @@ spec:
               resticIdentifier:
                 description: |-
                   ResticIdentifier is the full restic-compatible string for identifying
-                  this repository. This field is only used when RepositoryType is "restic".
+                  this repository.
                 type: string
               volumeNamespace:
                 description: |-
@@ -81,14 +74,15 @@ spec:
             required:
             - backupStorageLocation
             - maintenanceFrequency
+            - resticIdentifier
             - volumeNamespace
             type: object
           status:
             description: BackupRepositoryStatus is the current status of a BackupRepository.
             properties:
               lastMaintenanceTime:
-                description: LastMaintenanceTime is the last time repo maintenance
-                  succeeded.
+                description: LastMaintenanceTime is the last time maintenance was
+                  run.
                 format: date-time
                 nullable: true
                 type: string
@@ -103,33 +97,6 @@ spec:
                 - Ready
                 - NotReady
                 type: string
-              recentMaintenance:
-                description: RecentMaintenance is status of the recent repo maintenance.
-                items:
-                  properties:
-                    completeTimestamp:
-                      description: CompleteTimestamp is the completion time of the
-                        repo maintenance.
-                      format: date-time
-                      nullable: true
-                      type: string
-                    message:
-                      description: Message is a message about the current status of
-                        the repo maintenance.
-                      type: string
-                    result:
-                      description: Result is the result of the repo maintenance.
-                      enum:
-                      - Succeeded
-                      - Failed
-                      type: string
-                    startTimestamp:
-                      description: StartTimestamp is the start time of the repo maintenance.
-                      format: date-time
-                      nullable: true
-                      type: string
-                  type: object
-                type: array
             type: object
         type: object
     served: true

config/crd/v1/bases/velero.io_backups.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: backups.velero.io
 spec:
   group: velero.io
@@ -63,6 +63,7 @@ spec:
                   DefaultVolumesToRestic specifies whether restic should be used to take a
                   backup of all pod volumes by default.
 
+
                   Deprecated: this field is no longer used and will be removed entirely in future. Use DefaultVolumesToFsBackup instead.
                 nullable: true
                 type: boolean
@@ -175,13 +176,11 @@ spec:
                                     items:
                                       type: string
                                     type: array
-                                    x-kubernetes-list-type: atomic
                                 required:
                                 - key
                                 - operator
                                 type: object
                               type: array
-                              x-kubernetes-list-type: atomic
                             matchLabels:
                               additionalProperties:
                                 type: string
@@ -365,13 +364,11 @@ spec:
                           items:
                             type: string
                           type: array
-                          x-kubernetes-list-type: atomic
                       required:
                       - key
                       - operator
                       type: object
                     type: array
-                    x-kubernetes-list-type: atomic
                   matchLabels:
                     additionalProperties:
                       type: string
@@ -428,13 +425,11 @@ spec:
                             items:
                               type: string
                             type: array
-                            x-kubernetes-list-type: atomic
                         required:
                         - key
                         - operator
                         type: object
                       type: array
-                      x-kubernetes-list-type: atomic
                     matchLabels:
                       additionalProperties:
                         type: string
@@ -507,10 +502,6 @@ spec:
                       uploads to perform when using the uploader.
                     type: integer
                 type: object
-              volumeGroupSnapshotLabelKey:
-                description: VolumeGroupSnapshotLabelKey specifies the label key to
-                  group PVCs under a VGS.
-                type: string
               volumeSnapshotLocations:
                 description: VolumeSnapshotLocations is a list containing names of
                   VolumeSnapshotLocations associated with this backup.

config/crd/v1/bases/velero.io_backupstoragelocations.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: backupstoragelocations.velero.io
 spec:
   group: velero.io
@@ -86,13 +86,10 @@ spec:
                       valid secret key.
                     type: string
                   name:
-                    default: ""
                     description: |-
                       Name of the referent.
-                      This field is effectively required, but due to backwards compatibility is
-                      allowed to be empty. Instances of this type with an empty value here are
-                      almost certainly wrong.
                       More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
+                      TODO: Add other useful fields. apiVersion, kind, uid?
                     type: string
                   optional:
                     description: Specify whether the Secret or its key must be defined
@@ -144,6 +141,7 @@ spec:
                 description: |-
                   AccessMode is an unused field.
 
+
                   Deprecated: there is now an AccessMode field on the Spec and this field
                   will be removed entirely as of v2.0.
                 enum:
@@ -155,6 +153,7 @@ spec:
                   LastSyncedRevision is the value of the `metadata/revision` file in the backup
                   storage location the last time the BSL's contents were synced into the cluster.
 
+
                   Deprecated: this field is no longer updated or used for detecting changes to
                   the location's contents and will be removed entirely in v2.0.
                 type: string

config/crd/v1/bases/velero.io_deletebackuprequests.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: deletebackuprequests.velero.io
 spec:
   group: velero.io

config/crd/v1/bases/velero.io_downloadrequests.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: downloadrequests.velero.io
 spec:
   group: velero.io

config/crd/v1/bases/velero.io_podvolumebackups.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: podvolumebackups.velero.io
 spec:
   group: velero.io
@@ -15,41 +15,38 @@ spec:
   scope: Namespaced
   versions:
   - additionalPrinterColumns:
-    - description: PodVolumeBackup status such as New/InProgress
+    - description: Pod Volume Backup status such as New/InProgress
       jsonPath: .status.phase
       name: Status
       type: string
-    - description: Time duration since this PodVolumeBackup was started
+    - description: Time when this backup was started
       jsonPath: .status.startTimestamp
-      name: Started
+      name: Created
       type: date
-    - description: Completed bytes
-      format: int64
-      jsonPath: .status.progress.bytesDone
-      name: Bytes Done
-      type: integer
-    - description: Total bytes
-      format: int64
-      jsonPath: .status.progress.totalBytes
-      name: Total Bytes
-      type: integer
+    - description: Namespace of the pod containing the volume to be backed up
+      jsonPath: .spec.pod.namespace
+      name: Namespace
+      type: string
+    - description: Name of the pod containing the volume to be backed up
+      jsonPath: .spec.pod.name
+      name: Pod
+      type: string
+    - description: Name of the volume to be backed up
+      jsonPath: .spec.volume
+      name: Volume
+      type: string
+    - description: The type of the uploader to handle data transfer
+      jsonPath: .spec.uploaderType
+      name: Uploader Type
+      type: string
     - description: Name of the Backup Storage Location where this backup should be
         stored
       jsonPath: .spec.backupStorageLocation
       name: Storage Location
       type: string
-    - description: Time duration since this PodVolumeBackup was created
-      jsonPath: .metadata.creationTimestamp
+    - jsonPath: .metadata.creationTimestamp
       name: Age
       type: date
-    - description: Name of the node where the PodVolumeBackup is processed
-      jsonPath: .status.node
-      name: Node
-      type: string
-    - description: The type of the uploader to handle data transfer
-      jsonPath: .spec.uploaderType
-      name: Uploader
-      type: string
     name: v1
     schema:
       openAPIV3Schema:
@@ -79,11 +76,6 @@ spec:
                   BackupStorageLocation is the name of the backup storage location
                   where the backup repository is stored.
                 type: string
-              cancel:
-                description: |-
-                  Cancel indicates request to cancel the ongoing PodVolumeBackup. It can be set
-                  when the PodVolumeBackup is in InProgress phase
-                type: boolean
               node:
                 description: Node is the name of the node that the Pod is running
                   on.
@@ -104,6 +96,7 @@ spec:
                       the event) or if no container name is specified "spec.containers[2]" (container with
                       index 2 in this pod). This syntax is chosen only to have some well-defined way of
                       referencing a part of an object.
+                      TODO: this design is not final and this field is subject to change in the future.
                     type: string
                   kind:
                     description: |-
@@ -173,13 +166,6 @@ spec:
           status:
             description: PodVolumeBackupStatus is the current status of a PodVolumeBackup.
             properties:
-              acceptedTimestamp:
-                description: |-
-                  AcceptedTimestamp records the time the pod volume backup is to be prepared.
-                  The server's time is used for AcceptedTimestamp
-                format: date-time
-                nullable: true
-                type: string
               completionTimestamp:
                 description: |-
                   CompletionTimestamp records the time a backup was completed.
@@ -200,11 +186,7 @@ spec:
                 description: Phase is the current state of the PodVolumeBackup.
                 enum:
                 - New
-                - Accepted
-                - Prepared
                 - InProgress
-                - Canceling
-                - Canceled
                 - Completed
                 - Failed
                 type: string

config/crd/v1/bases/velero.io_podvolumerestores.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: podvolumerestores.velero.io
 spec:
   group: velero.io
@@ -15,40 +15,39 @@ spec:
   scope: Namespaced
   versions:
   - additionalPrinterColumns:
-    - description: PodVolumeRestore status such as New/InProgress
-      jsonPath: .status.phase
-      name: Status
+    - description: Namespace of the pod containing the volume to be restored
+      jsonPath: .spec.pod.namespace
+      name: Namespace
       type: string
-    - description: Time duration since this PodVolumeRestore was started
-      jsonPath: .status.startTimestamp
-      name: Started
-      type: date
-    - description: Completed bytes
-      format: int64
-      jsonPath: .status.progress.bytesDone
-      name: Bytes Done
-      type: integer
-    - description: Total bytes
-      format: int64
-      jsonPath: .status.progress.totalBytes
-      name: Total Bytes
-      type: integer
-    - description: Name of the Backup Storage Location where the backup data is stored
-      jsonPath: .spec.backupStorageLocation
-      name: Storage Location
-      type: string
-    - description: Time duration since this PodVolumeRestore was created
-      jsonPath: .metadata.creationTimestamp
-      name: Age
-      type: date
-    - description: Name of the node where the PodVolumeRestore is processed
-      jsonPath: .status.node
-      name: Node
+    - description: Name of the pod containing the volume to be restored
+      jsonPath: .spec.pod.name
+      name: Pod
       type: string
     - description: The type of the uploader to handle data transfer
       jsonPath: .spec.uploaderType
       name: Uploader Type
       type: string
+    - description: Name of the volume to be restored
+      jsonPath: .spec.volume
+      name: Volume
+      type: string
+    - description: Pod Volume Restore status such as New/InProgress
+      jsonPath: .status.phase
+      name: Status
+      type: string
+    - description: Pod Volume Restore status such as New/InProgress
+      format: int64
+      jsonPath: .status.progress.totalBytes
+      name: TotalBytes
+      type: integer
+    - description: Pod Volume Restore status such as New/InProgress
+      format: int64
+      jsonPath: .status.progress.bytesDone
+      name: BytesDone
+      type: integer
+    - jsonPath: .metadata.creationTimestamp
+      name: Age
+      type: date
     name: v1
     schema:
       openAPIV3Schema:
@@ -78,11 +77,6 @@ spec:
                   BackupStorageLocation is the name of the backup storage location
                   where the backup repository is stored.
                 type: string
-              cancel:
-                description: |-
-                  Cancel indicates request to cancel the ongoing PodVolumeRestore. It can be set
-                  when the PodVolumeRestore is in InProgress phase
-                type: boolean
               pod:
                 description: Pod is a reference to the pod containing the volume to
                   be restored.
@@ -99,6 +93,7 @@ spec:
                       the event) or if no container name is specified "spec.containers[2]" (container with
                       index 2 in this pod). This syntax is chosen only to have some well-defined way of
                       referencing a part of an object.
+                      TODO: this design is not final and this field is subject to change in the future.
                     type: string
                   kind:
                     description: |-
@@ -168,13 +163,6 @@ spec:
           status:
             description: PodVolumeRestoreStatus is the current status of a PodVolumeRestore.
             properties:
-              acceptedTimestamp:
-                description: |-
-                  AcceptedTimestamp records the time the pod volume restore is to be prepared.
-                  The server's time is used for AcceptedTimestamp
-                format: date-time
-                nullable: true
-                type: string
               completionTimestamp:
                 description: |-
                   CompletionTimestamp records the time a restore was completed.
@@ -186,19 +174,11 @@ spec:
               message:
                 description: Message is a message about the pod volume restore's status.
                 type: string
-              node:
-                description: Node is name of the node where the pod volume restore
-                  is processed.
-                type: string
               phase:
                 description: Phase is the current state of the PodVolumeRestore.
                 enum:
                 - New
-                - Accepted
-                - Prepared
                 - InProgress
-                - Canceling
-                - Canceled
                 - Completed
                 - Failed
                 type: string

config/crd/v1/bases/velero.io_restores.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: restores.velero.io
 spec:
   group: velero.io
@@ -138,13 +138,11 @@ spec:
                                     items:
                                       type: string
                                     type: array
-                                    x-kubernetes-list-type: atomic
                                 required:
                                 - key
                                 - operator
                                 type: object
                               type: array
-                              x-kubernetes-list-type: atomic
                             matchLabels:
                               additionalProperties:
                                 type: string
@@ -293,13 +291,11 @@ spec:
                           items:
                             type: string
                           type: array
-                          x-kubernetes-list-type: atomic
                       required:
                       - key
                       - operator
                       type: object
                     type: array
-                    x-kubernetes-list-type: atomic
                   matchLabels:
                     additionalProperties:
                       type: string
@@ -358,13 +354,11 @@ spec:
                             items:
                               type: string
                             type: array
-                            x-kubernetes-list-type: atomic
                         required:
                         - key
                         - operator
                         type: object
                       type: array
-                      x-kubernetes-list-type: atomic
                     matchLabels:
                       additionalProperties:
                         type: string

config/crd/v1/bases/velero.io_schedules.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: schedules.velero.io
 spec:
   group: velero.io
@@ -102,6 +102,7 @@ spec:
                       DefaultVolumesToRestic specifies whether restic should be used to take a
                       backup of all pod volumes by default.
 
+
                       Deprecated: this field is no longer used and will be removed entirely in future. Use DefaultVolumesToFsBackup instead.
                     nullable: true
                     type: boolean
@@ -214,13 +215,11 @@ spec:
                                         items:
                                           type: string
                                         type: array
-                                        x-kubernetes-list-type: atomic
                                     required:
                                     - key
                                     - operator
                                     type: object
                                   type: array
-                                  x-kubernetes-list-type: atomic
                                 matchLabels:
                                   additionalProperties:
                                     type: string
@@ -406,13 +405,11 @@ spec:
                               items:
                                 type: string
                               type: array
-                              x-kubernetes-list-type: atomic
                           required:
                           - key
                           - operator
                           type: object
                         type: array
-                        x-kubernetes-list-type: atomic
                       matchLabels:
                         additionalProperties:
                           type: string
@@ -469,13 +466,11 @@ spec:
                                 items:
                                   type: string
                                 type: array
-                                x-kubernetes-list-type: atomic
                             required:
                             - key
                             - operator
                             type: object
                           type: array
-                          x-kubernetes-list-type: atomic
                         matchLabels:
                           additionalProperties:
                             type: string
@@ -549,10 +544,6 @@ spec:
                           uploads to perform when using the uploader.
                         type: integer
                     type: object
-                  volumeGroupSnapshotLabelKey:
-                    description: VolumeGroupSnapshotLabelKey specifies the label key
-                      to group PVCs under a VGS.
-                    type: string
                   volumeSnapshotLocations:
                     description: VolumeSnapshotLocations is a list containing names
                       of VolumeSnapshotLocations associated with this backup.

config/crd/v1/bases/velero.io_serverstatusrequests.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: serverstatusrequests.velero.io
 spec:
   group: velero.io

config/crd/v1/bases/velero.io_volumesnapshotlocations.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: volumesnapshotlocations.velero.io
 spec:
   group: velero.io
@@ -57,13 +57,10 @@ spec:
                       valid secret key.
                     type: string
                   name:
-                    default: ""
                     description: |-
                       Name of the referent.
-                      This field is effectively required, but due to backwards compatibility is
-                      allowed to be empty. Instances of this type with an empty value here are
-                      almost certainly wrong.
                       More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
+                      TODO: Add other useful fields. apiVersion, kind, uid?
                     type: string
                   optional:
                     description: Specify whether the Secret or its key must be defined

config/crd/v2alpha1/bases/velero.io_datadownloads.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: datadownloads.velero.io
 spec:
   group: velero.io
@@ -92,13 +92,6 @@ spec:
                   DataMover specifies the data mover to be used by the backup.
                   If DataMover is "" or "velero", the built-in data mover will be used.
                 type: string
-              nodeOS:
-                description: NodeOS is OS of the node where the DataDownload is processed.
-                enum:
-                - auto
-                - linux
-                - windows
-                type: string
               operationTimeout:
                 description: |-
                   OperationTimeout specifies the time used to wait internal operations,
@@ -143,16 +136,6 @@ spec:
           status:
             description: DataDownloadStatus is the current status of a DataDownload.
             properties:
-              acceptedByNode:
-                description: Node is name of the node where the DataUpload is prepared.
-                type: string
-              acceptedTimestamp:
-                description: |-
-                  AcceptedTimestamp records the time the DataUpload is to be prepared.
-                  The server's time is used for AcceptedTimestamp
-                format: date-time
-                nullable: true
-                type: string
               completionTimestamp:
                 description: |-
                   CompletionTimestamp records the time a restore was completed.

config/crd/v2alpha1/bases/velero.io_datauploads.yaml

@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
+    controller-gen.kubebuilder.io/version: v0.14.0
   name: datauploads.velero.io
 spec:
   group: velero.io
@@ -87,9 +87,6 @@ spec:
                   of the CSI snapshot.
                 nullable: true
                 properties:
-                  driver:
-                    description: Driver is the driver used by the VolumeSnapshotContent
-                    type: string
                   snapshotClass:
                     description: SnapshotClass is the name of the snapshot class that
                       the volume snapshot is created with
@@ -146,17 +143,6 @@ spec:
           status:
             description: DataUploadStatus is the current status of a DataUpload.
             properties:
-              acceptedByNode:
-                description: AcceptedByNode is name of the node where the DataUpload
-                  is prepared.
-                type: string
-              acceptedTimestamp:
-                description: |-
-                  AcceptedTimestamp records the time the DataUpload is to be prepared.
-                  The server's time is used for AcceptedTimestamp
-                format: date-time
-                nullable: true
-                type: string
               completionTimestamp:
                 description: |-
                   CompletionTimestamp records the time a backup was completed.
@@ -179,13 +165,6 @@ spec:
               node:
                 description: Node is name of the node where the DataUpload is processed.
                 type: string
-              nodeOS:
-                description: NodeOS is OS of the node where the DataUpload is processed.
-                enum:
-                - auto
-                - linux
-                - windows
-                type: string
               path:
                 description: Path is the full path of the snapshot volume being backed
                   up.

config/rbac/role.yaml

@@ -8,7 +8,17 @@ rules:
   - ""
   resources:
   - persistentvolumerclaims
+  verbs:
+  - get
+- apiGroups:
+  - ""
+  resources:
   - persistentvolumes
+  verbs:
+  - get
+- apiGroups:
+  - ""
+  resources:
   - pods
   verbs:
   - get
@@ -16,18 +26,6 @@ rules:
   - velero.io
   resources:
   - backuprepositories
-  - backups
-  - backupstoragelocations
-  - datadownloads
-  - datauploads
-  - deletebackuprequests
-  - downloadrequests
-  - podvolumebackups
-  - podvolumerestores
-  - restores
-  - schedules
-  - serverstatusrequests
-  - volumesnapshotlocations
   verbs:
   - create
   - delete
@@ -40,18 +38,239 @@ rules:
   - velero.io
   resources:
   - backuprepositories/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - backups
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - backups/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - backupstoragelocations
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - backupstoragelocations/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - datadownloads
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - datadownloads/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - datauploads
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - datauploads/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - deletebackuprequests
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - deletebackuprequests/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - downloadrequests
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - downloadrequests/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - podvolumebackups
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - podvolumebackups/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - podvolumerestores
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - podvolumerestores/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - restores
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - restores/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - schedules
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - schedules/status
+  verbs:
+  - get
+  - patch
+  - update
+- apiGroups:
+  - velero.io
+  resources:
+  - serverstatusrequests
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - velero.io
+  resources:
   - serverstatusrequests/status
   verbs:
   - get
   - patch
   - update
+- apiGroups:
+  - velero.io
+  resources:
+  - volumesnapshotlocations
+  verbs:
+  - create
+  - delete
+  - get
+  - list
+  - patch
+  - update
+  - watch

design/Implemented/Extend-VolumePolicies-to-support-more-actions.md

@@ -276,7 +276,7 @@ func (v *volumeHelperImpl) ShouldPerformSnapshot(obj runtime.Unstructured, group
 
 	if !boolptr.IsSetToFalse(v.snapshotVolumes) {
 		// If the backup.Spec.SnapshotVolumes is not set, or set to true, then should take the snapshot.
-		v.logger.Infof("performing snapshot action for pv %s as the snapshotVolumes is not set to false", pv.Name)
+		v.logger.Infof("performing snapshot action for pv %s as the snapshotVolumes is not set to false")
 		return true, nil
 	}
 

design/Implemented/backup-performance-improvements.md

@@ -1,370 +0,0 @@
-# Velero Backup performance Improvements and VolumeGroupSnapshot enablement
-
-There are two different goals here, linked by a single primary missing feature in the Velero backup workflow.
-The first goal is to enhance backup performance by allowing the primary backup controller to run in multiple threads, enabling Velero to back up multiple items at the same time for a given backup.
-The second goal is to enable Velero to eventually support VolumeGroupSnapshots.
-For both of these goals, Velero needs a way to determine which items should be backed up together.
-
-This design proposal will include two development phases:
-- Phase 1 will refactor the backup workflow to identify blocks of related items that should be backed up together, and then coordinate backup hooks among items in the block.
-- Phase 2 will add multiple worker threads for backing up item blocks, so instead of backing up each block as it identified, the velero backup workflow will instead add the block to a channel and one of the workers will pick it up.
-- Actual support for VolumeGroupSnapshots is out-of-scope here and will be handled in a future design proposal, but the item block refactor introduced in Phase 1 is a primary building block for this future proposal.
-
-## Background
-Currently, during backup processing, the main Velero backup controller runs in a single thread, completely finishing the primary backup processing for one resource before moving on to the next one.
-We can improve the overall backup performance by backing up multiple items for a backup at the same time, but before we can do this we must first identify resources that need to be backed up together.
-Generally speaking, resources that need to be backed up together are resources with interdependencies -- pods with their PVCs, PVCs with their PVs, groups of pods that form a single application, CRs, pods, and other resources that belong to the same operator, etc.
-As part of this initial refactoring, once these "Item Blocks" are identified, an additional change will be to move pod hook processing up to the ItemBlock level.
-If there are multiple pods in the ItemBlock, pre-hooks for all pods will be run before backing up the items, followed by post-hooks for all pods.
-This change to hook processing is another prerequisite for future VolumeGroupSnapshot support, since supporting this will require backing up the pods and volumes together for any volumes which belong to the same group.
-Once we are backing up items by block, the next step will be to create multiple worker threads to process and back up ItemBlocks, so that we can back up multiple ItemBlocks at the same time.
-
-In looking at the different kinds of large backups that Velero must deal with, two obvious scenarios come to mind:
-1. Backups with a relatively small number of large volumes
-2. Backups with a large number of relatively small volumes.
-
-In case 1, the majority of the time spent on the backup is in the asynchronous phases -- CSI snapshot creation actions after the snaphandle exists, and DataUpload processing. In that case, parallel item processing will likely have a minimal impact on overall backup completion time.
-
-In case 2, the majority of time spent on the backup will likely be during the synchronous actions. Especially as regards CSI snapshot creation, the waiting for the VSC snaphandle to exist will result in significant passage of time with thousands of volumes. This is the sort of use case which will benefit the most from parallel item processing.
-
-## Goals
-- Identify groups of related items to back up together (ItemBlocks).
-- Manage backup hooks at the ItemBlock level rather than per-item.
-- Using worker threads, back up ItemBlocks at the same time.
-
-## Non Goals
-- Support VolumeGroupSnapshots: this is a future feature, although certain prerequisites for this enhancement are included in this proposal.
-- Process multiple backups in parallel: this is a future feature, although certain prerequisites for this enhancement are included in this proposal.
-- Refactoring plugin infrastructure to avoid RPC calls for internal plugins.
-- Restore performance improvements: this is potentially a future feature
-
-## High-Level Design
-
-### ItemBlock concept
-
-The updated design is based on a new struct/type called `ItemBlock`.
-Essentially, an `ItemBlock` is a group of items that must be backed up together in order to guarantee backup integrity.
-When we eventually split item backup across multiple worker threads, `ItemBlocks` will be kept together as the basic unit of backup.
-To facilitate this, a new plugin type, `ItemBlockAction` will allow relationships between items to be identified by velero -- any resources that must be backed up with other resources will need IBA plugins defined for them.
-Examples of `ItemBlocks` include:
-1. A pod, its mounted PVCs, and the bound PVs for those PVCs.
-2. A VolumeGroup (related PVCs and PVs) along with any pods mounting these volumes.
-3. For a ReadWriteMany PVC, the PVC, its bound PV, and all pods mounting this PVC.
-
-### Phase 1: ItemBlock processing
-- A new plugin type, `ItemBlockAction`, will be created
-- `ItemBlockAction` will contain the API method `GetRelatedItems`, which will be needed for determining which items to group together into `ItemBlocks`.
-- When processing the list of items returned from the item collector, instead of simply calling `BackupItem` on each in turn, we will use the `GetRelatedItems` API call to determine other items to include with the current item in an ItemBlock. Repeat recursively on each item returned.
-- Don't include an item in more than one ItemBlock -- if the next item from the item collector is already in a block, skip it.
-- Once ItemBlock is determined, call new func `BackupItemBlock` instead of `BackupItem`.
-- New func `BackupItemBlock` will call pre hooks for any pods in the block, then back up the items in the block (`BackupItem` will no longer run hooks directly), then call post hooks for any pods in the block.
-- The finalize phase will not be affected by the ItemBlock design, since this is just updating resources after async operations are completed on the items and there is no need to run these updates in parallel.
-
-### Phase 2: Process ItemBlocks for a single backup in multiple threads
-- Concurrent `BackupItemBlock` operations will be executed by worker threads invoked by the backup controller, which will communicate with the backup controller operation via a shared channel.
-- The ItemBlock processing loop implemented in Phase 1 will be modified to send each newly-created ItemBlock to the shared channel rather than calling `BackupItemBlock` inline.
-- Users will be able to configure the number of workers available for concurrent `BackupItemBlock` operations.
-- Access to the BackedUpItems map must be synchronized
-
-## Detailed Design
-
-### Phase 1: ItemBlock processing
-
-#### New ItemBlockAction plugin type
-
-In order for Velero to identify groups of items to back up together in an ItemBlock, we need a way to identify items which need to be backed up along with the current item. While the current `Execute` BackupItemAction method does return a list of additional items which are required by the current item, we need to know this *before* we start the item backup. To support this, we need a new plugin type, `ItemBlockAction` (IBA) with an API method, `GetRelatedItems` which Velero will call on each item as it processes. The expectation is that the registered IBA plugins will return the same items as returned as additional items by the BIA `Execute` method, with the exception that items which are not created until calling `Execute` should not be returned here, as they don't exist yet.
-
-#### Proto definition (compiled into golang by protoc)
-
-The ItemBlockAction plugin type is defined as follows:
-```
-service ItemBlockAction {
-    rpc AppliesTo(ItemBlockActionAppliesToRequest) returns (ItemBlockActionAppliesToResponse);
-    rpc GetRelatedItems(ItemBlockActionGetRelatedItemsRequest) returns (ItemBlockActionGetRelatedItemsResponse);
-}
-
-message ItemBlockActionAppliesToRequest {
-    string plugin = 1;
-}
-
-message ItemBlockActionAppliesToResponse {
-    ResourceSelector ResourceSelector = 1;
-}
-
-message ItemBlockActionGetRelatedItemsRequest {
-    string plugin = 1;
-    bytes item = 2;
-    bytes backup = 3;
-}
-
-message ItemBlockActionGetRelatedItemsResponse {
-    repeated generated.ResourceIdentifier relatedItems = 1;
-}
-```
-
-A new PluginKind, `ItemBlockAction`, will be created, and the backup process will be modified to use this plugin kind.
-
-For any BIA plugins which return additional items from `Execute()` that need to be backed up at the same time or sequentially in the same worker thread as the current items should add a new IBA plugin to return these same items (minus any which won't exist before BIA `Execute()` is called).
-This mainly applies to plugins that operate on pods which reference resources which must be backed up along with the pod and are potentially affected by pod hooks or for plugins which connect multiple pods whose volumes should be backed up at the same time.
-
-### Changes to processing item list from the Item Collector
-
-#### New structs BackupItemBlock, ItemBlock, and ItemBlockItem
-```go
-package backup
-
-type BackupItemBlock struct {
-    itemblock.ItemBlock
-    // This is a reference to the  shared itemBackupper for the backup
-    itemBackupper *itemBackupper
-}
-
-package itemblock
-
-type ItemBlock struct {
-    Log           logrus.FieldLogger
-    Items         []ItemBlockItem
-}
-
-type ItemBlockItem struct {
-    Gr           schema.GroupResource
-    Item         *unstructured.Unstructured
-    PreferredGVR schema.GroupVersionResource
-}
-```
-
-#### Current workflow
-In the `BackupWithResolvers` func, the current Velero implementation iterates over the list of items for backup returned by the Item Collector. For each item, Velero loads the item from the file created by the Item Collector, we call `backupItem`, update the GR map if successful, remove the (temporary) file containing item metadata, and update progress for the backup.
-
-#### Modifications to the loop over ItemCollector results
-The `kubernetesResource` struct used by the item collector will be modified to add an `orderedResource` bool which will be set true for all of the resources moved to the beginning for each GroupResource as a result of being ordered resources.
-In addition, an `inItemBlock` bool is added to the struct which will be set to true later when processing the list when each item is added to an ItemBlock.
-While the item collector already puts ordered resources first for each GR, there is no indication in the list which of these initial items are from the ordered resources list and which are the remaining (unordered) items.
-Velero needs to know which resources are ordered because when we process them later, the ordered resources for each GroupResource must be processed sequentially in a single ItemBlock.
-
-The current workflow within each iteration of the ItemCollector.items loop will replaced with the following:
-- (note that some of the below should be pulled out into a helper func to facilitate recursive call to it for items returned from `GetRelatedItems`.)
-- Before loop iteration, create a pointer to a `BackupItemBlock` which will represent the current ItemBlock being processed.
-- If `item` has `inItemBlock==true`, continue. This one has already been processed.
-- If current `itemBlock` is nil, create it.
-- Add `item` to `itemBlock`.
-- Load item from ItemCollector file. Close/remove file after loading (on error return or not, possibly with similar anonymous func to current impl)
-- If other versions of the same item exist (via EnableAPIGroupVersions), add these to the `itemBlock` as well (and load from ItemCollector file)
-- Get matching IBA plugins for item, call `GetRelatedItems` for each. For each item returned, get full item content from ItemCollector (if present in item list, pulling from file, removing file when done) or from cluster (if not present in item list), add item to the current block, add item to `itemsInBlock` map, and then recursively apply current step to each (i.e. call IBA method, add to block, etc.)
-- If current item and next item are both ordered items for the same GR, then continue to next item, adding to current `itemBlock`.
-- Once full ItemBlock list is generated, call `backupItemBlock(block ItemBlock)
-- Add `backupItemBlock` return values to `backedUpGroupResources` map
-
-
-#### New func `backupItemBlock`
-
-Method signature for new func `backupItemBlock` is as follows:
-```go
-func (kb *kubernetesBackupper) backupItemBlock(block BackupItemBlock) []schema.GroupResource
-```
-The return value is a slice of GRs for resources which were backed up. Velero tracks these to determine which CRDs need to be included in the backup. Note that we need to make sure we include in this not only those resources that were backed up directly, but also those backed up indirectly via additional items BIA execute returns.
-
-In order to handle backup hooks, this func will first take the input item list (`block.items`) and get a list of included pods, filtered to include only those not yet backed up (using `block.itemBackupper.backupRequest.BackedUpItems`). Iterate over this list and execute pre hooks (pulled out of `itemBackupper.backupItemInternal`) for each item.
-Now iterate over the full list (`block.items`) and call `backupItem` for each. After the first, the later items should already have been backed up, but calling a second time is harmless, since the first thing Velero does is check the `BackedUpItems` map, exiting if item is already backed up). We still need this call in case there's a plugin which returns something in `GetAdditionalItems` but forgets to return it in the `Execute` additional items return value. If we don't do this, we could end up missing items.
-
-After backing up the items in the block, we now execute post hooks using the same filtered item list we used for pre hooks, again taking the logic from `itemBackupper.backupItemInternal`).
-
-#### `itemBackupper.backupItemInternal` cleanup
-
-After implementing backup hooks in `backupItemBlock`, hook processing should be removed from `itemBackupper.backupItemInternal`.
-
-### Phase 2: Process ItemBlocks for a single backup in multiple threads
-
-#### New input field for number of ItemBlock workers
-
-The velero installer and server CLIs will get a new input field `itemBlockWorkerCount`, which will be passed along to the `backupReconciler`.
-The `backupReconciler` struct will also have this new field added. 
-
-#### Worker pool for item block processing
-
-A new type, `ItemBlockWorker` will be added which will manage a pool of worker goroutines which will process item blocks, a shared input channel for passing blocks to workers, and a WaitGroup to shut down cleanly when the reconciler exits.
-```go
-type ItemBlockWorkerPool struct {
-    itemBlockChannel chan ItemBlockInput
-    wg               *sync.WaitGroup
-    logger           logrus.FieldLogger
-}
-
-type ItemBlockInput struct {
-    itemBlock  *BackupItemBlock
-    returnChan chan ItemBlockReturn
-}
-
-type ItemBlockReturn struct {
-    itemBlock *BackupItemBlock
-    resources []schema.GroupResource
-    err       error
-}
-
-func (*p ItemBlockWorkerPool) getInputChannel() chan ItemBlockInput
-func StartItemBlockWorkerPool(context context.Context, workers int, logger logrus.FieldLogger) ItemBlockWorkerPool
-func processItemBlockWorker(context context.Context, itemBlockChannel chan ItemBlockInput, logger logrus.FieldLogger, wg *sync.WaitGroup)
-```
-
-The worker pool will be started by calling `StartItemBlockWorkerPool` in `NewBackupReconciler()`, passing in the worker count and reconciler context.
-`backupreconciler.prepareBackupRequest` will also add the input channel to the `backupRequest` so that it will be available during backup processing.
-The func `StartItemBlockWorkerPool` will create the `ItemBlockWorkerPool` with a shared buffered input channel (fixed buffer size) and start `workers` gororoutines which will each call `processItemBlockWorker`.
-The `processItemBlockWorker` func (run by the worker goroutines) will read from `itemBlockChannel`, call `BackupItemBlock` on the retrieved `ItemBlock`, and then send the return value to the retrieved `returnChan`, and then process the next block.
-
-#### Modify ItemBlock processing loop to send ItemBlocks to the worker pool rather than backing them up directly
-
-The ItemBlock processing loop implemented in Phase 1 will be modified to send each newly-created ItemBlock to the shared channel rather than calling `BackupItemBlock` inline, using a WaitGroup to manage in-process items. A separate goroutine will be created to process returns for this backup. After completion of the ItemBlock processing loop, velero will use the WaitGroup to wait for all ItemBlock processing to complete before moving forward.
-
-A simplified example of what this response goroutine might look like:
-```go
-    // omitting cancel handling, context, etc
-    ret := make(chan ItemBlockReturn)
-    wg := &sync.WaitGroup{}
-    // Handle returns
-    go func() {
-        for {
-            select {
-            case response := <-ret: // process each BackupItemBlock response
-                func() {
-                    defer wg.Done()
-                    responses = append(responses, response)
-                }()
-            case <-ctx.Done():
-                return
-            }
-        }
-    }()
-    // Simplified illustration, looping over and assumed already-determined ItemBlock list
-    for _, itemBlock := range itemBlocks {
-        wg.Add(1)
-        inputChan <- ItemBlockInput{itemBlock: itemBlock, returnChan: ret}
-    }
-    done := make(chan struct{})
-    go func() {
-        defer close(done)
-        wg.Wait()
-    }()
-    // Wait for all the ItemBlocks to be processed
-    select {
-    case <-done:
-        logger.Info("done processing ItemBlocks")
-    }
-    // responses from BackupItemBlock calls are in responses
-```
-
-When processing the responses, the main thing is to set `backedUpGroupResources[item.groupResource]=true` for each GR returned, which will give the same result as the current implementation calling items one-by-one and setting that field as needed.
-
-The ItemBlock processing loop described above will be split into two separate iterations. For the first iteration, velero will only process those items at the beginning of the loop identified as `orderedResources` -- when the groups generated from these resources are passed to the worker channel, velero will wait for the response before moving on to the next ItemBlock.
-This is to ensure that the ordered resources are processed in the required order. Once the last ordered resource is processed, the remaining ItemBlocks will be processed and sent to the worker channel without waiting for a response, in order to allow these ItemBlocks to be processed in parallel.
-The reason we must execute `ItemBlocks` with ordered resources first (and one at a time) is that this is a list of resources identified by the user as resources which must be backed up first, and in a particular order.
-
-#### Synchronize access to the BackedUpItems map
-
-Velero uses a map of BackedUpItems to track which items have already been backed up. This prevents velero from attempting to back up an item more than once, as well as guarding against creating infinite loops due to circular dependencies in the additional items returns. Since velero will now be accessing this map from the parallel goroutines, access to the map must be synchronized with mutexes.
-
-### Backup Finalize phase
-
-The finalize phase will not be affected by the ItemBlock design, since this is just updating resources after async operations are completed on the items and there is no need to run these updates in parallel.
-
-## Alternatives considered
-
-### BackpuItemAction v3 API
-
-Instead of adding a new  `ItemBlockAction` plugin type, we could add a `GetAdditionalItems` method to BackupItemAction.
-This was rejected because the new plugin type provides a cleaner interface, and keeps the function of grouping related items separate from the function of modifying item content for the backup.
-
-### Per-backup worker pool
-
-The current design makes use of a permanent worker pool, started at backup controller startup time. With this design, when we follow on with running multiple backups in parallel, the same set of workers will take ItemBlock inputs from more than one backup. Another approach that was initially considered was a temporary worker pool, created while processing a backup, and deleted upon backup completion. 
-
-#### User-visible API differences between the two approaches
-
-The main user-visible difference here is in the configuration API. For the permanent worker approach, the worker count represents the total worker count for all backups. The concurrent backup count represents the number of backups running at the same time. At any given time, though, the maximum number of worker threads backing up items concurrently is equal to the worker count. If worker count is 15 and the concurrent backup count is 3, then there will be, at most, 15 items being processed at the same time, split among up to three running backups.
-
-For the per-backup worker approach, the worker count represents the worker count for each backup. The concurrent backup count, as before, represents the number of backups running at the same time. If worker count is 15 and the concurrent backup count is 3, then there will be, at most, 45 items being processed at the same time, up to 15 for each of up to three running backups.
-#### Comparison of the two approaches
-
-- Permanent worker pool advantages:
-  - This is the more commonly-followed Kubernetes pattern. It's generally better to follow standard practices, unless there are genuine reasons for the use case to go in a different way.
-  - It's easier for users to understand the maximum number of concurrent items processed, which will have performance impact and impact on the resource requirements for the Velero pod. Users will not have to multiply the config numbers in their heads when working out how many total workers are present.
-  - It will give us more flexibility for future enhancements around concurrent backups. One possible use case: backup priority. Maybe a user wants scheduled backups to have a lower priority than user-generated backups, since a user is sitting there waiting for completion -- a shared worker pool could react to the priority by taking ItemBlocks for the higher priority backup first, which would allow a large lower-priority backup's items to be preempted by a higher-priority backup's items without needing to explicitly stop the main controller flow for that backup.
-- Per-backup worker pool advantages:
-  - Lower memory consumption than permanent worker pool, but the total memory used by a worker blocked on input will be pretty low, so if we're talking only 10-20 workers, the impact will be minimal.
-
-## Compatibility
-
-### Example IBA implementation for BIA plugins which return additional items
-
-Included below is an example of what might be required for a BIA  plugin which returns additional items.
-The code is taken from the internal velero `pod_action.go` which identifies the items required for a given pod.
-
-In this particular case, the only function of pod_action is to return additional items, so we can really just convert this plugin to an IBA plugin. If there were other actions, such as modifying the pod content on backup, then we would still need the pod action, and the related items vs. content manipulation functions would need to be separated.
-
-```go
-// PodAction implements ItemBlockAction.
-type PodAction struct {
-	log logrus.FieldLogger
-}
-
-// NewPodAction creates a new ItemAction for pods.
-func NewPodAction(logger logrus.FieldLogger) *PodAction {
-	return &PodAction{log: logger}
-}
-
-// AppliesTo returns a ResourceSelector that applies only to pods.
-func (a *PodAction) AppliesTo() (velero.ResourceSelector, error) {
-	return velero.ResourceSelector{
-		IncludedResources: []string{"pods"},
-	}, nil
-}
-
-// GetRelatedItems scans the pod's spec.volumes for persistentVolumeClaim volumes and returns a
-// ResourceIdentifier list containing references to all of the persistentVolumeClaim volumes used by
-// the pod. This ensures that when a pod is backed up, all referenced PVCs are backed up too.
-func (a *PodAction) GetRelatedItems(item runtime.Unstructured, backup *v1.Backup) (runtime.Unstructured, []velero.ResourceIdentifier, error) {
-	pod := new(corev1api.Pod)
-	if err := runtime.DefaultUnstructuredConverter.FromUnstructured(item.UnstructuredContent(), pod); err != nil {
-		return nil, errors.WithStack(err)
-	}
-
-	var relatedItems []velero.ResourceIdentifier
-	if pod.Spec.PriorityClassName != "" {
-		a.log.Infof("Adding priorityclass %s to relatedItems", pod.Spec.PriorityClassName)
-		relatedItems = append(relatedItems, velero.ResourceIdentifier{
-			GroupResource: kuberesource.PriorityClasses,
-			Name:          pod.Spec.PriorityClassName,
-		})
-	}
-
-	if len(pod.Spec.Volumes) == 0 {
-		a.log.Info("pod has no volumes")
-		return relatedItems, nil
-	}
-
-	for _, volume := range pod.Spec.Volumes {
-		if volume.PersistentVolumeClaim != nil && volume.PersistentVolumeClaim.ClaimName != "" {
-			a.log.Infof("Adding pvc %s to relatedItems", volume.PersistentVolumeClaim.ClaimName)
-
-			relatedItems = append(relatedItems, velero.ResourceIdentifier{
-				GroupResource: kuberesource.PersistentVolumeClaims,
-				Namespace:     pod.Namespace,
-				Name:          volume.PersistentVolumeClaim.ClaimName,
-			})
-		}
-	}
-
-	return relatedItems, nil
-}
-
-// API call
-func (a *PodAction) Name() string {
-	return "PodAction"
-}
-
-```
-
-
-## Implementation
-Phase 1 and Phase 2 could be implemented within the same Velero release cycle, but they need not be.
-Phase 1 is expected to be implemented in Velero 1.15.
-Phase 2 is expected to be implemented in Velero 1.16.

design/Implemented/backup-pvc-config.md

@@ -1,94 +0,0 @@
-# Backup PVC Configuration Design
-
-## Glossary & Abbreviation
-
-**Velero Generic Data Path (VGDP)**: VGDP is the collective modules that is introduced in [Unified Repository design][1]. Velero uses these modules to finish data transfer for various purposes (i.e., PodVolume backup/restore, Volume Snapshot Data Movement). VGDP modules include uploaders and the backup repository.  
-
-**Exposer**: Exposer is a module that is introduced in [Volume Snapshot Data Movement Design][2]. Velero uses this module to expose the volume snapshots to Velero node-agent pods or node-agent associated pods so as to complete the data movement from the snapshots.  
-
-**backupPVC**: The intermediate PVC created by the exposer for VGDP to access data from, see [Volume Snapshot Data Movement Design][2] for more details.  
-
-**backupPod**: The pod consumes the backupPVC so that VGDP could access data from the backupPVC, see [Volume Snapshot Data Movement Design][2] for more details.  
-
-**sourcePVC**: The PVC to be backed up, see [Volume Snapshot Data Movement Design][2] for more details. 
-
-## Background
-
-As elaberated in [Volume Snapshot Data Movement Design][2], a backupPVC may be created by the Exposer and the VGDP reads data from the backupPVC.  
-In some scenarios, users may need to configure some advanced settings of the backupPVC so that the data movement could work in best performance in their environments. Specifically:  
-- For some storage providers, when creating a read-only volume from a snapshot, it is very fast; whereas, if a writable volume is created from the snapshot, they need to clone the entire disk data, which is time consuming. If the backupPVC's `accessModes` is set as `ReadOnlyMany`, the volume driver is able to tell the storage to create a read-only volume, which may dramatically shorten the snapshot expose time. On the other hand,  `ReadOnlyMany` is not supported by all volumes. Therefore, users should be allowed to configure the `accessModes` for the backupPVC.  
-- Some storage providers create one or more replicas when creating a volume, the number of replicas is defined in the storage class. However, it doesn't make any sense to keep replicas when an intermediate volume used by the backup. Therefore, users should be allowed to configure another storage class specifically used by the backupPVC.  
-
-## Goals
-
-- Create a mechanism for users to specify various configurations for backupPVC    
-
-## Non-Goals
-
-## Solution
-
-We will use the ConfigMap specified by `velero node-agent` CLI's parameter `--node-agent-configmap` to host the backupPVC configurations.
-This configMap is not created by Velero, users should create it manually on demand. The configMap should be in the same namespace where Velero is installed. If multiple Velero instances are installed in different namespaces, there should be one configMap in each namespace which applies to node-agent in that namespace only.  
-Node-agent server checks these configurations at startup time and use it to initiate the related Exposer modules. Therefore, users could edit this configMap any time, but in order to make the changes effective, node-agent server needs to be restarted.  
-Inside the ConfigMap we will add one new kind of configuration as the data in the configMap, the name is ```backupPVC```.  
-Users may want to set different backupPVC configurations for different volumes, therefore, we define the configurations as a map and allow users to specific configurations by storage class. Specifically, the key of the map element is the storage class name used by the sourcePVC and the value is the set of configurations for the backupPVC created for the sourcePVC.   
-
-The data structure is as below:
-```go
-type Configs struct {
-	// LoadConcurrency is the config for data path load concurrency per node.
-	LoadConcurrency *LoadConcurrency `json:"loadConcurrency,omitempty"`
-
-	// LoadAffinity is the config for data path load affinity.
-	LoadAffinity []*LoadAffinity `json:"loadAffinity,omitempty"`
-
-	// BackupPVC is the config for backupPVC of snapshot data movement.
-	BackupPVC map[string]BackupPVC `json:"backupPVC,omitempty"`
-}
-
-type BackupPVC struct {
-	// StorageClass is the name of storage class to be used by the backupPVC.
-	StorageClass string `json:"storageClass,omitempty"`
-
-	// ReadOnly sets the backupPVC's access mode as read only.
-	ReadOnly bool `json:"readOnly,omitempty"`
-}
-```  
-
-### Sample
-A sample of the ConfigMap is as below:
-```json
-{
-    "backupPVC": {
-        "storage-class-1": {
-            "storageClass": "snapshot-storage-class",
-            "readOnly": true
-        },
-        "storage-class-2": {
-            "storageClass": "snapshot-storage-class"
-        },
-        "storage-class-3": {
-            "readOnly": true
-        }        
-    }
-}
-```
-
-To create the configMap, users need to save something like the above sample to a json file and then run below command:
-```
-kubectl create cm <ConfigMap name> -n velero --from-file=<json file name>
-``` 
-
-### Implementation
-The `backupPVC` is passed to the exposer and the exposer sets the related specification and create the backupPVC.  
-If `backupPVC.storageClass` doesn't exist or set as empty, the sourcePVC's storage class will be used.  
-If `backupPVC.readOnly` is set to true, `ReadOnlyMany` will be the only value set to the backupPVC's `accessModes`, otherwise, `ReadWriteOnce` is used.  
-
-Once `backupPVC.storageClass` is set, users must make sure that the specified storage class exists in the cluster and can be used the the backupPVC, otherwise, the corresponding DataUpload CR will stay in `Accepted` phase until the prepare timeout (by default 30min).   
-Once `backupPVC.readOnly` is set to true, users must make sure that the storage supports to create a `ReadOnlyMany` PVC from a snapshot, otherwise, the corresponding DataUpload CR will stay in `Accepted` phase until the prepare timeout (by default 30min).  
-
-Once above problems happen, the DataUpload CR is cancelled after prepare timeout and the backupPVC and backupPod will be deleted, so there is no way to tell the cause is one of the above problems or others.  
-To help the troubleshooting, we can add some diagnostic mechanism to discover the status of the backupPod before deleting it as a result of the prepare timeout.  
-
-[1]: unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
-[2]: volume-snapshot-data-movement/volume-snapshot-data-movement.md

design/Implemented/backup-repo-config.md

@@ -1,123 +0,0 @@
-# Backup Repository Configuration Design
-
-## Glossary & Abbreviation
-
-**Backup Storage**: The storage to store the backup data. Check [Unified Repository design][1] for details.  
-**Backup Repository**: Backup repository is layered between BR data movers and Backup Storage to provide BR related features that is introduced in [Unified Repository design][1].    
-
-## Background
-
-According to the [Unified Repository design][1] Velero uses selectable backup repositories for various backup/restore methods, i.e., fs-backup, volume snapshot data movement, etc. To achieve the best performance, backup repositories may need to be configured according to the running environments.  
-For example, if there are sufficient CPU and memory resources in the environment, users may enable compression feature provided by the backup repository, so as to achieve the best backup throughput.  
-As another example, if the local disk space is not sufficient, users may want to constraint the backup repository's cache size, so as to prevent the repository from running out of the disk space.  
-Therefore, it is worthy to allow users to configure some essential parameters of the backup repsoitories, and the configuration may vary from backup repositories.  
-
-## Goals
-
-- Create a mechanism for users to specify configurations for backup repositories  
-
-## Non-Goals
-
-## Solution
-
-### BackupRepository CRD
-
-After a backup repository is initialized, a BackupRepository CR is created to represent the instance of the backup repository. The BackupRepository's spec is a core parameter used by Unified Repo modules when interactive with the backup repsoitory. Therefore, we can add the configurations into the BackupRepository CR called ```repositoryConfig```.  
-The configurations may be different varying from backup repositories, therefore, we will not define each of the configurations explicitly. Instead, we add a map in the BackupRepository's spec to take any configuration to be set to the backup repository.  
-
-During various operations to the backup repository, the Unified Repo modules will retrieve from the map for the specific configuration that is required at that time. So even though it is specified, a configuration may not be visited/hornored if the operations don't require it for the specific backup repository, this won't bring any issue. When and how a configuration is hornored is decided by the configuration itself and should be clarified in the configuration's specification.  
-
-Below is the new BackupRepository's spec after adding the configuration map:  
-```yaml
-          spec:
-            description: BackupRepositorySpec is the specification for a BackupRepository.
-            properties:
-              backupStorageLocation:
-                description: |-
-                  BackupStorageLocation is the name of the BackupStorageLocation
-                  that should contain this repository.
-                type: string
-              maintenanceFrequency:
-                description: MaintenanceFrequency is how often maintenance should
-                  be run.
-                type: string
-              repositoryConfig:
-                additionalProperties:
-                  type: string
-                description: RepositoryConfig contains configurations for the specific
-                  repository.
-                type: object
-              repositoryType:
-                description: RepositoryType indicates the type of the backend repository
-                enum:
-                - kopia
-                - restic
-                - ""
-                type: string
-              resticIdentifier:
-                description: |-
-                  ResticIdentifier is the full restic-compatible string for identifying
-                  this repository.
-                type: string
-              volumeNamespace:
-                description: |-
-                  VolumeNamespace is the namespace this backup repository contains
-                  pod volume backups for.
-                type: string
-            required:
-            - backupStorageLocation
-            - maintenanceFrequency
-            - resticIdentifier
-            - volumeNamespace
-            type: object
-```            
-
-### BackupRepository configMap
-
-The BackupRepository CR is not created explicitly by a Velero CLI, but created as part of the backup/restore/maintenance operation if the CR doesn't exist. As a result, users don't have any way to specify the configurations before the BackupRepository CR is created.  
-Therefore, a BackupRepository configMap is introduced as a template of the configurations to be applied to the backup repository CR.  
-When the backup repository CR is created by the BackupRepository controller, the configurations in the configMap are copied to the ```repositoryConfig``` field.   
-For an existing BackupRepository CR, the configMap is never visited, if users want to modify the configuration value, they should directly edit the BackupRepository CR.  
-
-The BackupRepository configMap is created by users in velero installation namespace. The configMap name must be specified in the velero server parameter ```--backup-repository-configmap```, otherwise, it won't effect.  
-If the configMap name is specified but the configMap doesn't exist by the time of a backup repository is created, the configMap name is ignored.  
-For any reason, if the configMap doesn't effect, nothing is specified to the backup repository CR, so the Unified Repo modules use the hard-coded values to configure the backup repository.  
-
-The BackupRepository configMap supports backup repository type specific configurations, even though users can only specify one configMap.  
-So in the configMap struct, multiple entries are supported, indexed by the backup repository type. During the backup repository creation, the configMap is searched by the repository type.  
-
-### Configurations
-
-With the above mechanisms, any kind of configuration could be added. Here list the configurations defined at present:  
-```cacheLimitMB```: specifies the size limit(in MB) for the local data cache. The more data is cached locally, the less data may be downloaded from the backup storage, so the better performance may be achieved. Practically, users can specify any size that is smaller than the free space so that the disk space won't run out. This parameter is for each repository connection, that is, users could change it before connecting to the repository. If a backup repository doesn't use local cache, this parameter will be ignored. For Kopia repository, this parameter is supported.  
-```enableCompression```: specifies to enable/disable compression for a backup repsotiory. Most of the backup repositories support the data compression feature, if it is not supported by a backup repository, this parameter is ignored. Most of the backup repositories support to dynamically enable/disable compression, so this parameter is defined to be used whenever creating a write connection to the backup repository, if the dynamically changing is not supported, this parameter will be hornored only when initializing the backup repository. For Kopia repository, this parameter is supported and can be dynamically modified.  
-
-### Sample
-Below is an example of the BackupRepository configMap with the configurations:     
-```yaml
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: <config-name>
-  namespace: velero
-data:
-  <repository-type-1>: |
-    {
-      "cacheLimitMB": 2048,
-      "enableCompression": true    
-    }
-  <repository-type-2>: |
-    {
-      "cacheLimitMB": 1,
-      "enableCompression": false    
-    }        
-```
-
-To create the configMap, users need to save something like the above sample to a file and then run below commands:  
-```
-kubectl apply -f <yaml file name>
-```  
-
-
-
-[1]: unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md

design/Implemented/clean_artifacts_in_csi_flow.md

@@ -1,374 +0,0 @@
-# Design to clean the artifacts generated in the CSI backup and restore workflows
-
-## Terminology
-
-* VSC: VolumeSnapshotContent
-* VS: VolumeSnapshot
-
-## Abstract
-* The design aims to delete the unnecessary VSs and VSCs generated during CSI backup and restore process. 
-* The design stop creating related VSCs during backup syncing.
-
-## Background
-In the current CSI backup and restore workflows, please notice the CSI B/R workflows means only using the CSI snapshots in the B/R, not including the CSI snapshot data movement workflows, some generated artifacts are kept after the backup or the restore process completion.
-
-Some of them are kept due to design, for example, the VolumeSnapshotContents generated during the backup are kept to make sure the backup deletion can clean the snapshots in the storage providers.
-
-Some of them are kept by accident, for example, after restore, two VolumeSnapshotContents are generated for the same VolumeSnapshot. One is from the backup content, and one is dynamically generated from the restore's VolumeSnapshot.
-
-The design aims to clean the unnecessary artifacts, and make the CSI B/R workflow more concise and reliable.
-
-## Goals
-- Clean the redundant VSC generated during CSI backup and restore.
-- Remove the VSCs in the backup sync process.
-
-## Non Goals
-- There were some discussion about whether Velero backup should include VSs and VSCs not generated in during the backup. By far, the conclusion is not including them is a better option. Although that is a useful enhancement, that is not included this design.
-- Delete all the CSI-related metadata files in the BSL is not the aim of this design. 
-
-## Detailed Design
-### Backup
-During backup, the main change is the backup-generated VSCs should not kept anymore.
-
-The reasons is we don't need them to ensure the snapshots clean up during backup deletion. Please reference to the [Backup Deletion section](#backup-deletion) section for detail.
-
-As a result, we can simplify the VS deletion logic in the backup. Before, we need to not only delete the VS, but also recreate a static VSC pointing a non-exiting VS.
-
-The deletion code in VS BackupItemAction can be simplify to the following:
-
-``` go
-	if backup.Status.Phase == velerov1api.BackupPhaseFinalizing ||
-		backup.Status.Phase == velerov1api.BackupPhaseFinalizingPartiallyFailed {
-		p.log.
-			WithField("Backup", fmt.Sprintf("%s/%s", backup.Namespace, backup.Name)).
-			WithField("BackupPhase", backup.Status.Phase).Debugf("Cleaning VolumeSnapshots.")
-
-		if vsc == nil {
-			vsc = &snapshotv1api.VolumeSnapshotContent{}
-		}
-
-		csi.DeleteReadyVolumeSnapshot(*vs, *vsc, p.crClient, p.log)
-		return item, nil, "", nil, nil
-	}
-
-
-func DeleteReadyVolumeSnapshot(
-	vs snapshotv1api.VolumeSnapshot,
-	vsc snapshotv1api.VolumeSnapshotContent,
-	client crclient.Client,
-	logger logrus.FieldLogger,
-) {
-	logger.Infof("Deleting Volumesnapshot %s/%s", vs.Namespace, vs.Name)
-	if vs.Status == nil ||
-		vs.Status.BoundVolumeSnapshotContentName == nil ||
-		len(*vs.Status.BoundVolumeSnapshotContentName) <= 0 {
-		logger.Errorf("VolumeSnapshot %s/%s is not ready. This is not expected.",
-			vs.Namespace, vs.Name)
-		return
-	}
-
-	if vs.Status != nil && vs.Status.BoundVolumeSnapshotContentName != nil {
-		// Patch the DeletionPolicy of the VolumeSnapshotContent to set it to Retain.
-		// This ensures that the volume snapshot in the storage provider is kept.
-		if err := SetVolumeSnapshotContentDeletionPolicy(
-			vsc.Name,
-			client,
-			snapshotv1api.VolumeSnapshotContentRetain,
-		); err != nil {
-			logger.Warnf("Failed to patch DeletionPolicy of volume snapshot %s/%s",
-				vs.Namespace, vs.Name)
-			return
-		}
-
-		if err := client.Delete(context.TODO(), &vsc); err != nil {
-			logger.Warnf("Failed to delete the VSC %s: %s", vsc.Name, err.Error())
-		}
-	}
-	if err := client.Delete(context.TODO(), &vs); err != nil {
-		logger.Warnf("Failed to delete volumesnapshot %s/%s: %v", vs.Namespace, vs.Name, err)
-	} else {
-		logger.Infof("Deleted volumesnapshot with volumesnapshotContent %s/%s",
-			vs.Namespace, vs.Name)
-	}
-}
-```
-
-### Restore
-
-#### Restore the VolumeSnapshotContent
-The current behavior of VSC restoration is that the VSC from the backup is restore, and the restored VS also triggers creating a new VSC dynamically.
-
-Two VSCs created for the same VS in one restore seems not right.
-
-Skip restore the VSC from the backup is not a viable alternative, because VSC may reference to a [snapshot create secret](https://kubernetes-csi.github.io/docs/secrets-and-credentials-volume-snapshot-class.html?highlight=snapshotter-secret-name#createdelete-volumesnapshot-secret).
-
-If the `SkipRestore` is set true in the restore action's result, the secret returned in the additional items is ignored too.
-
-As a result, restore the VSC from the backup, and setup the VSC and the VS's relation is a better choice.
-
-Another consideration is the VSC name should not be the same as the backed-up VSC's, because the older version Velero's restore and backup keep the VSC after completion.
-
-There's high possibility that the restore will fail due to the VSC already exists in the cluster.
-
-Multiple restores of the same backup will also meet the same problem.
-
-The proposed solution is using the restore's UID and the VS's name to generate sha256 hash value as the new VSC name. Both the VS and VSC RestoreItemAction can access those UIDs, and it will avoid the conflicts issues.
-
-The restored VS name also shares the same generated name.
-
-The VS-referenced VSC name and the VSC's snapshot handle name are in their status.
-
-Velero restore process purges the restore resources' metadata and status before running the RestoreItemActions.
-
-As a result, we cannot read these information in the VS and VSC RestoreItemActions.
-
-Fortunately, RestoreItemAction input parameters includes the `ItemFromBackup`. The status is intact in `ItemFromBackup`.
-
-``` go
-func (p *volumeSnapshotRestoreItemAction) Execute(
-	input *velero.RestoreItemActionExecuteInput,
-) (*velero.RestoreItemActionExecuteOutput, error) {
-	p.log.Info("Starting VolumeSnapshotRestoreItemAction")
-
-	if boolptr.IsSetToFalse(input.Restore.Spec.RestorePVs) {
-		p.log.Infof("Restore %s/%s did not request for PVs to be restored.",
-			input.Restore.Namespace, input.Restore.Name)
-		return &velero.RestoreItemActionExecuteOutput{SkipRestore: true}, nil
-	}
-
-	var vs snapshotv1api.VolumeSnapshot
-	if err := runtime.DefaultUnstructuredConverter.FromUnstructured(
-		input.Item.UnstructuredContent(), &vs); err != nil {
-		return &velero.RestoreItemActionExecuteOutput{},
-			errors.Wrapf(err, "failed to convert input.Item from unstructured")
-	}
-
-	var vsFromBackup snapshotv1api.VolumeSnapshot
-	if err := runtime.DefaultUnstructuredConverter.FromUnstructured(
-		input.ItemFromBackup.UnstructuredContent(), &vsFromBackup); err != nil {
-		return &velero.RestoreItemActionExecuteOutput{},
-			errors.Wrapf(err, "failed to convert input.Item from unstructured")
-	}
-
-	// If cross-namespace restore is configured, change the namespace
-	// for VolumeSnapshot object to be restored
-	newNamespace, ok := input.Restore.Spec.NamespaceMapping[vs.GetNamespace()]
-	if !ok {
-		// Use original namespace
-		newNamespace = vs.Namespace
-	}
-
-	if csiutil.IsVolumeSnapshotExists(newNamespace, vs.Name, p.crClient) {
-		p.log.Debugf("VolumeSnapshot %s already exists in the cluster. Return without change.", vs.Namespace+"/"+vs.Name)
-		return &velero.RestoreItemActionExecuteOutput{UpdatedItem: input.Item}, nil
-	}
-
-	newVSCName := generateSha256FromRestoreAndVsUID(string(input.Restore.UID), string(vsFromBackup.UID))
-	// Reset Spec to convert the VolumeSnapshot from using
-	// the dynamic VolumeSnapshotContent to the static one.
-	resetVolumeSnapshotSpecForRestore(&vs, &newVSCName)
-
-	// Reset VolumeSnapshot annotation. By now, only change
-	// DeletionPolicy to Retain.
-	resetVolumeSnapshotAnnotation(&vs)
-
-	vsMap, err := runtime.DefaultUnstructuredConverter.ToUnstructured(&vs)
-	if err != nil {
-		p.log.Errorf("Fail to convert VS %s to unstructured", vs.Namespace+"/"+vs.Name)
-		return nil, errors.WithStack(err)
-	}
-
-	p.log.Infof(`Returning from VolumeSnapshotRestoreItemAction with 
-		no additionalItems`)
-
-	return &velero.RestoreItemActionExecuteOutput{
-		UpdatedItem:     &unstructured.Unstructured{Object: vsMap},
-		AdditionalItems: []velero.ResourceIdentifier{},
-	}, nil
-}
-
-// generateSha256FromRestoreAndVsUID Use the restore UID and the VS UID to generate the new VSC name.
-// By this way, VS and VSC RIA action can get the same VSC name.
-func generateSha256FromRestoreAndVsUID(restoreUID string, vsUID string) string {
-	sha256Bytes := sha256.Sum256([]byte(restoreUID + "/" + vsUID))
-	return "vsc-" + hex.EncodeToString(sha256Bytes[:])
-}
-```
-
-#### Restore the VolumeSnapshot
-``` go
-// Execute restores a VolumeSnapshotContent object without modification
-// returning the snapshot lister secret, if any, as additional items to restore.
-func (p *volumeSnapshotContentRestoreItemAction) Execute(
-	input *velero.RestoreItemActionExecuteInput,
-) (*velero.RestoreItemActionExecuteOutput, error) {
-	if boolptr.IsSetToFalse(input.Restore.Spec.RestorePVs) {
-		p.log.Infof("Restore did not request for PVs to be restored %s/%s",
-			input.Restore.Namespace, input.Restore.Name)
-		return &velero.RestoreItemActionExecuteOutput{SkipRestore: true}, nil
-	}
-
-	p.log.Info("Starting VolumeSnapshotContentRestoreItemAction")
-
-	var vsc snapshotv1api.VolumeSnapshotContent
-	if err := runtime.DefaultUnstructuredConverter.FromUnstructured(
-		input.Item.UnstructuredContent(), &vsc); err != nil {
-		return &velero.RestoreItemActionExecuteOutput{},
-			errors.Wrapf(err, "failed to convert input.Item from unstructured")
-	}
-
-	var vscFromBackup snapshotv1api.VolumeSnapshotContent
-	if err := runtime.DefaultUnstructuredConverter.FromUnstructured(
-		input.ItemFromBackup.UnstructuredContent(), &vscFromBackup); err != nil {
-		return &velero.RestoreItemActionExecuteOutput{},
-			errors.Errorf(err.Error(), "failed to convert input.ItemFromBackup from unstructured")
-	}
-
-	// If cross-namespace restore is configured, change the namespace
-	// for VolumeSnapshot object to be restored
-	newNamespace, ok := input.Restore.Spec.NamespaceMapping[vsc.Spec.VolumeSnapshotRef.Namespace]
-	if ok {
-		// Update the referenced VS namespace to the mapping one.
-		vsc.Spec.VolumeSnapshotRef.Namespace = newNamespace
-	}
-
-	// Reset VSC name to align with VS.
-	vsc.Name = generateSha256FromRestoreAndVsUID(string(input.Restore.UID), string(vscFromBackup.Spec.VolumeSnapshotRef.UID))
-
-	// Reset the ResourceVersion and UID of referenced VolumeSnapshot.
-	vsc.Spec.VolumeSnapshotRef.ResourceVersion = ""
-	vsc.Spec.VolumeSnapshotRef.UID = ""
-
-	// Set the DeletionPolicy to Retain to avoid VS deletion will not trigger snapshot deletion
-	vsc.Spec.DeletionPolicy = snapshotv1api.VolumeSnapshotContentRetain
-
-	if vscFromBackup.Status != nil && vscFromBackup.Status.SnapshotHandle != nil {
-		vsc.Spec.Source.VolumeHandle = nil
-		vsc.Spec.Source.SnapshotHandle = vscFromBackup.Status.SnapshotHandle
-	} else {
-		p.log.Errorf("fail to get snapshot handle from VSC %s status", vsc.Name)
-		return nil, errors.Errorf("fail to get snapshot handle from VSC %s status", vsc.Name)
-	}
-
-	additionalItems := []velero.ResourceIdentifier{}
-	if csi.IsVolumeSnapshotContentHasDeleteSecret(&vsc) {
-		additionalItems = append(additionalItems,
-			velero.ResourceIdentifier{
-				GroupResource: schema.GroupResource{Group: "", Resource: "secrets"},
-				Name:          vsc.Annotations[velerov1api.PrefixedSecretNameAnnotation],
-				Namespace:     vsc.Annotations[velerov1api.PrefixedSecretNamespaceAnnotation],
-			},
-		)
-	}
-
-	vscMap, err := runtime.DefaultUnstructuredConverter.ToUnstructured(&vsc)
-	if err != nil {
-		return nil, errors.WithStack(err)
-	}
-
-	p.log.Infof("Returning from VolumeSnapshotContentRestoreItemAction with %d additionalItems",
-		len(additionalItems))
-	return &velero.RestoreItemActionExecuteOutput{
-		UpdatedItem:     &unstructured.Unstructured{Object: vscMap},
-		AdditionalItems: additionalItems,
-	}, nil
-}
-```
-
-
-### Backup Sync
-csi-volumesnapshotclasses.json, csi-volumesnapshotcontents.json, and csi-volumesnapshots.json are CSI-related metadata files in the BSL for each backup.
-
-csi-volumesnapshotcontents.json and csi-volumesnapshots.json are not needed anymore, but csi-volumesnapshotclasses.json is still needed.
-
-One concrete scenario is that a backup is created in cluster-A, then the backup is synced to cluster-B, and the backup is deleted in the cluster-B. In this case, we don't have a chance to create the VS and VSC needed VolumeSnapshotClass.
-
-The VSC deletion workflow proposed by this design needs to create the VSC first. If the VSC's referenced VolumeSnapshotClass doesn't exist in cluster, the creation of VSC will fail.
-
-As a result, the VolumeSnapshotClass should still be synced in the backup sync process.
-
-### Backup Deletion
-Two factors are worthy for consideration for the backup deletion change:
-* Because the VSCs generated by the backup are not synced anymore, and the VSCs generated during the backup will not be kept too. The backup deletion needs to generate a VSC, then deletes it to make sure the snapshots in the storage provider are clean too.
-* The VSs generated by the backup are already deleted in the backup process, we don't need a DeleteItemAction for the VS anymore. As a result, the `velero.io/csi-volumesnapshot-delete` plugin is unneeded.
-
-For the VSC DeleteItemAction, we need to generate a VSC. Because we only care about the snapshot deletion, we don't need to create a VS associated with the VSC.
-
-Create a static VSC, then point it to a pseudo VS, and reference to the snapshot handle should be enough.
-
-To avoid the created VSC conflict with older version Velero B/R generated ones, the VSC name is set to `vsc-uuid`.
-
-The following is an example of the implementation.
-``` go
-	uuid, err := uuid.NewRandom()
-	if err != nil {
-		p.log.WithError(err).Errorf("Fail to generate the UUID to create VSC %s", snapCont.Name)
-		return errors.Wrapf(err, "Fail to generate the UUID to create VSC %s", snapCont.Name)
-	}
-	snapCont.Name = "vsc-" + uuid.String()
-
-	snapCont.Spec.DeletionPolicy = snapshotv1api.VolumeSnapshotContentDelete
-
-	snapCont.Spec.Source = snapshotv1api.VolumeSnapshotContentSource{
-		SnapshotHandle: snapCont.Status.SnapshotHandle,
-	}
-
-	snapCont.Spec.VolumeSnapshotRef = corev1api.ObjectReference{
-		APIVersion: snapshotv1api.SchemeGroupVersion.String(),
-		Kind:       "VolumeSnapshot",
-		Namespace:  "ns-" + string(snapCont.UID),
-		Name:       "name-" + string(snapCont.UID),
-	}
-
-	snapCont.ResourceVersion = ""
-
-	if err := p.crClient.Create(context.TODO(), &snapCont); err != nil {
-		return errors.Wrapf(err, "fail to create VolumeSnapshotContent %s", snapCont.Name)
-	}
-
-	// Read resource timeout from backup annotation, if not set, use default value.
-	timeout, err := time.ParseDuration(
-		input.Backup.Annotations[velerov1api.ResourceTimeoutAnnotation])
-	if err != nil {
-		p.log.Warnf("fail to parse resource timeout annotation %s: %s",
-			input.Backup.Annotations[velerov1api.ResourceTimeoutAnnotation], err.Error())
-		timeout = 10 * time.Minute
-	}
-	p.log.Debugf("resource timeout is set to %s", timeout.String())
-
-	interval := 5 * time.Second
-
-	// Wait until VSC created and ReadyToUse is true.
-	if err := wait.PollUntilContextTimeout(
-		context.Background(),
-		interval,
-		timeout,
-		true,
-		func(ctx context.Context) (bool, error) {
-			tmpVSC := new(snapshotv1api.VolumeSnapshotContent)
-			if err := p.crClient.Get(ctx, crclient.ObjectKeyFromObject(&snapCont), tmpVSC); err != nil {
-				return false, errors.Wrapf(
-					err, "failed to get VolumeSnapshotContent %s", snapCont.Name,
-				)
-			}
-
-			if tmpVSC.Status != nil && boolptr.IsSetToTrue(tmpVSC.Status.ReadyToUse) {
-				return true, nil
-			}
-
-			return false, nil
-		},
-	); err != nil {
-		return errors.Wrapf(err, "fail to wait VolumeSnapshotContent %s becomes ready.", snapCont.Name)
-	}
-```
-
-## Security Considerations
-Security is not relevant to this design.
-
-## Compatibility
-In this design, no new information is added in backup and restore. As a result, this design doesn't have any compatibility issue.
-
-## Open Issues
-Please notice the CSI snapshot backup and restore mechanism not supporting all file-store-based volume, e.g. Azure Files, EFS or vSphere CNS File Volume. Only block-based volumes are supported.
-Refer to [this comment](https://github.com/vmware-tanzu/velero/issues/3151#issuecomment-2623507686) for more details.

design/Implemented/handle-backup-of-volumes-by-resources-filters.md

@@ -86,7 +86,7 @@ volumePolicies:
     # capacity condition matches the volumes whose capacity falls into the range
     capacity: "0,100Gi"
     csi:
-      driver: ebs.csi.aws.com
+      driver: aws.ebs.csi.driver
       fsType: ext4
     storageClass:
     - gp2
@@ -174,7 +174,7 @@ data:
   - conditions:
       capacity: "0,100Gi"
       csi:
-        driver: ebs.csi.aws.com
+        driver: aws.ebs.csi.driver
         fsType: ext4
       storageClass:
       - gp2

design/Implemented/include-exclude-in-resource-policy.md

@@ -1,82 +0,0 @@
-# Proposal to add include exclude policy to resource policy
-
-This enhancement will allow the user to set include and exclude filters for resources in a resource policy configmap, so that
-these filters are reusable and the user will not need to set them each time they create a backup.
-
-## Background
-As mentioned in issue [#8610](https://github.com/vmware-tanzu/velero/issues/8610).  When there's a long list of resources 
-to include or exclude in a backup, it can be cumbersome to set them each time a backup is created.  There's a requirement to
-set these filters in a separate data structure so that they can be reused in multiple backups.
-
-## High-Level Design
-We may extend the data structure of resource policy to add `includeExcludePolicy`, which include the include and exclude filters 
-in the BackupSpec.  When the user creates a backup which references the resource policy config `velero backup create --resource-policies-configmap <configmap-name>`,
-the filters in "includeExcludePolicy" will take effect to filter the resources when velero collects the resources to backup.
-
-## Detailed Design
-
-### Data Structure
-The map `includeExcludePolicy` contains four fields `includedClusterScopedResources`, `excludedClusterScopedResources`, 
-`includedNamespaceScopedResources`,`excludedNamespaceScopedResources`.  These filters work exactly as the filters defined BackupSpec with
-the same names.  An example of the policy looks like:
-```yaml
-#omitted other irrelevant fields like 'version', 'volumePolicies'
-includeExcludePolicy:
-  includedClusterScopedResources:
-    - "cr"
-    - "crd"
-    - "pv"
-  excludedClusterScopedResources:
-    - "volumegroupsnapshotclass"
-    - "ingressclass"
-  includedNamespaceScopedResources:
-    - "pod"
-    - "service"
-    - "deployment"
-    - "pvc"
-  excludedNamespaceScopedResources:
-    - "configmap"
-```
-These filters are in the form of scoped include/exclude filters, which by design will not work with the "old" resource filters.
-Therefore, when a Backup references a resource policy configmap which has `includeExcludePolicy`, and at the same time it has 
-the "old" resource filters, i.e. `includedResources`, `excludedResources`, `includeClusterResources` set in the BackupSpec, the
-Backup will fail with a validation error.
-
-### Priorities 
-A user may set the include/exclude filters in Backupspec and also in the resource policy configmap.  In this case, the filters 
-in both the Backupspec and the resource policy configmap will take effect.  When there's a conflict, the filters in the Backupspec 
-will take precedence.  For example, if resource X is in the list of `includedNamespaceScopedResources` filter in the Backupspec, but 
-it's also in the list of `excludedClusterScopedResources` in the resource policy configmap, then resource X will be included in the backup.
-In this way, users can set the filters in the resource policy configmap to cover most of their use cases, and then override them 
-in the Backupspec when needed.
-
-### Implementation
-In addition to the data structure change, we will need to implement the following changes:
-1. A new function `CombineWithPolicy` will be added to the struct `ScopeIncludesExcludes`, which will combine the include/exclude filters
-in the resource policy configmap with the include/exclude filters in the Backupspec:  
-```go
-func (ie *ScopeIncludesExcludes) CombineWithPolicy(policy resourcepolicies.IncludeExcludePolicy) {
-	mapFunc := scopeResourceMapFunc(ie.helper)
-	for _, item := range policy.ExcludedNamespaceScopedResources {
-		resolvedItem := mapFunc(item, true)
-		if resolvedItem == "" {
-			continue
-		}
-		if !ie.ShouldInclude(resolvedItem) && !ie.ShouldExclude(resolvedItem) {
-			// The existing includeExcludes in the struct has higher priority, therefore, we should only add the item to the filter
-			// when the struct does not include this item and this item is not yet in the excludes filter.
-			ie.namespaceScopedResourceFilter.excludes.Insert(resolvedItem)
-		}
-		
-	}
-.....
-```
-This function will be called in the `kubernetesBackupper.BackupWithResolvers` function, to make sure the combined `ScopeIncludesExcludes` 
-filter will be assigned to the `ResourceIncludesExcludes` filter of the Backup request.
-
-2. Extra validation code will be added to the function `prepareBackupRequest` of `BackupReconciler` to check if there are "old"
-Resource filters in the BackupSpec when the Backup references a resource policy configmap which has `includeExcludePolicy`.
-
-## Alternatives Considered
-We may put `includeExcludePolicy` in a separate configmap, but it will require adding extra field to BackupSpec to reference the configmap,
-which is not necessary.

design/Implemented/multiple-arch-build-with-windows.md

@@ -1,122 +0,0 @@
-# Multi-arch Build and Windows Build Support
-
-## Background
-
-At present, Velero images could be built for linux-amd64 and linux-arm64. We need to support other platforms, i.e., windows-amd64.  
-At present, for linux image build, we leverage Buildkit's `--platform` option to create the image manifest list in one build call. However, it is a limited way and doesn't fully support all multi-arch scenarios. Specifically, since the build is done in one call with the same parameters, it is impossbile to build images with different configurations (e.g., Windows build requires a different Dockerfile).   
-At present, Velero by default build images locally, or no image or manifest is pushed to registry. However, docker doesn't support multi-arch build locally. We need to clarify the behavior of local build.    
-
-## Goals
-- Refactor the `make container` process to fully support multi-arch build
-- Add Windows build to the existing build process
-- Clarify the behavior of local build with multi-arch build capabilities
-- Don't change the pattern of the final image tag to be used by users
-
-## Non-Goals
-- There may be some workarounds to make the multi-arch image/manifest fully available locally. These workarounds will not be adopted, so local build always build single-arch images
-
-## Local Build
-
-For local build, two values of `--output` parameter for `docker buildx build` are supported:
-- `docker`: a docker format image is built, but the image is only built for the platform (`<os>/<arch>`) as same as the building env. E.g., when building from linux-amd64 env, a single manifest of linux-amd64 is created regardless how the input parameters are configured.  
-- `tar`: one or more images are built as tarballs according to the input platform (`<os>/<arch>`) parameters. Specifically, one tarball is generated for each platform. The build process is the same with the `Build Separate Manifests` of `Push Build` as detailed below. Merely, the `--output` parameter diffs, as `type=tar;dest=<tarball generated path>`. The tarball is generated to the `_output` folder and named with the platform info, e.g., `_output/velero-main-linux-amd64.tar`.  
-
-## Push Build
-
-For push build, the `--output` parameter for `docker buildx build` is always `registry`. And build will go according to the input parameters and create multi-arch manifest lists.    
-
-### Step 1: Build Separate Manifests
-
-Instead of specifying multiple platforms (`<os>/<arch>`) to `--platform` option, we add multiple `container-%` targets in Makefile and each target builds one platform representively.  
-
-The goal here is to build multiple manifests through the multiple targets. However, `docker buildx build` by default creates a manifest list even though there is only one element in `--platform`. Therefore, two flags `--provenance=false` and `--sbom=false` will be set additionally to force `docker buildx build` to create manifests.  
-
-Each manifest has a unique tag, the OS type and arch is added to the tag, in the pattern `$(REGISTRY)/$(BIN):$(VERSION)-$(OS)-$(ARCH)`. For example, `velero/velero:main-linux-amd64`.  
-
-All the created manifests will be pushed to registry so that the all-in-one manifest list could be created.  
-
-### Step 2: Create All-In-One Manifest List
-
-The next step is to create a manifest list to include all the created manifests. This could be done by `docker manifest create` command, the tags created and pushed at Step 1 are passed to this command.  
-A tag is also created for the manifest list, in the pattern `$(REGISTRY)/$(BIN):$(VERSION)`. For example, `velero/velero:main`.  
-
-### Step 3: Push All-In-One Manifest List
-
-The created manifest will be pushed to registry by command `docker manifest push`.  
-
-## Input Parameters
-
-Below are the input parameters that are configurable to meet different build purposes during Dev and release cycle:
-- BUILD_OUTPUT_TYPE: the type of output for the build, i.e., `docker`, `tar`, `registry`, while `docker` and `tar` is for local build; `registry` means push build. Default value is `docker`  
-- BUILD_OS: which types of OS should be built for. Multiple values are accepted, e.g., `linux,windows`. Default value is `linux`  
-- BUILD_ARCH: which types of architecture should be built for. Multiple values are accepted, e.g., `amd64,arm64`. Default value is `amd64`  
-- BUILDX_INSTANCE: an existing buildx instance to be used by the build. Default value is <empty> which indicates the build to create a new buildx instance  
-
-## Windows Build
-
-Windows container images vary from Windows OS versions, e.g., `ltsc2022` for Windows server 2022 and `1809` for Windows server 2019. Images for different OS versions should be built separately.  
-Therefore, separate build targets are added for each OS version, like `container-windows-%`.  
-For the same reason, a new input parameter is added, `BUILD_WINDOWS_VERSION`. The default value is `ltsc2022`. Windows server 2022 is the only base image we will deliver officially, Windows server 2019 is not supported. In future, we may need to support Windows server 2025 base image.  
-For local build to tar, the Windows OS version is also added to the name of the tarball, e.g., `_output/velero-main-windows-ltsc2022-amd64.tar`.  
-
-At present, Windows container image only supports `amd64` as the architecture, so `BUILD_ARCH` is ignored for Windows.  
-
-The Windows manifests need to be annotated with os type, arch, and os version. This will be done through `docker manifest annotate` command.  
-
-## Use Malti-arch Images
-
-In order to use the images, the manifest list's tag should be provided to `velero install` command or helm, the individual manifests are covered by the manifest list. During launch time, the container engine will load the right image to the container according to the platform of the running node.  
-
-## Build Samples
-
-**Local build to docker**
-```
-make container
-```
-The built image could be listed by `docker image ls`.  
-
-**Local build for linux-amd64 and windows-amd64 to tar**
-```
-BUILD_OUTPUT_TYPE=tar BUILD_OS=linux,windows make container
-```
-Under `_output` directory, below files are generated:  
-```
-velero-main-linux-amd64.tar
-velero-main-windows-ltsc2022-amd64.tar
-``` 
-
-**Local build for linux-amd64, linux-arm64 and windows-amd64 to tar**
-```
-BUILD_OUTPUT_TYPE=tar BUILD_OS=linux,windows BUILD_ARCH=amd64,arm64 make container
-```
-Under `_output` directory, below files are generated:  
-```
-velero-main-linux-amd64.tar
-velero-main-linux-arm64.tar
-velero-main-windows-ltsc2022-amd64.tar
-```
-
-**Push build for linux-amd64 and windows-amd64**  
-Prerequisite: login to registry, e.g., through `docker login`  
-```
-BUILD_OUTPUT_TYPE=registry REGISTRY=<registry> BUILD_OS=linux,windows make container
-```
-Nothing is available locally, in the registry 3 tags are available:
-```
-velero/velero:main
-velero/velero:main-windows-ltsc2022-amd64
-velero/velero:main-linux-amd64
-```
-
-**Push build for linux-amd64, linux-arm64 and windows-amd64**  
-Prerequisite: login to registry, e.g., through `docker login` 
-```
-BUILD_OUTPUT_TYPE=registry REGISTRY=<registry> BUILD_OS=linux,windows BUILD_ARCH=amd64,arm64 make container
-```
-Nothing is available locally, in the registry 4 tags are available:
-```
-velero/velero:main
-velero/velero:main-windows-ltsc2022-amd64
-velero/velero:main-linux-amd64
-velero/velero:main-linux-arm64
-```

design/Implemented/node-agent-affinity.md

@@ -26,18 +26,18 @@ Therefore, in order to improve the compatibility, it is worthy to configure the
 
 ## Non-Goals
 - It is also beneficial to support VGDP instances affinity for PodVolume backup/restore, however, it is not possible since VGDP instances for PodVolume backup/restore should always run in the node where the source/target pods are created.  
-- It is also beneficial to support VGDP instances affinity for data movement restores, however, it is not possible in some cases. For example, when the `volumeBindingMode` in the StorageClass is `WaitForFirstConsumer`, the restore volume must be mounted in the node where the target pod is scheduled, so the VGDP instance must run in the same node. On the other hand, considering the fact that restores may not frequently and centrally run, we will not support data movement restores.  
-- As elaborated in the [Volume Snapshot Data Movement Design][2], the Exposer may take different ways to expose snapshots, i.e., through backup pods (this is the only way supported at present). The implementation section below only considers this approach currently, if a new expose method is introduced in future, the definition of the affinity configurations and behaviors should still work, but we may need a new implementation.  
+- It is also beneficial to support VGDP instances affinity for data movement restores, however, it is not possible in some cases. For example, when the `volumeBindingMode` in the storageclass is `WaitForFirstConsumer`, the restore volume must be mounted in the node where the target pod is scheduled, so the VGDP instance must run in the same node. On the other hand, considering the fact that restores may not frequently and centrally run, we will not support data movement restores.  
+- As elaberated in the [Volume Snapshot Data Movement Design][2], the Exposer may take different ways to expose snapshots, i.e., through backup pods (this is the only way supported at present). The implementation section below only considers this approach currently, if a new expose method is introduced in future, the definition of the affinity configurations and behaviors should still work, but we may need a new implementation.  
 
 ## Solution
 
-We will use the ConfigMap specified by `velero node-agent` CLI's parameter `--node-agent-configmap` to host the node affinity configurations.
+We will use the ```node-agent-config``` configMap to host the node affinity configurations.
 This configMap is not created by Velero, users should create it manually on demand. The configMap should be in the same namespace where Velero is installed. If multiple Velero instances are installed in different namespaces, there should be one configMap in each namespace which applies to node-agent in that namespace only.  
 Node-agent server checks these configurations at startup time and use it to initiate the related VGDP modules. Therefore, users could edit this configMap any time, but in order to make the changes effective, node-agent server needs to be restarted.  
-Inside the ConfigMap we will add one new kind of configuration as the data in the configMap, the name is ```loadAffinity```.  
+Inside ```node-agent-config``` configMap we will add one new kind of configuration as the data in the configMap, the name is ```loadAffinity```.  
 Users may want to set different LoadAffinity configurations according to different conditions (i.e., for different storages represented by StorageClass, CSI driver, etc.), so we define ```loadAffinity``` as an array. This is for extensibility consideration, at present, we don't implement multiple configurations support, so if there are multiple configurations, we always take the first one in the array.  
 
-The data structure is as below:
+The data structure for ```node-agent-config``` is as below:
 ```go
 type Configs struct {
 	// LoadConcurrency is the config for load concurrency per node.
@@ -63,7 +63,7 @@ Anti-affinity configuration means preventing VGDP instances running in the nodes
 - It could be defined by `MatchExpressions` of `metav1.LabelSelector`. The labels are defined in `Key` and `Values` of `MatchExpressions` and the `Operator` should be defined as `LabelSelectorOpNotIn` or `LabelSelectorOpDoesNotExist`.   
 
 ### Sample
-A sample of the ConfigMap is as below:
+A sample of the ```node-agent-config``` configMap is as below:
 ```json
 {
     "loadAffinity": [
@@ -101,7 +101,7 @@ This sample showcases one anti-affinity configuration:
 
 To create the configMap, users need to save something like the above sample to a json file and then run below command:
 ```
-kubectl create cm <ConfigMap name> -n velero --from-file=<json file name>
+kubectl create cm node-agent-config -n velero --from-file=<json file name>
 ``` 
 
 ### Implementation
@@ -111,7 +111,15 @@ It is possible that node-agent pods, as a daemonset, don't run in every worker n
 Otherwise, if a backupPod are scheduled to a node where node-agent pod is absent, the corresponding DataUpload CR will stay in `Accepted` phase until the prepare timeout (by default 30min).  
 
 At present, as part of the expose operations, the exposer creates a volume, represented by backupPVC, from the snapshot. The backupPVC uses the same storageClass with the source volume. If the `volumeBindingMode` in the storageClass is `Immediate`, the volume is immediately allocated from the underlying storage without waiting for the backupPod. On the other hand, the loadAffinity is set to the backupPod's affinity. If the backupPod is scheduled to a node where the snapshot volume is not accessible, e.g., because of storage topologies, the backupPod won't get into Running state, concequently, the data movement won't complete.  
-Once this problem happens, the backupPod stays in `Pending` phase, and the corresponding DataUpload CR stays in `Accepted` phase until the prepare timeout (by default 30min). Below is an example of the backupPod's status when the problem happens:   
+Once this problem happens, the backupPod stays in `Pending` phase, and the corresponding DataUpload CR stays in `Accepted` phase until the prepare timeout (by default 30min).   
+
+There is a common solution for the both problems:
+- We have an existing logic to periodically enqueue the dataupload CRs which are in the `Accepted` phase for timeout and cancel checks
+- We add a new logic to this existing logic to check if the corresponding backupPods are in unrecoverable status
+- The above problems could be covered by this check, because in both cases the backupPods are in abnormal and unrecoverable status
+- If a backupPod is unrecoverable, the dataupload controller cancels the dataupload and deletes the backupPod
+
+Specifically, when the above problems happen, the status of a backupPod is like below:
 ```
   status:
     conditions:
@@ -125,8 +133,5 @@ Once this problem happens, the backupPod stays in `Pending` phase, and the corre
     phase: Pending
 ```    
 
-On the other hand, the backupPod is deleted after the prepare timeout, so there is no way to tell the cause is one of the above problems or others.  
-To help the troubleshooting, we can add some diagnostic mechanism to discover the status of the backupPod and node-agent in the same node before deleting it as a result of the prepare timeout.  
-
-[1]: unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
+[1]: Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
 [2]: volume-snapshot-data-movement/volume-snapshot-data-movement.md

design/Implemented/node-agent-concurrency.md

@@ -26,11 +26,11 @@ Therefore, in order to gain the optimized performance with the limited resources
 
 ## Solution
 
-We introduce a ConfigMap specified by `velero node-agent` CLI's parameter `--node-agent-configmap` for users to specify the node-agent related configurations. This configMap is not created by Velero, users should create it manually on demand. The configMap should be in the same namespace where Velero is installed. If multiple Velero instances are installed in different namespaces, there should be one configMap in each namespace which applies to node-agent in that namespace only.  
+We introduce a configMap named ```node-agent-config``` for users to specify the node-agent related configurations. This configMap is not created by Velero, users should create it manually on demand. The configMap should be in the same namespace where Velero is installed. If multiple Velero instances are installed in different namespaces, there should be one configMap in each namespace which applies to node-agent in that namespace only.  
 Node-agent server checks these configurations at startup time and use it to initiate the related VGDP modules. Therefore, users could edit this configMap any time, but in order to make the changes effective, node-agent server needs to be restarted.  
-The ConfigMap may be used for other purpose of configuring node-agent in future, at present, there is only one kind of configuration as the data in the configMap, the name is ```loadConcurrency```.  
+The ```node-agent-config``` configMap may be used for other purpose of configuring node-agent in future, at present, there is only one kind of configuration as the data in the configMap, the name is ```loadConcurrency```.  
 
-The data structure is as below:
+The data structure for ```node-agent-config``` is as below:
 ```go
 type Configs struct {
 	// LoadConcurrency is the config for load concurrency per node.
@@ -82,7 +82,7 @@ At least one node is expected to have a label with the specified ```RuledConfigs
 If one node falls into more than one rules, e.g., if node1 also has the label ```beta.kubernetes.io/instance-type=Standard_B4ms```, the smallest number (3) will be used.  
 
 ### Sample
-A sample of the ConfigMap is as below:
+A sample of the ```node-agent-config``` configMap is as below:
 ```json
 {
     "loadConcurrency": {
@@ -110,7 +110,7 @@ A sample of the ConfigMap is as below:
 ```
 To create the configMap, users need to save something like the above sample to a json file and then run below command:
 ```
-kubectl create cm <ConfigMap name> -n velero --from-file=<json file name>
+kubectl create cm node-agent-config -n velero --from-file=<json file name>
 ```
 
 ### Global data path manager

design/Implemented/node-agent-load-soothing.md

@@ -1,121 +0,0 @@
-# Node-agent Load Soothing Design
-
-## Glossary & Abbreviation
-
-**Velero Generic Data Path (VGDP)**: VGDP is the collective of modules that is introduced in [Unified Repository design][1]. Velero uses these modules to finish data transfer for various purposes (i.e., PodVolume backup/restore, Volume Snapshot Data Movement). VGDP modules include uploaders and the backup repository.  
-
-## Background
-
-As mentioned in [node-agent Concurrency design][2], [CSI Snapshot Data Movement design][3], [VGDP Micro Service design][4] and [VGDP Micro Service for fs-backup design][5], all data movement activities for CSI snapshot data movement backups/restores and fs-backup respect the `loadConcurrency` settings configured in the `node-agent-configmap`. Once the number of existing loads exceeds the corresponding `loadConcurrency` setting, the loads will be throttled and some loads will be held until VGDP quotas are available.  
-However, this throttling only happens after the data mover pod is started and gets to `running`. As a result, when there are large number of concurrent volume backups, there may be many data mover pods get created but the VGDP instances inside them are actually on hold because of the VGDP throttling.  
-This could cause below problems:
-- In some environments, there is a pod limit in each node of the cluster or a pod limit throughout the cluster, too many of the inactive data mover pods may block other pods from running
-- In some environments, the system disk for each node of the cluster is limited, while pods also occupy system disk space, etc., many of the inactive data mover pods also take unnecessary space from system disk and cause other critical pods evicted
-- For CSI snapshot data movement backup, before creation of the data mover pod, the volume snapshot has also created, this means excessive number of snapshots may also be created and live for longer time since the VGDP won't start until the quota is available. However, in some environments, large number of snapshots is not allowed or may cause degradation of the storage peroformance
-
-On the other hand, the VGDP throttling mentioned in [node-agent Concurrency design][2] is an accurate controlling mechanism, that is, exactly the required number of data mover pods are throttled.  
-
-Therefore, another mechanism is required to soothe the creation of the data mover pods and volume snapshots before the VGDP throttling. It doesn't need to accurately control these creations but should effectively reduce the excessive number of inactive data mover pods and volume snapshots.  
-It is not practical to make an accurate control as it is almost impossible to predict which group of nodes a data mover pod is scheduled to, under the consideration of many complex factors, i.e., selected node, affinity, node OS, etc.  
-
-
-## Goals
-
-- Allow users to configure the expected number of loads pending on waiting for VGDP load concurrency quota
-- Create a soothing mechanism to prevent new loads from starting if the number of existing loads excceds the expected number
-
-## Non-Goals
-- Accurately controlling the loads from initiation is not a goal  
-
-## Solution
-
-We introduce a new field `prepareQueueLength` in `loadConcurrency` of `node-agent-configmap` as the allowed number of loads that are under preparing (expose). Specifically, loads are in this situation after its CR is in `Accepted` and `Prepared` phase. The `prepareQueueLength` should be a positive number, negative numbers will be ignored.  
-Once the value is set, the soothing mechanism takes effect, as the best effort, only the allowed number of CRs go into `Accepted` or `Prepared` phase, others will wait and stay as `New` state; and thereby only the allowed number of data mover pods, volume snapshots are created.  
-Otherwise, node-agent works the same as the legacy behavior, CRs go to `Accepted` or `Prepared` state as soon as the controllers process them and data mover pods and volume snapshots are also created without any constraints.  
-If users want to constrain the excessive number of pending data mover pods and volume snapshots, they could set a value by considering the VGDP load concurrency; otherwise, if they don't see constrains for pods or volume snapshots in their environment, they don't need to use this feature, in parallel preparing could also be beneficial for increasing the concurrency.  
-
-Node-agent server checks this configuration at startup time and use it to initiate the related VGDP modules. Therefore, users could edit this configMap any time, but in order to make the changes effective, node-agent server needs to be restarted.  
-
-The data structure is as below:
-```go
-type LoadConcurrency struct {
-    // GlobalConfig specifies the concurrency number to all nodes for which per-node config is not specified
-    GlobalConfig int `json:"globalConfig,omitempty"`
-
-    // PerNodeConfig specifies the concurrency number to nodes matched by rules
-    PerNodeConfig []RuledConfigs `json:"perNodeConfig,omitempty"`
-
-    // PrepareQueueLength specifies the max number of loads that are under expose
-	PrepareQueueLength int `json:"prepareQueueLength,omitempty"`    
-}
-```
-
-### Sample
-A sample of the ConfigMap is as below:
-```json
-{
-    "loadConcurrency": {
-        "globalConfig": 2,
-        "perNodeConfig": [
-            {
-                "nodeSelector": {
-                    "matchLabels": {
-                        "kubernetes.io/hostname": "node1"
-                    }
-                },
-                "number": 3
-            },
-            {
-                "nodeSelector": {
-                    "matchLabels": {
-                        "beta.kubernetes.io/instance-type": "Standard_B4ms"
-                    }
-                },
-                "number": 5
-            }
-        ],
-        "prepareQueueLength": 2
-    }
-}
-```
-To create the configMap, users need to save something like the above sample to a json file and then run below command:
-```
-kubectl create cm <ConfigMap name> -n velero --from-file=<json file name>
-```
-
-## Detailed Design
-Changes apply to the DataUpload Controller, DataDownload Controller, PodVolumeBackup Controller and PodVolumeRestore Controller, as below:
-1. The soothe happens to data mover CRs (DataUpload, DataDownload, PodVolumeBackup or PodVolumeRestore) that are in `New` state
-2. Before starting processing the CR, the corresponding controller counts the existing CRs under or pending for expose in the cluster, that is a total number of existing DataUpload, DataDownload, PodVolumeBackup and PodVolumeRestore that are in either `Accepted` or `Preparing` state  
-3. If the total number doesn't exceed the allowed number, the controller set the CR's phase to `Accepted`
-4. Once the total number exceeds the allowed number, the controller gives up processing the CR and have it requeued later. The delay for the requeue is 5 seconds
-
-The count happens for all the controllers in all nodes, to prevent the checks drain out the API server, the count happens to controller client caches for those CRs. And the count result is also cached, so that the count only happens whenever necessary. Below shows how it judges the necessity:
-- When one or more CRs' phase change to `Accepted`
-- When one or more CRs' phase change from `Accepted` to one of the terminal phases
-- When one or more CRs' phase change from `Prepared` to one of the terminal phases
-- When one or more CRs' phase change from `Prepared` to `InProgress`
-
-Ideally, 2~3 in the above steps need to be synchornized among controllers in all nodes. However, this synchronization is not implemented, the consideration is as below:    
-1. It is impossible to accurately synchronize the count among controllers in different nodes, because the client cache is not coherrent among nodes.  
-2. It is possible to synchronize the count among controllers in the same node. However, it is too expensive to make this synchronization, because 2~3 are part of the expose workflow, the synchronization impacts the performance and stability of the existing workflow. 
-3. Even without the synchronization, the soothing mechanism still works eventually -- when the controllers see all the discharged loads (expected ones and over-discharged ones), they will stop creating new loads until the quota is available again.  
-4. Step 2~3 that need to be synchronized could complete very quickly.    
-
-This is why we say this mechanism is not an accurate control. Or in another word, it is possible that more loads than the number of `prepareQueueLength` are discharged if controllers make the count and expose in the overlapped time (step 2~3).  
-For example, when multiple controllers of the same type (DataUpload, DataDownload, PodVolumeBackup or PodVolumeRestore) from different nodes make the count:  
-```
-max number of waiting loads = number defined by `prepareQueueLength` + number of nodes in cluster
-```
-As another example, when hybrid loads are running the count concurrently, e.g., mix of data mover backups, data mover restores, pod volume backups or pod volume restores, more loads may be discharged and the number depends on the number of concurrent hybrid loads.  
-In either case, because step 2~3 is short in time, it is less likely to reach the theoretically worset result.  
-
-
-
-
-
-[1]: unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
-[2]: node-agent-concurrency.md
-[3]: volume-snapshot-data-movement/volume-snapshot-data-movement.md
-[4]: vgdp-micro-service/vgdp-micro-service.md
-[5]: vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md

design/Implemented/plugin-versioning.md

@@ -241,7 +241,7 @@ In cases where the methods signatures remain the same, the adaptation layer will
 Examples where an adaptation may be safe:
 - A method signature is being changed to add a new parameter but the parameter could be optional (for example, adding a context parameter). The adaptation could call through to the method provided in the previous version but omit the parameter.
 - A method signature is being changed to remove a parameter, but it is safe to pass a default value to the previous version. The adaptation could call through to the method provided in the previous version but use a default value for the parameter.
-- A new method is being added but does not impact any existing behaviour of Velero (for example, a new method which will allow Velero to [wait for additional items to be ready](https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/wait-for-additional-items.md)). The adaptation would return a value which allows the existing behaviour to be performed.
+- A new method is being added but does not impact any existing behaviour of Velero (for example, a new method which will allow Velero to [wait for additional items to be ready](https://github.com/vmware-tanzu/velero/blob/main/design/wait-for-additional-items.md)). The adaptation would return a value which allows the existing behaviour to be performed.
 - A method is being deleted as it is no longer used. The adaptation would call through to any methods which are still included but would omit the deleted method in the adaptation.
 
 Examples where an adaptation may not be safe:

design/Implemented/priority-class-name-support_design.md

@@ -1,694 +0,0 @@
-# PriorityClass Support Design Proposal
-
-## Abstract
-
-This design document outlines the implementation of priority class name support for Velero components, including the Velero server deployment, node agent daemonset, and maintenance jobs. This feature allows users to specify a priority class name for Velero components, which can be used to influence the scheduling and eviction behavior of these components.
-
-## Background
-
-Kubernetes allows users to define priority classes, which can be used to influence the scheduling and eviction behavior of pods. Priority classes are defined as cluster-wide resources, and pods can reference them by name. When a pod is created, the priority admission controller uses the priority class name to populate the priority value for the pod. The scheduler then uses this priority value to determine the order in which pods are scheduled.
-
-Currently, Velero does not provide a way for users to specify a priority class name for its components. This can be problematic in clusters where resource contention is high, as Velero components may be evicted or not scheduled in a timely manner, potentially impacting backup and restore operations.
-
-## Goals
-
-- Add support for specifying priority class names for Velero components
-- Update the Velero CLI to accept priority class name parameters for different components
-- Update the Velero deployment, node agent daemonset, maintenance jobs, and data mover pods to use the specified priority class names
-
-## Non Goals
-
-- Creating or managing priority classes
-- Automatically determining the appropriate priority class for Velero components
-
-## High-Level Design
-
-The implementation will add new fields to the Velero options struct to store the priority class names for the server deployment and node agent daemonset. The Velero CLI will be updated to accept new flags for these components. For data mover pods and maintenance jobs, priority class names will be configured through existing ConfigMap mechanisms (`node-agent-configmap` for data movers and `repo-maintenance-job-configmap` for maintenance jobs). The Velero deployment, node agent daemonset, maintenance jobs, and data mover pods will be updated to use their respective priority class names.
-
-## Detailed Design
-
-### CLI Changes
-
-New flags will be added to the `velero install` command to specify priority class names for different components:
-
-```go
-flags.StringVar(
-    &o.ServerPriorityClassName,
-    "server-priority-class-name",
-    o.ServerPriorityClassName,
-    "Priority class name for the Velero server deployment. Optional.",
-)
-
-flags.StringVar(
-    &o.NodeAgentPriorityClassName,
-    "node-agent-priority-class-name",
-    o.NodeAgentPriorityClassName,
-    "Priority class name for the node agent daemonset. Optional.",
-)
-```
-
-Note: Priority class names for data mover pods and maintenance jobs will be configured through their respective ConfigMaps (`--node-agent-configmap` for data movers and `--repo-maintenance-job-configmap` for maintenance jobs).
-
-### Velero Options Changes
-
-The `VeleroOptions` struct in `pkg/install/resources.go` will be updated to include new fields for priority class names:
-
-```go
-type VeleroOptions struct {
-    // ... existing fields ...
-    ServerPriorityClassName       string
-    NodeAgentPriorityClassName    string
-}
-```
-
-### Deployment Changes
-
-The `podTemplateConfig` struct in `pkg/install/deployment.go` will be updated to include a new field for the priority class name:
-
-```go
-type podTemplateConfig struct {
-    // ... existing fields ...
-    priorityClassName string
-}
-```
-
-A new function, `WithPriorityClassName`, will be added to set this field:
-
-```go
-func WithPriorityClassName(priorityClassName string) podTemplateOption {
-    return func(c *podTemplateConfig) {
-        c.priorityClassName = priorityClassName
-    }
-}
-```
-
-The `Deployment` function will be updated to use the priority class name:
-
-```go
-deployment := &appsv1api.Deployment{
-    // ... existing fields ...
-    Spec: appsv1api.DeploymentSpec{
-        // ... existing fields ...
-        Template: corev1api.PodTemplateSpec{
-            // ... existing fields ...
-            Spec: corev1api.PodSpec{
-                // ... existing fields ...
-                PriorityClassName: c.priorityClassName,
-            },
-        },
-    },
-}
-```
-
-### DaemonSet Changes
-
-The `DaemonSet` function will use the priority class name passed via the podTemplateConfig (from the CLI flag):
-
-```go
-daemonSet := &appsv1api.DaemonSet{
-    // ... existing fields ...
-    Spec: appsv1api.DaemonSetSpec{
-        // ... existing fields ...
-        Template: corev1api.PodTemplateSpec{
-            // ... existing fields ...
-            Spec: corev1api.PodSpec{
-                // ... existing fields ...
-                PriorityClassName: c.priorityClassName,
-            },
-        },
-    },
-}
-```
-
-### Maintenance Job Changes
-
-The `JobConfigs` struct in `pkg/repository/maintenance/maintenance.go` will be updated to include a field for the priority class name:
-
-```go
-type JobConfigs struct {
-    // LoadAffinities is the config for repository maintenance job load affinity.
-    LoadAffinities []*kube.LoadAffinity `json:"loadAffinity,omitempty"`
-
-    // PodResources is the config for the CPU and memory resources setting.
-    PodResources *kube.PodResources `json:"podResources,omitempty"`
-    
-    // PriorityClassName is the priority class name for the maintenance job pod
-    // Note: This is only read from the global configuration, not per-repository
-    PriorityClassName string `json:"priorityClassName,omitempty"`
-}
-```
-
-The `buildJob` function will be updated to use the priority class name from the global job configuration:
-
-```go
-func buildJob(cli client.Client, ctx context.Context, repo *velerov1api.BackupRepository, bslName string, config *JobConfigs,
-    podResources kube.PodResources, logLevel logrus.Level, logFormat *logging.FormatFlag) (*batchv1.Job, error) {
-    // ... existing code ...
-    
-    // Use the priority class name from the global job configuration if available
-    // Note: Priority class is only read from global config, not per-repository
-    priorityClassName := ""
-    if config != nil && config.PriorityClassName != "" {
-        priorityClassName = config.PriorityClassName
-    }
-    
-    // ... existing code ...
-    
-    job := &batchv1.Job{
-        // ... existing fields ...
-        Spec: batchv1.JobSpec{
-            // ... existing fields ...
-            Template: corev1api.PodTemplateSpec{
-                // ... existing fields ...
-                Spec: corev1api.PodSpec{
-                    // ... existing fields ...
-                    PriorityClassName: priorityClassName,
-                },
-            },
-        },
-    }
-    
-    // ... existing code ...
-}
-```
-
-Users will be able to configure the priority class name for all maintenance jobs by creating the repository maintenance job ConfigMap before installation. For example:
-
-```bash
-# Create the ConfigMap before running velero install
-cat <<EOF | kubectl create configmap repo-maintenance-job-config -n velero --from-file=config.json=/dev/stdin
-{
-    "global": {
-        "priorityClassName": "low-priority",
-        "podResources": {
-            "cpuRequest": "100m",
-            "memoryRequest": "128Mi"
-        }
-    }
-}
-EOF
-
-# Then install Velero referencing this ConfigMap
-velero install --provider aws \
-    --repo-maintenance-job-configmap repo-maintenance-job-config \
-    # ... other flags
-```
-
-The ConfigMap can be updated after installation to change the priority class for future maintenance jobs. Note that only the "global" configuration is used for priority class - all maintenance jobs will use the same priority class regardless of which repository they are maintaining.
-
-### Node Agent ConfigMap Changes
-
-We'll update the `Configs` struct in `pkg/nodeagent/node_agent.go` to include a field for the priority class name in the node-agent-configmap:
-
-```go
-type Configs struct {
-    // ... existing fields ...
-    
-    // PriorityClassName is the priority class name for the data mover pods 
-    // created by the node agent
-    PriorityClassName string `json:"priorityClassName,omitempty"`
-}
-```
-
-This will allow users to configure the priority class name for data mover pods through the node-agent-configmap. Note that the node agent daemonset itself gets its priority class from the `--node-agent-priority-class-name` CLI flag during installation, not from this configmap. For example:
-
-```bash
-# Create the ConfigMap before running velero install
-cat <<EOF | kubectl create configmap node-agent-config -n velero --from-file=config.json=/dev/stdin
-{
-    "priorityClassName": "low-priority",
-    "loadAffinity": [
-        {
-            "nodeSelector": {
-                "matchLabels": {
-                    "node-role.kubernetes.io/worker": "true"
-                }
-            }
-        }
-    ]
-}
-EOF
-
-# Then install Velero referencing this ConfigMap
-velero install --provider aws \
-    --node-agent-configmap node-agent-config \
-    --use-node-agent \
-    # ... other flags
-```
-
-The `createBackupPod` function in `pkg/exposer/csi_snapshot.go` will be updated to accept and use the priority class name:
-
-```go
-func (e *csiSnapshotExposer) createBackupPod(
-    ctx context.Context,
-    ownerObject corev1api.ObjectReference,
-    backupPVC *corev1api.PersistentVolumeClaim,
-    operationTimeout time.Duration,
-    label map[string]string,
-    annotation map[string]string,
-    affinity *kube.LoadAffinity,
-    resources corev1api.ResourceRequirements,
-    backupPVCReadOnly bool,
-    spcNoRelabeling bool,
-    nodeOS string,
-    priorityClassName string, // New parameter
-) (*corev1api.Pod, error) {
-    // ... existing code ...
-    
-    pod := &corev1api.Pod{
-        // ... existing fields ...
-        Spec: corev1api.PodSpec{
-            // ... existing fields ...
-            PriorityClassName: priorityClassName,
-            // ... existing fields ...
-        },
-    }
-    
-    // ... existing code ...
-}
-```
-
-The call to `createBackupPod` in the `Expose` method will be updated to pass the priority class name retrieved from the node-agent-configmap:
-
-```go
-priorityClassName, _ := kube.GetDataMoverPriorityClassName(ctx, namespace, kubeClient, configMapName)
-backupPod, err := e.createBackupPod(
-    ctx,
-    ownerObject,
-    backupPVC,
-    csiExposeParam.OperationTimeout,
-    csiExposeParam.HostingPodLabels,
-    csiExposeParam.HostingPodAnnotations,
-    csiExposeParam.Affinity,
-    csiExposeParam.Resources,
-    backupPVCReadOnly,
-    spcNoRelabeling,
-    csiExposeParam.NodeOS,
-    priorityClassName, // Priority class name from node-agent-configmap
-)
-```
-
-A new function, `GetDataMoverPriorityClassName`, will be added to the `pkg/util/kube` package (in the same file as `ValidatePriorityClass`) to retrieve the priority class name for data mover pods:
-
-```go
-// In pkg/util/kube/priority_class.go
-
-// GetDataMoverPriorityClassName retrieves the priority class name for data mover pods from the node-agent-configmap
-func GetDataMoverPriorityClassName(ctx context.Context, namespace string, kubeClient kubernetes.Interface, configName string) (string, error) {
-    // configData is a minimal struct to parse only the priority class name from the ConfigMap
-    type configData struct {
-        PriorityClassName string `json:"priorityClassName,omitempty"`
-    }
-
-    // Get the ConfigMap
-    cm, err := kubeClient.CoreV1().ConfigMaps(namespace).Get(ctx, configName, metav1.GetOptions{})
-    if err != nil {
-        if apierrors.IsNotFound(err) {
-            // ConfigMap not found is not an error, just return empty string
-            return "", nil
-        }
-        return "", errors.Wrapf(err, "error getting node agent config map %s", configName)
-    }
-
-    if cm.Data == nil {
-        // No data in ConfigMap, return empty string
-        return "", nil
-    }
-
-    // Extract the first value from the ConfigMap data
-    jsonString := ""
-    for _, v := range cm.Data {
-        jsonString = v
-        break // Use the first value found
-    }
-
-    if jsonString == "" {
-        // No data to parse, return empty string
-        return "", nil
-    }
-
-    // Parse the JSON to extract priority class name
-    var config configData
-    if err := json.Unmarshal([]byte(jsonString), &config); err != nil {
-        // Invalid JSON is not a critical error for priority class
-        // Just return empty string to use default behavior
-        return "", nil
-    }
-
-    return config.PriorityClassName, nil
-}
-```
-
-This function will get the priority class name from the node-agent-configmap. If it's not found, it will return an empty string.
-
-### Validation and Logging
-
-To improve observability and help with troubleshooting, the implementation will include:
-
-1. **Optional Priority Class Validation**: A helper function to check if a priority class exists in the cluster. This function will be added to the `pkg/util/kube` package alongside other Kubernetes utility functions:
-
-```go
-// In pkg/util/kube/priority_class.go
-
-// ValidatePriorityClass checks if the specified priority class exists in the cluster
-// Returns true if the priority class exists or if priorityClassName is empty
-// Returns false if the priority class doesn't exist or validation fails
-// Logs warnings when the priority class doesn't exist
-func ValidatePriorityClass(ctx context.Context, kubeClient kubernetes.Interface, priorityClassName string, logger logrus.FieldLogger) bool {
-    if priorityClassName == "" {
-        return true
-    }
-    
-    _, err := kubeClient.SchedulingV1().PriorityClasses().Get(ctx, priorityClassName, metav1.GetOptions{})
-    if err != nil {
-        if apierrors.IsNotFound(err) {
-            logger.Warnf("Priority class %q not found in cluster. Pod creation may fail if the priority class doesn't exist when pods are scheduled.", priorityClassName)
-        } else {
-            logger.WithError(err).Warnf("Failed to validate priority class %q", priorityClassName)
-        }
-        return false
-    }
-    logger.Infof("Validated priority class %q exists in cluster", priorityClassName)
-    return true
-}
-```
-
-2. **Debug Logging**: Add debug logs when priority classes are applied:
-
-```go
-// In deployment creation
-if c.priorityClassName != "" {
-    logger.Debugf("Setting priority class %q for Velero server deployment", c.priorityClassName)
-}
-
-// In daemonset creation
-if c.priorityClassName != "" {
-    logger.Debugf("Setting priority class %q for node agent daemonset", c.priorityClassName)
-}
-
-// In maintenance job creation
-if priorityClassName != "" {
-    logger.Debugf("Setting priority class %q for maintenance job %s", priorityClassName, job.Name)
-}
-
-// In data mover pod creation
-if priorityClassName != "" {
-    logger.Debugf("Setting priority class %q for data mover pod %s", priorityClassName, pod.Name)
-}
-```
-
-These validation and logging features will help administrators:
-
-- Identify configuration issues early (validation warnings)
-- Troubleshoot priority class application issues
-- Verify that priority classes are being applied as expected
-
-The `ValidatePriorityClass` function should be called at the following points:
-
-1. **During `velero install`**: Validate the priority classes specified via CLI flags:
-   - After parsing `--server-priority-class-name` flag
-   - After parsing `--node-agent-priority-class-name` flag
-
-2. **When reading from ConfigMaps**: Validate priority classes when loading configurations:
-   - In `GetDataMoverPriorityClassName` when reading from node-agent-configmap
-   - In maintenance job controller when reading from repo-maintenance-job-configmap
-
-3. **During pod/job creation** (optional, for runtime validation):
-   - Before creating data mover pods (PVB/PVR/CSI snapshot data movement)
-   - Before creating maintenance jobs
-
-Example usage:
-
-```go
-// During velero install
-if o.ServerPriorityClassName != "" {
-    _ = kube.ValidatePriorityClass(ctx, kubeClient, o.ServerPriorityClassName, logger.WithField("component", "server"))
-    // For install command, we continue even if validation fails (warnings are logged)
-}
-
-// When reading from ConfigMap in node-agent server
-priorityClassName, err := kube.GetDataMoverPriorityClassName(ctx, namespace, kubeClient, configMapName)
-if err == nil && priorityClassName != "" {
-    // Validate the priority class exists in the cluster
-    if kube.ValidatePriorityClass(ctx, kubeClient, priorityClassName, logger.WithField("component", "data-mover")) {
-        dataMovePriorityClass = priorityClassName
-        logger.WithField("priorityClassName", priorityClassName).Info("Using priority class for data mover pods")
-    } else {
-        logger.WithField("priorityClassName", priorityClassName).Warn("Priority class not found in cluster, data mover pods will use default priority")
-        // Clear the priority class to prevent pod creation failures
-        priorityClassName = ""
-    }
-}
-```
-
-Note: The validation function returns a boolean to allow callers to decide how to handle missing priority classes. For the install command, validation failures are ignored (only warnings are logged) to allow for scenarios where priority classes might be created after Velero installation. For runtime components like the node-agent server, the priority class is cleared if validation fails to prevent pod creation failures.
-
-## Alternatives Considered
-
-1. **Using a single flag for all components**: We could have used a single flag for all components, but this would not allow for different priority classes for different components. Since maintenance jobs and data movers typically require lower priority than the Velero server, separate flags provide more flexibility.
-
-2. **Using a configuration file**: We could have added support for specifying the priority class names in a configuration file. However, this would have required additional changes to the Velero CLI and would have been more complex to implement.
-
-3. **Inheriting priority class from parent components**: We initially considered having maintenance jobs inherit their priority class from the Velero server, and data movers inherit from the node agent. However, this approach doesn't allow for the appropriate prioritization of different components based on their importance and resource requirements.
-
-## Security Considerations
-
-There are no security considerations for this feature.
-
-## Compatibility
-
-This feature is compatible with all Kubernetes versions that support priority classes. The PodPriority feature became stable in Kubernetes 1.14. For more information, see the [Kubernetes documentation on Pod Priority and Preemption](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/).
-
-## ConfigMap Update Strategy
-
-### Static ConfigMap Reading at Startup
-
-The node-agent server reads and parses the ConfigMap once during initialization and passes configurations (like `podResources`, `loadAffinity`, and `priorityClassName`) directly to controllers as parameters. This approach ensures:
-
-- Single ConfigMap read to minimize API calls
-- Consistent configuration across all controllers
-- Validation of priority classes at startup with fallback behavior
-- No need for complex update mechanisms or watchers
-
-ConfigMap changes require a restart of the node-agent to take effect.
-
-### Implementation Approach
-
-1. **Data Mover Controllers**: Receive priority class as a string parameter from node-agent server at initialization
-2. **Maintenance Job Controller**: Read fresh configuration from repo-maintenance-job-configmap at job creation time
-3. ConfigMap changes require restart of components to take effect
-4. Priority class validation happens at startup with automatic fallback to prevent failures
-
-## Implementation
-
-The implementation will involve the following steps:
-
-1. Add the priority class name fields for server and node agent to the `VeleroOptions` struct
-2. Add the priority class name field to the `podTemplateConfig` struct
-3. Add the `WithPriorityClassName` function for the server deployment and daemonset
-4. Update the `Deployment` function to use the server priority class name
-5. Update the `DaemonSet` function to use the node agent priority class name
-6. Update the `JobConfigs` struct to include `PriorityClassName` field
-7. Update the `buildJob` function in maintenance job to use the priority class name from JobConfigs (global config only)
-8. Update the `Configs` struct in node agent to include `PriorityClassName` field for data mover pods
-9. Update the data mover pod creation to use the priority class name from node-agent-configmap
-10. Update the PodVolumeBackup controller to retrieve and apply priority class name from node-agent-configmap
-11. Update the PodVolumeRestore controller to retrieve and apply priority class name from node-agent-configmap
-12. Add the `GetDataMoverPriorityClassName` utility function to retrieve priority class from configmap
-13. Add the priority class name flags for server and node agent to the `velero install` command
-14. Add unit tests for:
-    - `WithPriorityClassName` function
-    - `GetDataMoverPriorityClassName` function
-    - Priority class application in deployment, daemonset, and job specs
-15. Add integration tests to verify:
-    - Priority class is correctly applied to all component pods
-    - ConfigMap updates are reflected in new pods
-    - Empty/missing priority class names are handled gracefully
-16. Update user documentation to include:
-    - How to configure priority classes for each component
-    - Examples of creating ConfigMaps before installation
-    - Expected priority class hierarchy recommendations
-    - Troubleshooting guide for priority class issues
-17. Update CLI documentation for new flags (`--server-priority-class-name` and `--node-agent-priority-class-name`)
-
-Note: The server deployment and node agent daemonset will have CLI flags for priority class. Data mover pods and maintenance jobs will use their respective ConfigMaps for priority class configuration.
-
-This approach ensures that different Velero components can use different priority class names based on their importance and resource requirements:
-
-1. The Velero server deployment can use a higher priority class to ensure it continues running even under resource pressure.
-2. The node agent daemonset can use a medium priority class.
-3. Maintenance jobs can use a lower priority class since they should not run when resources are limited.
-4. Data mover pods can use a lower priority class since they should not run when resources are limited.
-
-### Implementation Considerations
-
-Priority class names are configured through different mechanisms:
-
-1. **Server Deployment**: Uses the `--server-priority-class-name` CLI flag during installation.
-
-2. **Node Agent DaemonSet**: Uses the `--node-agent-priority-class-name` CLI flag during installation.
-
-3. **Data Mover Pods**: Will use the node-agent-configmap (specified via the `--node-agent-configmap` flag). This ConfigMap controls priority class for all data mover pods (including PVB and PVR) created by the node agent.
-
-4. **Maintenance Jobs**: Will use the repository maintenance job ConfigMap (specified via the `--repo-maintenance-job-configmap` flag). Users should create this ConfigMap before running `velero install` with the desired priority class configuration. The ConfigMap can be updated after installation to change priority classes for future maintenance jobs. While the ConfigMap structure supports per-repository configuration for resources and affinity, priority class is intentionally only read from the global configuration to ensure all maintenance jobs have the same priority.
-
-#### ConfigMap Pre-Creation Guide
-
-For components that use ConfigMaps for priority class configuration, the ConfigMaps must be created before running `velero install`. Here's the recommended workflow:
-
-```bash
-# Step 1: Create priority classes in your cluster (if not already existing)
-kubectl apply -f - <<EOF
-apiVersion: scheduling.k8s.io/v1
-kind: PriorityClass
-metadata:
-  name: velero-critical
-value: 100
-globalDefault: false
-description: "Critical priority for Velero server"
----
-apiVersion: scheduling.k8s.io/v1
-kind: PriorityClass
-metadata:
-  name: velero-standard
-value: 50
-globalDefault: false
-description: "Standard priority for Velero node agent"
----
-apiVersion: scheduling.k8s.io/v1
-kind: PriorityClass
-metadata:
-  name: velero-low
-value: 10
-globalDefault: false
-description: "Low priority for Velero data movers and maintenance jobs"
-EOF
-
-# Step 2: Create the namespace
-kubectl create namespace velero
-
-# Step 3: Create ConfigMaps for data movers and maintenance jobs
-kubectl create configmap node-agent-config -n velero --from-file=config.json=/dev/stdin <<EOF
-{
-    "priorityClassName": "velero-low"
-}
-EOF
-
-kubectl create configmap repo-maintenance-job-config -n velero --from-file=config.json=/dev/stdin <<EOF
-{
-    "global": {
-        "priorityClassName": "velero-low"
-    }
-}
-EOF
-
-# Step 4: Install Velero with priority class configuration
-velero install \
-    --provider aws \
-    --server-priority-class-name velero-critical \
-    --node-agent-priority-class-name velero-standard \
-    --node-agent-configmap node-agent-config \
-    --repo-maintenance-job-configmap repo-maintenance-job-config \
-    --use-node-agent
-```
-
-#### Recommended Priority Class Hierarchy
-
-When configuring priority classes for Velero components, consider the following hierarchy based on component criticality:
-
-1. **Velero Server (Highest Priority)**:
-   - Example: `velero-critical` with value 100
-   - Rationale: The server must remain running to coordinate backup/restore operations
-
-2. **Node Agent DaemonSet (Medium Priority)**:
-   - Example: `velero-standard` with value 50
-   - Rationale: Node agents need to be available on nodes but are less critical than the server
-
-3. **Data Mover Pods & Maintenance Jobs (Lower Priority)**:
-   - Example: `velero-low` with value 10
-   - Rationale: These are temporary workloads that can be delayed during resource contention
-
-This hierarchy ensures that core Velero components remain operational even under resource pressure, while allowing less critical workloads to be preempted if necessary.
-
-This approach has several advantages:
-
-- Leverages existing configuration mechanisms, minimizing new CLI flags
-- Provides a single point of configuration for related components (node agent and its pods)
-- Allows dynamic configuration updates without requiring Velero reinstallation
-- Maintains backward compatibility with existing installations
-- Enables administrators to set up priority classes during initial deployment
-- Keeps configuration simple by using the same priority class for all maintenance jobs
-
-The priority class name for data mover pods will be determined by checking the node-agent-configmap. This approach provides a centralized way to configure priority class names for all data mover pods. The same approach will be used for PVB (PodVolumeBackup) and PVR (PodVolumeRestore) pods, which will also retrieve their priority class name from the node-agent-configmap.
-
-For PVB and PVR pods specifically, the implementation follows this approach:
-
-1. **Controller Initialization**: Both PodVolumeBackup and PodVolumeRestore controllers are updated to accept a priority class name as a string parameter. The node-agent server reads the priority class from the node-agent-configmap once at startup:
-
-```go
-// In node-agent server startup (pkg/cmd/cli/nodeagent/server.go)
-dataMovePriorityClass := ""
-if s.config.nodeAgentConfig != "" {
-    ctx, cancel := context.WithTimeout(context.Background(), time.Second*30)
-    defer cancel()
-    priorityClass, err := kube.GetDataMoverPriorityClassName(ctx, s.namespace, s.kubeClient, s.config.nodeAgentConfig)
-    if err != nil {
-        s.logger.WithError(err).Warn("Failed to get priority class name from node-agent-configmap, using empty value")
-    } else if priorityClass != "" {
-        // Validate the priority class exists in the cluster
-        if kube.ValidatePriorityClass(ctx, s.kubeClient, priorityClass, s.logger.WithField("component", "data-mover")) {
-            dataMovePriorityClass = priorityClass
-            s.logger.WithField("priorityClassName", priorityClass).Info("Using priority class for data mover pods")
-        } else {
-            s.logger.WithField("priorityClassName", priorityClass).Warn("Priority class not found in cluster, data mover pods will use default priority")
-        }
-    }
-}
-
-// Pass priority class to controllers
-pvbReconciler := controller.NewPodVolumeBackupReconciler(
-    s.mgr.GetClient(), s.mgr, s.kubeClient, ..., dataMovePriorityClass)
-pvrReconciler := controller.NewPodVolumeRestoreReconciler(
-    s.mgr.GetClient(), s.mgr, s.kubeClient, ..., dataMovePriorityClass)
-```
-
-2. **Controller Structure**: Controllers store the priority class name as a field:
-
-```go
-type PodVolumeBackupReconciler struct {
-    // ... existing fields ...
-    dataMovePriorityClass string
-}
-```
-
-3. **Pod Creation**: The priority class is included in the pod spec when creating data mover pods.
-
-### VGDP Micro-Service Considerations
-
-With the introduction of VGDP micro-services (as described in the VGDP micro-service design), data mover pods are created as dedicated pods for volume snapshot data movement. These pods will also inherit the priority class configuration from the node-agent-configmap. Since VGDP-MS pods (backupPod/restorePod) inherit their configurations from the node-agent, they will automatically use the priority class name specified in the node-agent-configmap.
-
-This ensures that all pods created by Velero for data movement operations (CSI snapshot data movement, PVB, and PVR) use a consistent approach for priority class name configuration through the node-agent-configmap.
-
-### How Exposers Receive Configuration
-
-CSI Snapshot Exposer and Generic Restore Exposer do not directly watch or read ConfigMaps. Instead, they receive configuration through their parent controllers:
-
-1. **Controller Initialization**: Controllers receive the priority class name as a parameter during initialization from the node-agent server.
-
-2. **Configuration Propagation**: During reconciliation of resources:
-   - The controller calls `setupExposeParam()` which includes the `dataMovePriorityClass` value
-   - For CSI operations: `CSISnapshotExposeParam.PriorityClassName` is set
-   - For generic restore: `GenericRestoreExposeParam.PriorityClassName` is set
-   - The controller passes these parameters to the exposer's `Expose()` method
-
-3. **Pod Creation**: The exposer creates pods with the priority class name provided by the controller.
-
-This design keeps exposers stateless and ensures:
-- Exposers remain simple and focused on pod creation
-- All configuration flows through controllers consistently
-- No complex state synchronization between components
-- Configuration changes require component restart to take effect
-
-## Open Issues
-
-None.

design/Implemented/repo_maintenance_job_config.md

@@ -1,311 +0,0 @@
-# Repository maintenance job configuration design
-
-## Abstract
-Add this design to make the repository maintenance job can read configuration from a dedicate ConfigMap and make the Job's necessary parts configurable, e.g. `PodSpec.Affinity` and `PodSpec.Resources`.
-
-## Background
-Repository maintenance is split from the Velero server to a k8s Job in v1.14 by design [repository maintenance job](repository-maintenance.md).
-The repository maintenance Job configuration was read from the Velero server CLI parameter, and it inherits the most of Velero server's Deployment's PodSpec to fill un-configured fields.
-
-This design introduces a new way to let the user to customize the repository maintenance behavior instead of inheriting from the Velero server Deployment or reading from `velero server` CLI parameters.
-The configurations added in this design including the resource limitations, node selection.
-It's possible new configurations are introduced in future releases based on this design.
-
-For the node selection, the repository maintenance Job also inherits from the Velero server deployment before, but the Job may last for a while and cost noneligible resources, especially memory.
-The users have the need to choose which k8s node to run the maintenance Job.
-This design reuses the data structure introduced by design [Velero Generic Data Path affinity configuration](node-agent-affinity.md) to make the repository maintenance job can choose which node running on.
-
-## Goals
-- Unify the repository maintenance Job configuration at one place.
-- Let user can choose repository maintenance Job running on which nodes.
-
-## Non Goals
-- There was an [issue](https://github.com/vmware-tanzu/velero/issues/7911) to require the whole Job's PodSpec should be configurable. That's not in the scope of this design.
-- Please notice this new configuration is dedicated for the repository maintenance. Repository itself configuration is not covered.
-
-
-## Compatibility
-v1.14 uses the `velero server` CLI's parameter to pass the repository maintenance job configuration.
-In v1.15, those parameters are still kept, including `--maintenance-job-cpu-request`, `--maintenance-job-mem-request`, `--maintenance-job-cpu-limit`, `--maintenance-job-mem-limit`, and `--keep-latest-maintenance-jobs`.
-But the parameters read from the ConfigMap specified by `velero server` CLI parameter `--repo-maintenance-job-configmap` introduced by this design have a higher priority.
-
-If there `--repo-maintenance-job-configmap` is not specified, then the `velero server` parameters are used if provided.
-
-If the `velero server` parameters are not specified too, then the default values are used.
-* `--keep-latest-maintenance-jobs` default value is 3.
-* `--maintenance-job-cpu-request` default value is 0.
-* `--maintenance-job-mem-request` default value is 0.
-* `--maintenance-job-cpu-limit` default value is 0.
-* `--maintenance-job-mem-limit` default value is 0.
-
-## Deprecation
-Propose to deprecate the `velero server` parameters `--maintenance-job-cpu-request`, `--maintenance-job-mem-request`, `--maintenance-job-cpu-limit`, `--maintenance-job-mem-limit`, and `--keep-latest-maintenance-jobs` in release-1.15.
-That means those parameters will be deleted in release-1.17.
-After deletion, those resources-related parameters are replaced by the ConfigMap specified by `velero server` CLI's parameter `--repo-maintenance-job-configmap`.
-`--keep-latest-maintenance-jobs` is deleted from `velero server` CLI. It turns into a non-configurable internal parameter, and its value is 3.
-Please check [issue 7923](https://github.com/vmware-tanzu/velero/issues/7923) for more information why deleting this parameter.
-
-## Design
-This design introduces a new ConfigMap specified by `velero server` CLI parameter `--repo-maintenance-job-configmap` as the source of the repository maintenance job configuration. The specified ConfigMap is read from the namespace where Velero is installed.
-If the ConfigMap doesn't exist, the internal default values are used.
-
-Example of using the parameter `--repo-maintenance-job-configmap`:
-```
-velero server \
-    ...
-    --repo-maintenance-job-configmap repo-job-config
-    ...
-```
-
-**Notice**
-* Velero doesn't own this ConfigMap. If the user wants to customize the repository maintenance job, the user needs to create this ConfigMap.
-* Velero reads this ConfigMap content at starting a new repository maintenance job, so the ConfigMap change will not take affect until the next created job.
-
-### Structure
-The data structure is as below:
-```go
-type Configs struct {
-    // LoadAffinity is the config for data path load affinity.
-    LoadAffinity []*LoadAffinity `json:"loadAffinity,omitempty"`    
-
-    // PodResources is the config for the CPU and memory resources setting.
-    PodResources *kube.PodResources `json:"podResources,omitempty"`
-}
-
-type LoadAffinity struct {
-    // NodeSelector specifies the label selector to match nodes
-    NodeSelector metav1.LabelSelector `json:"nodeSelector"`
-}
-
-type PodResources struct {
-	CPURequest    string `json:"cpuRequest,omitempty"`
-	MemoryRequest string `json:"memoryRequest,omitempty"`
-	CPULimit      string `json:"cpuLimit,omitempty"`
-	MemoryLimit   string `json:"memoryLimit,omitempty"`
-}
-```
-
-The ConfigMap content is a map.
-If there is a key value as `global` in the map, the key's value is applied to all BackupRepositories maintenance jobs that cannot find their own specific configuration in the ConfigMap.
-The other keys in the map is the combination of three elements of a BackupRepository:
-* The namespace in which BackupRepository backs up volume data.
-* The BackupRepository referenced BackupStorageLocation's name.
-* The BackupRepository's type. Possible values are `kopia` and `restic`.
-
-Those three keys can identify a [unique BackupRepository](https://github.com/vmware-tanzu/velero/blob/2fc6300f2239f250b40b0488c35feae59520f2d3/pkg/repository/backup_repo_op.go#L32-L37).
-
-If there is a key match with BackupRepository, the key's value is applied to the BackupRepository's maintenance jobs.
-By this way, it's possible to let user configure before the BackupRepository is created.
-This is especially convenient for administrator configuring during the Velero installation.
-For example, the following BackupRepository's key should be `test-default-kopia`.
-
-``` yaml
-- apiVersion: velero.io/v1
-  kind: BackupRepository
-  metadata:
-    generateName: test-default-kopia-
-    labels:
-      velero.io/repository-type: kopia
-      velero.io/storage-location: default
-      velero.io/volume-namespace: test
-    name: test-default-kopia-kgt6n
-    namespace: velero
-  spec:
-    backupStorageLocation: default
-    maintenanceFrequency: 1h0m0s
-    repositoryType: kopia
-    resticIdentifier: gs:jxun:/restic/test
-    volumeNamespace: test
-```
-
-The `LoadAffinity` structure is reused from design [Velero Generic Data Path affinity configuration](node-agent-affinity.md).
-It's possible that the users want to choose nodes that match condition A or condition B to run the job.
-For example, the user want to let the nodes is in a specified machine type or the nodes locate in the us-central1-x zones to run the job.
-This can be done by adding multiple entries in the `LoadAffinity` array.
-
-### Affinity Example
-A sample of the ConfigMap is as below:
-``` bash
-cat <<EOF > repo-maintenance-job-config.json
-{
-    "global": {
-        podResources: {
-            "cpuRequest": "100m",
-            "cpuLimit": "200m",
-            "memoryRequest": "100Mi",
-            "memoryLimit": "200Mi"
-        },
-        "loadAffinity": [
-            {
-                "nodeSelector": {
-                    "matchExpressions": [
-                        {
-                            "key": "cloud.google.com/machine-family",
-                            "operator": "In",
-                            "values": [
-                                "e2"
-                            ]
-                        }
-                    ]          
-                }
-            },
-            {
-                "nodeSelector": {
-                    "matchExpressions": [
-                        {
-                            "key": "topology.kubernetes.io/zone",
-                            "operator": "In",
-                            "values": [
-                                "us-central1-a",
-                                "us-central1-b",
-                                "us-central1-c"
-                            ]
-                        }
-                    ]          
-                }
-            }
-        ]
-    }
-}
-EOF
-```
-This sample showcases two affinity configurations:
-- matchLabels: maintenance job runs on nodes with label key `cloud.google.com/machine-family` and value `e2`.
-- matchLabels: maintenance job runs on nodes located in `us-central1-a`, `us-central1-b` and `us-central1-c`.
-The nodes matching one of the two conditions are selected.
-
-To create the configMap, users need to save something like the above sample to a json file and then run below command:
-```
-kubectl create cm repo-maintenance-job-config -n velero --from-file=repo-maintenance-job-config.json
-```
-
-### Value assigning rules
-If the Velero BackupRepositoryController cannot find the introduced ConfigMap, the following default values are used for repository maintenance job:
-``` go
-config := Configs {
-    // LoadAffinity is the config for data path load affinity.
-    LoadAffinity: nil,
-
-    // Resources is the config for the CPU and memory resources setting.
-    PodResources: &kube.PodResources{
-        // The repository maintenance job CPU request setting
-	    CPURequest:   "0m",
-
-        // The repository maintenance job memory request setting
-	    MemoryRequest:   "0Mi",
-
-        // The repository maintenance job CPU limit setting
-	    CPULimit:     "0m",
-
-        // The repository maintenance job memory limit setting
-	    MemoryLimit:     "0Mi",
-    },
-}
-```
-
-If the Velero BackupRepositoryController finds the introduced ConfigMap with only `global` element, the `global` value is used.
-
-If the Velero BackupRepositoryController finds the introduced ConfigMap with only element matches the BackupRepository, the matched element value is used.
-
-
-If the Velero BackupRepositoryController finds the introduced ConfigMap with both `global` element and element matches the BackupRepository, the matched element defined values overwrite the `global` value, and the `global` value is still used for matched element undefined values.
-
-For example, the ConfigMap content has two elements.
-``` json
-{
-    "global": {
-        "loadAffinity": [
-            {
-                "nodeSelector": {
-                    "matchExpressions": [
-                        {
-                            "key": "cloud.google.com/machine-family",
-                            "operator": "In",
-                            "values": [
-                                "e2"
-                            ]
-                        }
-                    ]          
-                }
-            },
-        ],
-        "podResources": {
-            "cpuRequest": "100m",
-            "cpuLimit": "200m",
-            "memoryRequest": "100Mi",
-            "memoryLimit": "200Mi"
-        }
-    },
-    "ns1-default-kopia": {
-        "podResources": {
-            "memoryRequest": "400Mi",
-            "memoryLimit": "800Mi"
-        }
-    }
-}
-```
-The config value used for BackupRepository backing up volume data in namespace `ns1`, referencing BSL `default`, and the type is `Kopia`:
-``` go
-config := Configs {
-    // LoadAffinity is the config for data path load affinity.
-    LoadAffinity: []*kube.LoadAffinity{
-        {
-			NodeSelector: metav1.LabelSelector{
-				MatchExpressions: []metav1.LabelSelectorRequirement{
-					{
-						Key:      "cloud.google.com/machine-family",
-						Operator: metav1.LabelSelectorOpIn,
-						Values:   []string{"e2"},
-					},
-				},
-			},
-		},
-    },
-    PodResources: &kube.PodResources{
-        // The repository maintenance job CPU request setting
-	    CPURequest:   "",
-        // The repository maintenance job memory request setting
-	    MemoryRequest:   "400Mi",
-        // The repository maintenance job CPU limit setting
-	    CPULimit:     "",
-        // The repository maintenance job memory limit setting
-	    MemoryLimit:     "800Mi",
-    }
-}
-```
-
-
-### Implementation
-During the Velero repository controller starts to maintain a repository, it will call the repository manager's `PruneRepo` function to build the maintenance Job.
-The ConfigMap specified by `velero server` CLI parameter `--repo-maintenance-job-configmap` is get to reinitialize the repository `MaintenanceConfig` setting.
-
-``` go
-	jobConfig, err := getMaintenanceJobConfig(
-		context.Background(),
-		m.client,
-		m.log,
-		m.namespace,
-		m.repoMaintenanceJobConfig,
-		repo,
-	)
-	if err != nil {
-        log.Infof("Cannot find the ConfigMap %s with error: %s. Use default value.",
-			m.namespace+"/"+m.repoMaintenanceJobConfig,
-			err.Error(),
-		)
-	}
-
-	log.Info("Start to maintenance repo")
-
-	maintenanceJob, err := m.buildMaintenanceJob(
-		jobConfig,
-		param,
-	)
-	if err != nil {
-		return errors.Wrap(err, "error to build maintenance job")
-	}
-```
-
-## Alternatives Considered
-An other option is creating each ConfigMap for a BackupRepository.
-This is not ideal for scenario that has a lot of BackupRepositories in the cluster.

design/Implemented/resource-status-restore.md

@@ -1,113 +0,0 @@
-# Allow Object-Level Resource Status Restore in Velero
-
-## Abstract
-This design proposes a way to enhance Velero’s restore functionality by enabling object-level resource status restoration through annotations. 
-Currently, Velero allows restoring resource statuses only at a resource type level, which lacks granularity of restoring the status of specific resources. 
-By introducing an annotation that controllers can set on individual resource objects, this design aims to improve flexibility and autonomy for users/resource-controllers, providing a more way
-to enable resource status restore.
-
-
-## Background
-Velero provides the `restoreStatus` field in the Restore API to specify resource types for status restoration. However, this feature is limited to resource types as a whole, lacking the granularity needed to restore specific objects of a resource type. Resource controllers, especially those managing custom resources with external dependencies, may need to restore status on a per-object basis based on internal logic and dependencies.
-
-This design adds an annotation-based approach to allow controllers to specify status restoration at the object level, enabling Velero to handle status restores more flexibly.
-
-## Goals
-- Provide a mechanism to specify the restoration of a resource’s status at an object level.
-- Maintain backwards compatibility with existing functionality, allowing gradual adoption of this feature.
-- Integrate the new annotation-based objects-level status restore with Velero’s existing resource-type-level `restoreStatus` configuration.
-
-## Non-Goals
-- Alter Velero’s existing resource type-level status restoration mechanism for resources without annotations.
-
-## Use-Cases/Scenarios
-
-1. Controller managing specific Resources
-  - A resource controller identifies that a specific object of a resource should have its status restored due to particular dependencies
-  - The controller automatically sets the `velero.io/restore-status: true` annotation on the resource.
-  - During restore, Velero restores the status of this object, while leaving other resources unaffected.
-  - The status for the annotated object will be restored regardless of its inclusion/exclusion in `restoreStatus.includedResources`
-
-2. A specific object must not have its status restored even if its included in `restoreStatus.includedResources`
-  - A user specifies a resource type in the `restoreStatus.includedResources` field within the Restore custom resource.
-  - A particular object of that resource type is annotated with `velero.io/restore-status: false` by the user.
-  - The status of the annotated object will not restored even though its included in `restoreStatus.includedResources` because annotation is `false` and it takes precedence.
-
-4. Default Behavior for objects Without the Annotation
-  - Objects without the `velero.io/restore-status` annotation behave as they currently do: Velero skips their status restoration unless the resource type is specified in the `restoreStatus.includedResources` field.
-
-## High-Level Design
-
-- Object-Level Status Restore Annotation: We are introducing the `velero.io/restore-status` annotation at the resource object level to mark specific objects for status restoration.
-  - `true`: Indicates that the status should be restored for this object
-  - `false`: Skip restoring status for this specific object
-  - Invalid or missing annotations defer to the meaning of existing resource type-level logic.
-
-- Restore logic precedence: 
-  - Annotations take precedence when they exist with valid values (`true` or `false`).
-  - Restore spec `restoreStatus.includedResources` is only used when annotations are invalid or missing.
-
-- Velero Restore Logic Update: During a restore operation, Velero will:
-  - Extend the existing restore logic to parse and prioritize annotations introduced in this design.
-  - Update resource objects accordingly based on their annotation values or fallback configuration.
-
-
-## Detailed Design
-
-- Annotation for object-Level Status Restore: The `velero.io/restore-status` annotation will be set on individual resource objects by users/controllers as needed:
-```yaml
-metadata:
-  annotations:
-    velero.io/restore-status: "true"
-```
-
-- Restore Logic Modifications: During the restore operation, the restore controller will follow these steps:
-   - Parse the `restoreStatus.includedResources` spec to determine resource types eligible for status restoration.
-   - For each resource object:
-     - Check for the `velero.io/restore-status` annotation.
-     - If the annotation value is:
-       - `true`: Restore the status of the object
-       - `false`: Skip restoring the status of the object
-     - If the annotation is invalid or missing:
-       - Default to the `restoreStatus.includedResources` configuration
-
-
-## Implementation
-
-We are targeting the implementation of this design for Velero 1.16 release.
-
-Current restoreStatus logic resides here: https://github.com/vmware-tanzu/velero/blob/32a8c62920ad96c70f1465252c0197b83d5fa6b6/pkg/restore/restore.go#L1652
-
-The modified logic would look somewhat like:
-
-```go
-// Determine whether to restore status from resource type configuration
-shouldRestoreStatus := ctx.resourceStatusIncludesExcludes != nil && ctx.resourceStatusIncludesExcludes.ShouldInclude(groupResource.String())
-
-// Check for object-level annotation
-annotations := obj.GetAnnotations()
-objectAnnotation := annotations["velero.io/restore-status"]
-annotationValid := objectAnnotation == "true" || objectAnnotation == "false"
-
-// Determine restore behavior based on annotation precedence
-shouldRestoreStatus = (annotationValid && objectAnnotation == "true") || (!annotationValid && shouldRestoreStatus)
-
-ctx.log.Debugf("status field for %s: exists: %v, should restore: %v (by annotation: %v)", newGR, statusFieldExists, shouldRestoreStatus, annotationValid)
-
-if shouldRestoreStatus && statusFieldExists {
-    if err := unstructured.SetNestedField(obj.Object, objStatus, "status"); err != nil {
-        ctx.log.Errorf("Could not set status field %s: %v", kube.NamespaceAndName(obj), err)
-        errs.Add(namespace, err)
-        return warnings, errs, itemExists
-    }
-    obj.SetResourceVersion(createdObj.GetResourceVersion())
-    updated, err := resourceClient.UpdateStatus(obj, metav1.UpdateOptions{})
-    if err != nil {
-        ctx.log.Infof("Status field update failed %s: %v", kube.NamespaceAndName(obj), err)
-        warnings.Add(namespace, err)
-	} else {
-        createdObj = updated
-    }
-}
-```
-

design/Implemented/retry-patching-configuration_design.md

@@ -1,111 +0,0 @@
-# Backup Restore Status Patch Retrying Configuration
-
-## Abstract
-When a backup/restore completes, we want to ensure that the custom resource progresses to the correct status.
-If a patch call fails to update status to completion, it should be retried up to a certain time limit.
-
-This design proposes a way to configure timeout for this retry time limit.
-
-## Background
-Original Issue: https://github.com/vmware-tanzu/velero/issues/7207
-
-Velero was performing a restore when the API server was rolling out to a new version.
-It had trouble connecting to the API server, but eventually, the restore was successful.
-However, since the API server was still in the middle of rolling out, Velero failed to update the restore CR status and gave up.
-
-After the connection was restored, it didn't attempt to update, causing the restore CR to be stuck at "In progress" indefinitely.
-This can lead to incorrect decisions for other components that rely on the backup/restore CR status to determine completion.
-
-## Goals
-- Make timeout configurable for retry patching by reusing existing [`--resource-timeout` server flag](https://github.com/vmware-tanzu/velero/blob/d9ca14747925630664c9e4f85a682b5fc356806d/pkg/cmd/server/server.go#L245)
-
-## Non Goals
-- Create a new timeout flag
-- Refactor backup/restore workflow
-
-
-## High-Level Design
-We will add retries with timeout to existing patch calls that moves a backup/restore from InProgress to a different status phase such as
-- FailedValidation (final)
-- Failed (final)
-- WaitingForPluginOperations
-- WaitingForPluginOperationsPartiallyFailed
-- Finalizing
-- FinalizingPartiallyFailed
-
-and from above non final phases to
-- Completed
-- PartiallyFailed
-
-Once backup/restore is in some phase it will already be reconciled again periodically and do not need additional retry
-- WaitingForPluginOperations
-- WaitingForPluginOperationsPartiallyFailed
-
-## Detailed Design
-Relevant reconcilers will have `resourceTimeout   time.Duration` added to its struct and to parameters of New[Backup|Restore]XReconciler functions.
-
-pkg/cmd/server/server.go in `func (s *server) runControllers(..) error` also update the New[Backup|Restore]XCReconciler with added duration parameters using value from existing `--resource-timeout` server flag.
-
-Current calls to kube.PatchResource involving status patch will be replaced with kube.PatchResourceWithRetriesOnErrors added to package `kube` below.
-
-Calls where there is a ...client.Patch() will be wrapped with client.RetriesPhasePatchFuncOnErrors() added to package `client` below.
-
-pkg/util/kube/client.go
-```go
-// PatchResourceWithRetries patches the original resource with the updated resource, retrying when the provided retriable function returns true.
-func PatchResourceWithRetries(maxDuration time.Duration, original, updated client.Object, kbClient client.Client, retriable func(error) bool) error {
-	return veleroPkgClient.RetryOnRetriableMaxBackOff(maxDuration, func() error { return PatchResource(original, updated, kbClient) }, retriable)
-}
-
-// PatchResourceWithRetriesOnErrors patches the original resource with the updated resource, retrying when the operation returns an error.
-func PatchResourceWithRetriesOnErrors(maxDuration time.Duration, original, updated client.Object, kbClient client.Client) error {
-	return PatchResourceWithRetries(maxDuration, original, updated, kbClient, func(err error) bool {
-		// retry using DefaultBackoff to resolve connection refused error that may occur when the server is under heavy load
-		// TODO: consider using a more specific error type to retry, for now, we retry on all errors
-		// specific errors:
-		// - connection refused: https://pkg.go.dev/syscall#:~:text=Errno(0x67)-,ECONNREFUSED,-%3D%20Errno(0x6f
-		return err != nil
-	})
-}
-```
-
-pkg/client/retry.go
-```go
-// CapBackoff provides a backoff with a set backoff cap
-func CapBackoff(cap time.Duration) wait.Backoff {
-	if cap < 0 {
-		cap = 0
-	}
-	return wait.Backoff{
-		Steps:    math.MaxInt,
-		Duration: 10 * time.Millisecond,
-		Cap:      cap,
-		Factor:   retry.DefaultBackoff.Factor,
-		Jitter:   retry.DefaultBackoff.Jitter,
-	}
-}
-
-// RetryOnRetriableMaxBackOff accepts a patch function param, retrying when the provided retriable function returns true.
-func RetryOnRetriableMaxBackOff(maxDuration time.Duration, fn func() error, retriable func(error) bool) error {
-	return retry.OnError(CapBackoff(maxDuration), func(err error) bool { return retriable(err) }, fn)
-}
-
-// RetryOnErrorMaxBackOff accepts a patch function param, retrying when the error is not nil.
-func RetryOnErrorMaxBackOff(maxDuration time.Duration, fn func() error) error {
-	return RetryOnRetriableMaxBackOff(maxDuration, fn, func(err error) bool { return err != nil })
-}
-```
-
-## Alternatives Considered
- - Requeuing InProgress backups that is not known by current velero instance to still be in progress as failed (attempted in [#7863](https://github.com/vmware-tanzu/velero/pull/7863))
-    - It was deemed as making backup restore flow hard to enhance for future reconciler updates such as adding cancel or adding parallel backups.
-
-## Security Considerations
-None
-
-## Compatibility
-Retry should only trigger a restore or backup that is already in progress and not patching successfully by current instance. Prior InProgress backups/restores will not be re-processed and will remain stuck InProgress until there is another velero server (re)start.
-
-## Implementation
-There is a past implementation in [#7845](https://github.com/vmware-tanzu/velero/pull/7845/) where implementation for this design will be based upon.
-

design/Implemented/schedule-skip-immediately-config_design.md

@@ -71,20 +71,6 @@ type ScheduleSpec struct {
 }
 ```
 
-**Note:** The Velero server automatically patches the `skipImmediately` field back to `false` after it's been used. This is because `skipImmediately` is designed to be a one-time operation rather than a persistent state. When the controller detects that `skipImmediately` is set to `true`, it:
-1. Sets the flag back to `false`
-2. Records the current time in `schedule.Status.LastSkipped`
-
-This "consume and reset" pattern ensures that after skipping one immediate backup, the schedule returns to normal behavior for subsequent runs. The `LastSkipped` timestamp is then used to determine when the next backup should run.
-
-```go
-// From pkg/controller/schedule_controller.go
-if schedule.Spec.SkipImmediately != nil && *schedule.Spec.SkipImmediately { 
-    *schedule.Spec.SkipImmediately = false 
-    schedule.Status.LastSkipped = &metav1.Time{Time: c.clock.Now()} 
-} 
-```
-
 `LastSkipped` will be added to `ScheduleStatus` struct to track the last time a schedule was skipped.
 ```diff
 // ScheduleStatus captures the current state of a Velero schedule
@@ -111,8 +97,6 @@ type ScheduleStatus struct {
 }
 ```
 
-The `LastSkipped` field is crucial for the schedule controller to determine the next run time. When a backup is skipped, this timestamp is used instead of `LastBackup` to calculate when the next backup should occur, ensuring the schedule maintains its intended cadence even after skipping a backup.
-
 When `schedule.spec.SkipImmediately` is `true`, `LastSkipped` will be set to the current time, and `schedule.spec.SkipImmediately` set to nil so it can be used again.
 
 The `getNextRunTime()` function below is updated so `LastSkipped` which is after `LastBackup` will be used to determine next run time.

design/Implemented/supporting-volumeattributes-resource-policy.md

@@ -1,84 +0,0 @@
-# Adding Support For VolumeAttributes in Resource Policy
- 
-## Abstract
-Currently [Velero Resource policies](https://velero.io/docs/main/resource-filtering/#creating-resource-policies) are only supporting "Driver" to be filtered for [CSI volume conditions](https://github.com/vmware-tanzu/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28)
-
-If user want to skip certain CSI volumes based on other volume attributes like protocol or SKU, etc, they can't do it with the current Velero resource policies. It would be convenient if Velero resource policies could be extended to filter on volume attributes along with existing driver filter in the resource policies `conditions` to handle the backup of volumes just by `some specific volumes attributes conditions`.
- 
-## Background
-As of Today, Velero resource policy already provides us the way to filter volumes based on the `driver` name. But it's not enough to handle the volumes based on other volume attributes like protocol, SKU, etc.
-
-## Example:
-  - Provision Azure NFS: Define the Storage class with `protocol: nfs` under storage class parameters to provision [CSI NFS Azure File Shares](https://learn.microsoft.com/en-us/azure/aks/azure-files-csi#nfs-file-shares).
-  - User wants to back up AFS (Azure file shares) but only want to backup `SMB` type of file share volumes and not `NFS` file share volumes.
-
-## Goals
-- We are only bringing additional support in the resource policy to only handle volumes during backup.
-- Introducing support for `VolumeAttributes` filter along with `driver` filter in CSI volume conditions to handle volumes.
- 
-## Non-Goals
-- Currently, only handles volumes, and does not support other resources.
- 
-## Use-cases/Scenarios
-### Skip backup volumes by some volume attributes:
-Users want to skip PV with the requirements:
-- option to skip specified PV on volume attributes type (like Protocol as NFS, SMB, etc)
-
-### Sample Storage Class Used to create such Volumes
-```
-apiVersion: storage.k8s.io/v1
-kind: StorageClass
-metadata:
-  name: azurefile-csi-nfs
-provisioner: file.csi.azure.com
-allowVolumeExpansion: true
-parameters:
-  protocol: nfs 
-```
-
-## High-Level Design
-Modifying the existing Resource Policies code for [csiVolumeSource](https://github.com/vmware-tanzu/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources_validator.go#L28C6-L28C22) to add the new `VolumeAttributes` filter for CSI volumes and adding validations in existing [csiCondition](https://github.com/vmware-tanzu/velero/blob/8e23752a6ea83f101bd94a69dcf17f519a805388/internal/resourcepolicies/volume_resources.go#L150) to match with volume attributes in the conditions from Resource Policy config map and original persistent volume.
-
-## Detailed Design
-The volume resources policies should contain a list of policies which is the combination of conditions and related `action`, when target volumes meet the conditions, the related `action` will take effection.
-
-Below is the API Design for the user configuration:
-
-### API Design
-```go
-type csiVolumeSource struct {
-	Driver string `yaml:"driver,omitempty"`
-	// [NEW] CSI volume attributes
-	VolumeAttributes map[string]string `yaml:"volumeAttributes,omitempty"`
-}
-```
-
-The policies YAML config file would look like this:
-```yaml
-version: v1
-volumePolicies:
-  - conditions:
-      csi:
-        driver: disk.csi.azure.com
-    action:
-      type: skip
-  - conditions:
-      csi:
-        driver: file.csi.azure.com
-        volumeAttributes:
-          protocol: nfs
-    action:
-      type: skip`
-```
- 
-### New Supported Conditions
-#### VolumeAttributes
-Existing CSI Volume Condition can now add `volumeAttributes` which will be key and value pairs.  
-
- Specify details for the related volume source (currently only csi driver is supported filter)
-     ```yaml
-     csi: // match volume using `file.csi.azure.com` and with volumeAttributes protocol as nfs
-       driver: file.csi.azure.com 
-       volumeAttributes:
-          protocol: nfs
-     ```

design/Implemented/vgdp-affinity-enhancement.md

@@ -1,257 +0,0 @@
-# Velero Generic Data Path Load Affinity Enhancement Design
-
-## Glossary & Abbreviation
-
-**Velero Generic Data Path (VGDP)**: VGDP is the collective modules that is introduced in [Unified Repository design][1]. Velero uses these modules to finish data transfer for various purposes (i.e., PodVolume backup/restore, Volume Snapshot Data Movement). VGDP modules include uploaders and the backup repository. 
-
-**Exposer**: Exposer is a module that is introduced in [Volume Snapshot Data Movement Design][1]. Velero uses this module to expose the volume snapshots to Velero node-agent pods or node-agent associated pods so as to complete the data movement from the snapshots.
-
-## Background
-
-The implemented [VGDP LoadAffinity design][3] already defined the a structure `LoadAffinity` in `--node-agent-configmap` parameter. The parameter is used to set the affinity of the backupPod of VGDP.
-
-There are still some limitations of this design:
-* The affinity setting is global. Say there are two StorageClasses and the underlying storage can only provision volumes to part of the cluster nodes. The supported nodes don't have intersection. Then the affinity will definitely not work in some cases.
-* The old design focuses on the backupPod affinity, but the restorePod also needs the affinity setting.
-
-As a result, create this design to address the limitations.
-
-## Goals
-
-- Enhance the node affinity of VGDP instances for volume snapshot data movement: add per StorageClass node affinity.
-- Enhance the node affinity of VGDP instances for volume snapshot data movement: support the or logic between affinity selectors.
-- Define the behaviors of node affinity of VGDP instances in node-agent for volume snapshot data movement restore, when the PVC restore doesn't require delay binding.
-
-## Non-Goals
-
-- It is also beneficial to support VGDP instances affinity for PodVolume backup/restore, this will be implemented after the PodVolume micro service completes.
-
-## Solution
-
-This design still uses the ConfigMap specified by `velero node-agent` CLI's parameter `--node-agent-configmap` to host the node affinity configurations.
-
-Upon the implemented [VGDP LoadAffinity design][3] introduced `[]*LoadAffinity` structure, this design add a new field `StorageClass`. This field is optional.
-* If the `LoadAffinity` element's `StorageClass` doesn't have value, it means this element is applied to global, just as the old design.
-* If the `LoadAffinity` element's `StorageClass` has value, it means this element is applied to the VGDP instances' PVCs use the specified StorageClass.
-* The `LoadAffinity` element whose `StorageClass` has value has higher priority than the `LoadAffinity` element whose `StorageClass` doesn't have value.
-
-
-```go
-type Configs struct {
-    // LoadConcurrency is the config for load concurrency per node.
-    LoadConcurrency *LoadConcurrency `json:"loadConcurrency,omitempty"`
-
-    // LoadAffinity is the config for data path load affinity.
-    LoadAffinity []*LoadAffinity `json:"loadAffinity,omitempty"`    
-}
-
-type LoadAffinity struct {
-    // NodeSelector specifies the label selector to match nodes
-    NodeSelector metav1.LabelSelector `json:"nodeSelector"`
-}
-```
-
-``` go
-type LoadAffinity struct {
-    // NodeSelector specifies the label selector to match nodes
-    NodeSelector metav1.LabelSelector `json:"nodeSelector"`
-
-    // StorageClass specifies the VGDPs the LoadAffinity applied to. If the StorageClass doesn't have value, it applies to all. If not, it applies to only the VGDPs that use this StorageClass.
-    StorageClass string `json:"storageClass"`
-}
-```
-
-### Decision Tree
-
-```mermaid
-flowchart TD
-    A[VGDP Pod Needs Scheduling] --> B{Is this a restore operation?}
-    
-    B -->|Yes| C{StorageClass has volumeBindingMode: WaitForFirstConsumer?}
-    B -->|No| D[Backup Operation]
-    
-    C -->|Yes| E{restorePVC.ignoreDelayBinding = true?}
-    C -->|No| F[StorageClass binding mode: Immediate]
-    
-    E -->|No| G[Wait for target Pod scheduling<br/>Use Pod's selected node<br/>⚠️ Affinity rules ignored]
-    E -->|Yes| H[Apply affinity rules<br/>despite WaitForFirstConsumer]
-    
-    F --> I{Check StorageClass in loadAffinity by StorageClass field}
-    H --> I
-    D --> J{Using backupPVC with different StorageClass?}
-    
-    J -->|Yes| K[Use final StorageClass<br/>for affinity lookup]
-    J -->|No| L[Use original PVC StorageClass<br/>for affinity lookup]
-    
-    K --> I
-    L --> I
-    
-    I -->|StorageClass found| N[Filter the LoadAffinity by <br/>the StorageClass<br/>🎯 and apply the LoadAffinity HIGHEST PRIORITY]
-    I -->|StorageClass not found| O{Check loadAffinity element without StorageClass field}
-
-    O -->|No loadAffinity configured| R[No affinity constraints<br/>Schedule on any available node<br/>🌐 DEFAULT]
-    
-    O --> V[Validate node-agent availability<br/>⚠️ Ensure node-agent pods exist on target nodes]
-    N --> V
-    
-    V --> W{Node-agent available on selected nodes?}
-    W -->|Yes| X[✅ VGDP Pod scheduled successfully]
-    W -->|No| Y[❌ Pod stays in Pending state<br/>Timeout after 30min<br/>Check node-agent DaemonSet coverage]
-    
-    R --> Z[Schedule on any node<br/>✅ Basic scheduling]
-    
-    %% Styling
-    classDef successNode fill:#d4edda,stroke:#155724,color:#155724
-    classDef warningNode fill:#fff3cd,stroke:#856404,color:#856404
-    classDef errorNode fill:#f8d7da,stroke:#721c24,color:#721c24
-    classDef priorityHigh fill:#e7f3ff,stroke:#0066cc,color:#0066cc
-    classDef priorityMedium fill:#f0f8ff,stroke:#4d94ff,color:#4d94ff
-    classDef priorityDefault fill:#f8f9fa,stroke:#6c757d,color:#6c757d
-    
-    class X,Z successNode
-    class G,V,Y warningNode
-    class Y errorNode
-    class N,T,U priorityHigh
-    class P,Q priorityMedium
-    class R priorityDefault
-```
-
-### Examples
-
-#### LoadAffinity interacts with LoadAffinityPerStorageClass
-
-``` json
-{
-    "loadAffinity": [
-        {
-            "nodeSelector": {
-                "matchLabels": {
-                    "beta.kubernetes.io/instance-type": "Standard_B4ms"
-                }
-            }
-        },
-        {
-            "nodeSelector": {
-                "matchExpressions": [
-                    {
-                        "key": "kubernetes.io/os",
-                        "values": [
-                            "linux"
-                        ],
-                        "operator": "In"
-                    }
-                ]
-            },
-            "storageClass": "kibishii-storage-class"
-        },
-        {
-            "nodeSelector": {
-                "matchLabels": {
-                    "beta.kubernetes.io/instance-type": "Standard_B8ms"
-                }
-            },
-            "storageClass": "kibishii-storage-class"
-        }
-    ]
-}
-```
-
-This sample demonstrates how the `loadAffinity` elements with `StorageClass` field and without `StorageClass` field setting work together.
-If the VGDP mounting volume is created from StorageClass `kibishii-storage-class`, its pod will run Linux nodes or instance type as `Standard_B8ms`.
-
-The other VGDP instances will run on nodes, which instance type is `Standard_B4ms`.
-
-#### LoadAffinity interacts with BackupPVC
-
-``` json
-{
-    "loadAffinity": [
-        {
-            "nodeSelector": {
-                "matchLabels": {
-                    "beta.kubernetes.io/instance-type": "Standard_B4ms"
-                }
-            },
-            "storageClass": "kibishii-storage-class"
-        },
-        {
-            "nodeSelector": {
-                "matchLabels": {
-                    "beta.kubernetes.io/instance-type": "Standard_B2ms"
-                }
-            },
-            "storageClass": "worker-storagepolicy"
-        }
-    ],
-    "backupPVC": {
-        "kibishii-storage-class": {
-            "storageClass": "worker-storagepolicy"
-        }
-    }
-}
-```
-
-Velero data mover supports to use different StorageClass to create backupPVC by [design](https://github.com/vmware-tanzu/velero/pull/7982).
-
-In this example, if the backup target PVC's StorageClass is `kibishii-storage-class`, its backupPVC should use StorageClass `worker-storagepolicy`. Because the final StorageClass is `worker-storagepolicy`, the backupPod uses the loadAffinity specified by `loadAffinity`'s elements with `StorageClass` field set to `worker-storagepolicy`. backupPod will be assigned to nodes, which instance type is `Standard_B2ms`.
-
-
-#### LoadAffinity interacts with RestorePVC
-
-``` json
-{
-    "loadAffinity": [
-        {
-            "nodeSelector": {
-                "matchLabels": {
-                    "beta.kubernetes.io/instance-type": "Standard_B4ms"
-                }
-            },
-            "storageClass": "kibishii-storage-class"
-        }
-    ],
-    "restorePVC": {
-        "ignoreDelayBinding": false
-    }
-}
-```
-
-##### StorageClass's bind mode is WaitForFirstConsumer
-
-``` yaml
-apiVersion: storage.k8s.io/v1
-kind: StorageClass
-metadata:
-  name: kibishii-storage-class
-parameters:
-  svStorageClass: worker-storagepolicy
-provisioner: csi.vsphere.vmware.com
-reclaimPolicy: Delete
-volumeBindingMode: WaitForFirstConsumer
-```
-
-If restorePVC should be created from StorageClass `kibishii-storage-class`, and it's volumeBindingMode is `WaitForFirstConsumer`.
-Although `loadAffinityPerStorageClass` has a section matches the StorageClass, the `ignoreDelayBinding` is set `false`, the Velero exposer will wait until the target Pod scheduled to a node, and returns the node as SelectedNode for the restorePVC.
-As a result, the `loadAffinityPerStorageClass` will not take affect.
-
-##### StorageClass's bind mode is Immediate
-
-``` yaml
-apiVersion: storage.k8s.io/v1
-kind: StorageClass
-metadata:
-  name: kibishii-storage-class
-parameters:
-  svStorageClass: worker-storagepolicy
-provisioner: csi.vsphere.vmware.com
-reclaimPolicy: Delete
-volumeBindingMode: Immediate
-```
-
-Because the StorageClass volumeBindingMode is `Immediate`, although `ignoreDelayBinding` is set to `false`, restorePVC will not be created according to the target Pod.
-
-The restorePod will be assigned to nodes, which instance type is `Standard_B4ms`.
-
-[1]: Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
-[2]: Implemented/volume-snapshot-data-movement/volume-snapshot-data-movement.md
-[3]: Implemented/node-agent-affinity.md

design/Implemented/vgdp-micro-service-for-fs-backup/vgdp-micro-service-for-fs-backup.md

@@ -1,662 +0,0 @@
-# VGDP Micro Service For fs-backup
-
-## Glossary & Abbreviation
-
-**VGDP**: Velero Generic Data Path. The collective modules that is introduced in [Unified Repository design][1]. Velero uses these modules to finish data transmission for various purposes. It includes uploaders and the backup repository.  
-**fs-backup**: Also known as pod volume backup (PVB)/pod volume restore (PVR). It is one of the primary backup methods built-in with Velero. It has been refactored in [Unified Repository design][1].  
-**PVB**: Pod Volume Backup, the internal name for backup part of fs-backup.  
-**PVR**: Pod Volume Restore, the internal name for restore part of fs-backup.  
-**Exposer**: Exposer is introduced in [Volume Snapshot Data Movement design][2] and is used to expose the volume snapshots/volumes for VGDP to access locally.  
-**VGDP MS**: VGDP Micro Service, it is introduced in [VGDP Micro Service For Volume Snapshot Data Movement][3]. It hosts VGDP instances in dedicated backup/restore pods, instead of in node-agent pods.   
-
-## Background
-As described in [VGDP Micro Service For Volume Snapshot Data Movement][3], hosting VGDP instances in dedicated pods has solved many major problems and brought significant improvements in scalability. These improvements are also effective for fs-backup. And besides the benefits listed in [VGDP Micro Service For Volume Snapshot Data Movement][3], we can also see below ones specifically for fs-backup:
-- This enables fs-backup to support Windows workloads. Windows doesn't support propagate mount, so the current fs-backup solution doesn't work for Windows nodes and Windows workloads. However, if the final host-path for the source volume is mounted to the VGDP MS pods, it should work.   
-- This enables fs-backup to reuse the existing VGDP features seamlessly, i.e., concurrency control, node selector, etc.
-
-By moving all VGDP instances out of node-agent pods, we would further get prepared for below important features and improvements:
-- NFS support: NFS volumes are mounted to VGDP MS pods, so node-agent pods don't need to restart when a new BSL is added.
-- Performance improvement for Kopia uploader restore ([#7725][9]): dedicated cache volumes could be mounted to the VGDP MS pods, without affecting node-agent pods.
-- Controllable resource usage for node-agent: node-agent pods are long running and so not suitable for data path activities as the OS usually reclaim memory in a lazy reclaim behavior, so the unused memory may be shown as occupied by node-agent pods, which misleads Kubernetes or other related sub system. After this change, node-agent pods no longer require large resource (CPU/memory) usage, so no obvious memory retain will be observed.
-- Simplify node-agent configuration: host-path mounts, root user and privileged mode are no longer required by node-agent; and the configuration differences of node-agent for linux and Windows nodes could be eliminated. 
-
-## Goals
-- Create a solution to make VGDP instances as micro services for fs-backup
-- Modify the fs-backup workflow to offload the VGDP work from node-agent to the VGDP MS
-- Create the mechanism for fs-backup to control and monitor the VGDP MS in various scenarios
-
-## Non-Goals
-- The current solution covers the VGDP Micro Service for fs-backup itself, the potentional features/improvements that rely on this solution will be covered by further designs and implementations.   
-
-
-## Overview
-The solution is based on [VGDP Micro Service For Volume Snapshot Data Movement][3], the architecture is followed as is and existing components are not changed unless it is necessary.  
-Below diagram shows how these components work together:  
-![vgdp-ms-1.png](vgdp-ms-1.png)  
-
-Below lists the changed components, why and how:  
-**Pod-Volume Exposer**: A new exposer, pod-volume exposer is added. It retrieves the host path of the specific volume and then creates the backupPod/restorePod and mounts the host path to the pod. The command of the backupPod/restorePod is also changed to launch VGDP MS for PVB/PVR.  
-**PVB/PVR Controller**: The PVB/PVR controllers are refactored to work with podVolume exposer, VGDP-MS, etc. The controllers will also support Cancel and resume. So PVB/PVR CRD is also refactored to support these scenarios.    
-**PVB/PVR VGDP-MS**: New commands for PVB/PVR VGDP-MS are added. The VGDP instances are started in the backupPod/restorePod as result of the commands.  
-
-The VGDP Watcher and its mechanism are fully reused.
-
-The [Node-agent concurrency][4] is reused to control the concurrency of VGDP MS for fs-backup. When there are too many volumes in the backup/restore, which takes too much computing resources(CPU, memory, etc.) or Kubernetes resources(pods, PVCs, PVs, etc.), users could set the concurrency in each node so as to control the total number of concurrent VGDP instances in the cluster.  
-
-## Detailed Design
-### Exposer
-As the old behavior, the host path (e.g., `/var/lib/kubelet/pods`) for the Kubernetes pods are mounted to node-agent pods, then the VGDP instances running in the same pods access the data through subdir of the host path for a specific volume, e.g.,  `/var/lib/kubelet/pods/<pod UID>/volumes/kubernetes.io~csi/<PVC name>/mount`. Therefore, a node-agent pod could access all volumes attached to the same node.  
-For the new implementation, the exposer retrieves the host path for a specific volume directly, and then mount that host path to the backupPod/restorePod. This also means that the backupPod/restorePod could only access the volume to be backed up or restored.    
-
-The exposer creates backupPod/restorePod and sets ```velero pod-volume``` as the command run by backupPod/restorePod. And `velero` image is used for the backupPod/restorePod.   
-There are sub commands varying from backup and restore:  
-```velero pod-volume backup --volume-path xxx --pod-volume-backup xxx --resource-timeout xxx --log-format xxx --log-level xxx```  
-Or:  
-```velero pod-volume restore --volume-path xxx --pod-volume-restore xxx --resource-timeout xxx --log-format xxx --log-level xxx```  
-
-Below are the parameters of the commands:  
-**volume-path**: Deliver the full path inside the backupPod/restorePod for the volume to be backed up/restored.    
-**pod-volume-backup**: PVB CR for this backup.  
-**pod-volume-restore**: PVR CR for this restore.  
-**resource-timeout**: resource-timeout is used to control the timeout for operations related to resources. It has the same meaning with the resource-timeout for node-agent.  
-**log-format** and **log-level**: This is to control the behavior of log generation inside VGDP-MS.  
-
-Below pod configurations are inherited from node-agent and set to backupPod/restorePod's spec:
-- Volumes: Some configMaps will be mapped as volumes to node-agent, so we add the same volumes of node-agent to the backupPod/restorePod
-- Environment Variables
-- Security Contexts  
-
-Since the volume data is still accessed by host path, the backupPod/restorePod may still need to run in Privileged mode in some environments. Therefore, the Privileged mode setting which is a part of Security Contexts will be inherited from node-agent.    
-The root user is still required, especially by the restore (in order to restore the file system attributes, owners, etc.), so we will use root user for backupPod/restorePod.  
-
-As same as [VGDP Micro Service For Volume Snapshot Data Movement][3], the backupPod/restorePods's ```RestartPolicy``` is set to ```RestartPolicyNever```, so that once VGDP-MS terminates for any reason, backupPod/restorePod won't restart and the PVB/PVR is marked as one of the terminal phases (Completed/Failed/Cancelled) accordingly.  
-
-### VGDP Watcher
-The VGDP watcher is fully reused, specifically, we still use the dual mode event watcher to watch the status change from backupPod/restorePod or the VGDP instance.  
-The AsyncBR adapter and its interface is also fully reused.  
-
-### VGDP-MS
-The VGDP-MS that is represented by ```velero pod-volume``` keeps the same workflow as [VGDP Micro Service For Volume Snapshot Data Movement][3]:  
-![vgdp-ms-2.png](vgdp-ms-2.png)  
-
-**Start DUCR/DDCR Watcher**: The same as [VGDP Micro Service For Volume Snapshot Data Movement][3], except that it watches PVB/PVR CRs.  
-**Wait DUCR/DDCR InProgress**: The same as The same as [VGDP Micro Service For Volume Snapshot Data Movement][3], VGDP-MS won't start the VGDP instance until PVB/PVR CR turns to ```InProgress```.  
-**Record VGDP Starts**: The same as [VGDP Micro Service For Volume Snapshot Data Movement][3].  
-**VGDP Callbacks**: The same as [VGDP Micro Service For Volume Snapshot Data Movement][3].  
-**Record VGDP Ends**: The same as [VGDP Micro Service For Volume Snapshot Data Movement][3].    
-**Record VGDP Progress**: The same as [VGDP Micro Service For Volume Snapshot Data Movement][3].  
-**Set VGDP Output**: The same as [VGDP Micro Service For Volume Snapshot Data Movement][3].  
-
-The return message for VGDP completion is also reused, except that `VolMode` is always set to `PersistentVolumeFilesystem`:  
-```
-type BackupResult struct {
-    SnapshotID    string              `json:"snapshotID"`
-    EmptySnapshot bool                `json:"emptySnapshot"`
-    Source        exposer.AccessPoint `json:"source,omitempty"`
-}
-```
-```
-type RestoreResult struct {
-    Target exposer.AccessPoint `json:"target,omitempty"`
-}
-```  
-``` 
-type AccessPoint struct {
-    ByPath  string                        `json:"byPath"`
-    VolMode uploader.PersistentVolumeMode `json:"volumeMode"`
-}
-``` 
-
-And the mechanism and data struct for Progress update is also reused:
-``` 
-type Progress struct {
-    TotalBytes int64 `json:"totalBytes,omitempty"`
-    BytesDone  int64 `json:"doneBytes,omitempty"`
-}
-```    
-
-### Log Collection
-The log collection mechanism is the same as [VGDP Micro Service For Volume Snapshot Data Movement][3].       
-
-### Resource Control
-The resource control mechanism is the same as [VGDP Micro Service For Volume Snapshot Data Movement][3].  
-
-### Restic Restore
-As the current Restic path deprecation process, restore is still supported. On the other hand, we don't want to support Restic path for this new VGDP MS implementation.  
-Therefore, the legacy PVR controller and workflow is preserved for Restic path restore.  The controller watches legacy PVRs only, and then launches the legacy workflow. Meawhile, the new PVR controller should skip legacy PVRs.  
-After Restic path is full deprecated, the code for the legacy controller and workflow should be removed.  
-
-### Velero Server Restarts
-The backup/restore stays in InProgress phase during the running of PVB/PVR, no phase changes between completion of item iteration and completion of PVB/PVR.   As a result, on Velero server restarts, there is no way to resume a backup/restore.  
-Therefore, the backup/restore will be be marked as Failed, which is the same as the old behavior. And it is still not as good as CSI snapshot data movement for which the backup/restore could be resumed as long as it has iterated all items.  
-By the meanwhile, there is indeed some improvements. As the old behavior, once the backup/restore is set as Failed on Velero server restart, the running PVB/PVR will be left there, as a result, the VGDP instances may run for a long time and take lots of resource for nothing; for the new implementation, PVB/PVR will be set as Cancel immediately after the backup/restore is set as Failed.  
-
-### node-agent Restarts
-As the old behavior, once a node-agent pod restarts, all the PVBs/PVRs running in the same node will be set as Failed as there is no way to resume the VGDP instances for them.  
-For the new implementation, since the VGDP instances run in dedicated backupPods/restorePods without affected, the PVBs/PVRs will be resumed after node-agent restarts. This includes PVBs/PVRs in all phases.  
-
-The legacy PVRs handling Restic restore are processed by the old workflow, so they will still be set as Failed on node-agent restart.  
-
-### Windows Support
-Windows nodes and workloads will be supported by following the same changes for CSI snapshot data movement as listed in [Velero Windows Support][7]. There are some additional changes particularly for PVB/PVR.   
-
-#### Restore Helper 
-PVR requires an init-container, called `restore-wait`, to run in the workload pod. There are default configurations for the container and users could customize them by the `pod-volume-restore` RIA plugin configMap.
-The `pod-volume-restore` RIA is used to config the init-container, so it should support Windows pods for all the configurations.  
-Meanwhile, the customized options in the configMap should also support Windows pods. If an option is not suitable for Windows pods, it will be ignored by the RIA.  
-
-By default, the init-container uses `velero` image with a binary called `velero-restore-helper` inside, so that binary should be compiled and assembled to the `velero` image for Windows.  
-
-#### Privileged mode
-Privileged pods are implemented by [HostProcess Pods][8] on Windows and need to be specially configured. And there are many constrains for it.  
-As one of the constrains, HostProcess pods supports Windows service accounts only. As a result, restore will not be able to support it until [#8423][10] is fixed, otherwise, the restored files are not usable by workloads which run under genneral container users, e.g., `containerUser` or `containerAdministrator`.  
-Therefore, as the current implementation, fs-backup will not support Windows workloads in the environments where Privileged mode is required. A limitation should be documented.  
-
-## node-agent
-node-agent is required to host the PVB/PVR controller which reconciles PVB/PVR and operates PVB/PVR in other steps before the VGDP instance is started, i.e., Accept, Expose, etc.  
-node-agent still requires host path mount because of two deprecating features [in-tree storage provider support deprecation][5] and [emptyDir volume support deprecation][6]. As a result, Privileged mode and root user are still required in some environments. Therefore, we will keep the node-agent deamonset as is, until the two deprecations complete.   
-
-## CRD Changes
-In order to support the VGDP MS workflow, some elements in the PVB/PVR CRDs are added or extended:
-- New phases are added for PVB/PVR: `PodVolumeBackupPhaseAccepted`, `PodVolumeBackupPhasePrepared`, `PodVolumeBackupPhaseCanceling`, `PodVolumeBackupPhaseCanceled`; `PodVolumeRestorePhaseAccepted`, `PodVolumeRestorePhasePrepared`, `PodVolumeRestorePhaseCanceling`, `PodVolumeRestorePhaseCanceled`.  
-- New fields are added to PVB/PVR spec to support cancel: `Cancel bool`
-- New fields are added to PVB/PVR spec to support the accept phase and processing: `AcceptedTimestamp *metav1.Time`
-- A new field, which records the node the PVR is running, is added to PVR Status: `Node string`
-
-New changes happen to Backup/Restore CRDs.  
-
-Below is the new PVB CRD:
-```yaml
-apiVersion: apiextensions.k8s.io/v1
-kind: CustomResourceDefinition
-metadata:
-  annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
-  name: podvolumebackups.velero.io
-spec:
-  group: velero.io
-  names:
-    kind: PodVolumeBackup
-    listKind: PodVolumeBackupList
-    plural: podvolumebackups
-    singular: podvolumebackup
-  scope: Namespaced
-  versions:
-  - additionalPrinterColumns:
-    - description: PodVolumeBackup status such as New/InProgress
-      jsonPath: .status.phase
-      name: Status
-      type: string
-    - description: Time duration since this PodVolumeBackup was started
-      jsonPath: .status.startTimestamp
-      name: Started
-      type: date
-    - description: Completed bytes
-      format: int64
-      jsonPath: .status.progress.bytesDone
-      name: Bytes Done
-      type: integer
-    - description: Total bytes
-      format: int64
-      jsonPath: .status.progress.totalBytes
-      name: Total Bytes
-      type: integer
-    - description: Name of the Backup Storage Location where this backup should be
-        stored
-      jsonPath: .spec.backupStorageLocation
-      name: Storage Location
-      type: string
-    - description: Time duration since this PodVolumeBackup was created
-      jsonPath: .metadata.creationTimestamp
-      name: Age
-      type: date
-    - description: Name of the node where the PodVolumeBackup is processed
-      jsonPath: .status.node
-      name: Node
-      type: string
-    - description: The type of the uploader to handle data transfer
-      jsonPath: .spec.uploaderType
-      name: Uploader
-      type: string
-    name: v1
-    schema:
-      openAPIV3Schema:
-        properties:
-          apiVersion:
-            description: |-
-              APIVersion defines the versioned schema of this representation of an object.
-              Servers should convert recognized schemas to the latest internal value, and
-              may reject unrecognized values.
-              More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
-            type: string
-          kind:
-            description: |-
-              Kind is a string value representing the REST resource this object represents.
-              Servers may infer this from the endpoint the client submits requests to.
-              Cannot be updated.
-              In CamelCase.
-              More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
-            type: string
-          metadata:
-            type: object
-          spec:
-            description: PodVolumeBackupSpec is the specification for a PodVolumeBackup.
-            properties:
-              backupStorageLocation:
-                description: |-
-                  BackupStorageLocation is the name of the backup storage location
-                  where the backup repository is stored.
-                type: string
-              cancel:
-                description: |-
-                  Cancel indicates request to cancel the ongoing PodVolumeBackup. It can be set
-                  when the PodVolumeBackup is in InProgress phase
-                type: boolean
-              node:
-                description: Node is the name of the node that the Pod is running
-                  on.
-                type: string
-              pod:
-                description: Pod is a reference to the pod containing the volume to
-                  be backed up.
-                properties:
-                  apiVersion:
-                    description: API version of the referent.
-                    type: string
-                  fieldPath:
-                    description: |-
-                      If referring to a piece of an object instead of an entire object, this string
-                      should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2].
-                      For example, if the object reference is to a container within a pod, this would take on a value like:
-                      "spec.containers{name}" (where "name" refers to the name of the container that triggered
-                      the event) or if no container name is specified "spec.containers[2]" (container with
-                      index 2 in this pod). This syntax is chosen only to have some well-defined way of
-                      referencing a part of an object.
-                    type: string
-                  kind:
-                    description: |-
-                      Kind of the referent.
-                      More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
-                    type: string
-                  name:
-                    description: |-
-                      Name of the referent.
-                      More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
-                    type: string
-                  namespace:
-                    description: |-
-                      Namespace of the referent.
-                      More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
-                    type: string
-                  resourceVersion:
-                    description: |-
-                      Specific resourceVersion to which this reference is made, if any.
-                      More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency
-                    type: string
-                  uid:
-                    description: |-
-                      UID of the referent.
-                      More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids
-                    type: string
-                type: object
-                x-kubernetes-map-type: atomic
-              repoIdentifier:
-                description: RepoIdentifier is the backup repository identifier.
-                type: string
-              tags:
-                additionalProperties:
-                  type: string
-                description: |-
-                  Tags are a map of key-value pairs that should be applied to the
-                  volume backup as tags.
-                type: object
-              uploaderSettings:
-                additionalProperties:
-                  type: string
-                description: |-
-                  UploaderSettings are a map of key-value pairs that should be applied to the
-                  uploader configuration.
-                nullable: true
-                type: object
-              uploaderType:
-                description: UploaderType is the type of the uploader to handle the
-                  data transfer.
-                enum:
-                - kopia
-                - ""
-                type: string
-              volume:
-                description: |-
-                  Volume is the name of the volume within the Pod to be backed
-                  up.
-                type: string
-            required:
-            - backupStorageLocation
-            - node
-            - pod
-            - repoIdentifier
-            - volume
-            type: object
-          status:
-            description: PodVolumeBackupStatus is the current status of a PodVolumeBackup.
-            properties:
-              acceptedTimestamp:
-                description: |-
-                  AcceptedTimestamp records the time the pod volume backup is to be prepared.
-                  The server's time is used for AcceptedTimestamp
-                format: date-time
-                nullable: true
-                type: string
-              completionTimestamp:
-                description: |-
-                  CompletionTimestamp records the time a backup was completed.
-                  Completion time is recorded even on failed backups.
-                  Completion time is recorded before uploading the backup object.
-                  The server's time is used for CompletionTimestamps
-                format: date-time
-                nullable: true
-                type: string
-              message:
-                description: Message is a message about the pod volume backup's status.
-                type: string
-              path:
-                description: Path is the full path within the controller pod being
-                  backed up.
-                type: string
-              phase:
-                description: Phase is the current state of the PodVolumeBackup.
-                enum:
-                - New
-                - Accepted
-                - Prepared
-                - InProgress
-                - Canceling
-                - Canceled
-                - Completed
-                - Failed
-                type: string
-              progress:
-                description: |-
-                  Progress holds the total number of bytes of the volume and the current
-                  number of backed up bytes. This can be used to display progress information
-                  about the backup operation.
-                properties:
-                  bytesDone:
-                    format: int64
-                    type: integer
-                  totalBytes:
-                    format: int64
-                    type: integer
-                type: object
-              snapshotID:
-                description: SnapshotID is the identifier for the snapshot of the
-                  pod volume.
-                type: string
-              startTimestamp:
-                description: |-
-                  StartTimestamp records the time a backup was started.
-                  Separate from CreationTimestamp, since that value changes
-                  on restores.
-                  The server's time is used for StartTimestamps
-                format: date-time
-                nullable: true
-                type: string
-            type: object
-        type: object
-    served: true
-    storage: true
-    subresources: {}
-```
-
-Below is the new PVR CRD:
-```yaml
-apiVersion: apiextensions.k8s.io/v1
-kind: CustomResourceDefinition
-metadata:
-  annotations:
-    controller-gen.kubebuilder.io/version: v0.16.5
-  name: podvolumerestores.velero.io
-spec:
-  group: velero.io
-  names:
-    kind: PodVolumeRestore
-    listKind: PodVolumeRestoreList
-    plural: podvolumerestores
-    singular: podvolumerestore
-  scope: Namespaced
-  versions:
-  - additionalPrinterColumns:
-    - description: PodVolumeRestore status such as New/InProgress
-      jsonPath: .status.phase
-      name: Status
-      type: string
-    - description: Time duration since this PodVolumeRestore was started
-      jsonPath: .status.startTimestamp
-      name: Started
-      type: date
-    - description: Completed bytes
-      format: int64
-      jsonPath: .status.progress.bytesDone
-      name: Bytes Done
-      type: integer
-    - description: Total bytes
-      format: int64
-      jsonPath: .status.progress.totalBytes
-      name: Total Bytes
-      type: integer
-    - description: Name of the Backup Storage Location where the backup data is stored
-      jsonPath: .spec.backupStorageLocation
-      name: Storage Location
-      type: string
-    - description: Time duration since this PodVolumeRestore was created
-      jsonPath: .metadata.creationTimestamp
-      name: Age
-      type: date
-    - description: Name of the node where the PodVolumeRestore is processed
-      jsonPath: .status.node
-      name: Node
-      type: string
-    - description: The type of the uploader to handle data transfer
-      jsonPath: .spec.uploaderType
-      name: Uploader Type
-      type: string
-    name: v1
-    schema:
-      openAPIV3Schema:
-        properties:
-          apiVersion:
-            description: |-
-              APIVersion defines the versioned schema of this representation of an object.
-              Servers should convert recognized schemas to the latest internal value, and
-              may reject unrecognized values.
-              More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
-            type: string
-          kind:
-            description: |-
-              Kind is a string value representing the REST resource this object represents.
-              Servers may infer this from the endpoint the client submits requests to.
-              Cannot be updated.
-              In CamelCase.
-              More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
-            type: string
-          metadata:
-            type: object
-          spec:
-            description: PodVolumeRestoreSpec is the specification for a PodVolumeRestore.
-            properties:
-              backupStorageLocation:
-                description: |-
-                  BackupStorageLocation is the name of the backup storage location
-                  where the backup repository is stored.
-                type: string
-              cancel:
-                description: |-
-                  Cancel indicates request to cancel the ongoing PodVolumeRestore. It can be set
-                  when the PodVolumeRestore is in InProgress phase
-                type: boolean
-              pod:
-                description: Pod is a reference to the pod containing the volume to
-                  be restored.
-                properties:
-                  apiVersion:
-                    description: API version of the referent.
-                    type: string
-                  fieldPath:
-                    description: |-
-                      If referring to a piece of an object instead of an entire object, this string
-                      should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2].
-                      For example, if the object reference is to a container within a pod, this would take on a value like:
-                      "spec.containers{name}" (where "name" refers to the name of the container that triggered
-                      the event) or if no container name is specified "spec.containers[2]" (container with
-                      index 2 in this pod). This syntax is chosen only to have some well-defined way of
-                      referencing a part of an object.
-                    type: string
-                  kind:
-                    description: |-
-                      Kind of the referent.
-                      More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
-                    type: string
-                  name:
-                    description: |-
-                      Name of the referent.
-                      More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
-                    type: string
-                  namespace:
-                    description: |-
-                      Namespace of the referent.
-                      More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
-                    type: string
-                  resourceVersion:
-                    description: |-
-                      Specific resourceVersion to which this reference is made, if any.
-                      More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency
-                    type: string
-                  uid:
-                    description: |-
-                      UID of the referent.
-                      More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids
-                    type: string
-                type: object
-                x-kubernetes-map-type: atomic
-              repoIdentifier:
-                description: RepoIdentifier is the backup repository identifier.
-                type: string
-              snapshotID:
-                description: SnapshotID is the ID of the volume snapshot to be restored.
-                type: string
-              sourceNamespace:
-                description: SourceNamespace is the original namespace for namespace
-                  mapping.
-                type: string
-              uploaderSettings:
-                additionalProperties:
-                  type: string
-                description: |-
-                  UploaderSettings are a map of key-value pairs that should be applied to the
-                  uploader configuration.
-                nullable: true
-                type: object
-              uploaderType:
-                description: UploaderType is the type of the uploader to handle the
-                  data transfer.
-                enum:
-                - kopia
-                - ""
-                type: string
-              volume:
-                description: Volume is the name of the volume within the Pod to be
-                  restored.
-                type: string
-            required:
-            - backupStorageLocation
-            - pod
-            - repoIdentifier
-            - snapshotID
-            - sourceNamespace
-            - volume
-            type: object
-          status:
-            description: PodVolumeRestoreStatus is the current status of a PodVolumeRestore.
-            properties:
-              acceptedTimestamp:
-                description: |-
-                  AcceptedTimestamp records the time the pod volume restore is to be prepared.
-                  The server's time is used for AcceptedTimestamp
-                format: date-time
-                nullable: true
-                type: string
-              completionTimestamp:
-                description: |-
-                  CompletionTimestamp records the time a restore was completed.
-                  Completion time is recorded even on failed restores.
-                  The server's time is used for CompletionTimestamps
-                format: date-time
-                nullable: true
-                type: string
-              message:
-                description: Message is a message about the pod volume restore's status.
-                type: string
-              node:
-                description: Node is name of the node where the pod volume restore
-                  is processed.
-                type: string
-              phase:
-                description: Phase is the current state of the PodVolumeRestore.
-                enum:
-                - New
-                - Accepted
-                - Prepared
-                - InProgress
-                - Canceling
-                - Canceled
-                - Completed
-                - Failed
-                type: string
-              progress:
-                description: |-
-                  Progress holds the total number of bytes of the snapshot and the current
-                  number of restored bytes. This can be used to display progress information
-                  about the restore operation.
-                properties:
-                  bytesDone:
-                    format: int64
-                    type: integer
-                  totalBytes:
-                    format: int64
-                    type: integer
-                type: object
-              startTimestamp:
-                description: |-
-                  StartTimestamp records the time a restore was started.
-                  The server's time is used for StartTimestamps
-                format: date-time
-                nullable: true
-                type: string
-            type: object
-        type: object
-    served: true
-    storage: true
-    subresources: {}
-```
-
-## Installation Changes
-No changes to installation, the backupPod/restorePod's configurations are either inherited from node-agent or retrieved from node-agent-configmap.  
-
-## Upgrade
-Upgrade is not impacted.  
-
-## CLI
-CLI is not changed.
-
-
-
-[1]: ../unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
-[2]: ../volume-snapshot-data-movement/volume-snapshot-data-movement.md
-[3]: ../vgdp-micro-service/vgdp-micro-service.md
-[4]: ../node-agent-concurrency.md
-[5]: https://github.com/vmware-tanzu/velero/issues/8955
-[6]: https://github.com/vmware-tanzu/velero/issues/8956
-[7]: https://github.com/vmware-tanzu/velero/issues/8289
-[8]: https://kubernetes.io/docs/tasks/configure-pod-container/create-hostprocess-pod/
-[9]: https://github.com/vmware-tanzu/velero/issues/7725
-[10]: https://github.com/vmware-tanzu/velero/issues/8423

design/Implemented/vgdp-micro-service/vgdp-micro-service.md

@@ -1,223 +0,0 @@
-# VGDP Micro Service For Volume Snapshot Data Movement
-
-## Glossary & Abbreviation
-
-**VGDP**: Velero Generic Data Path. The collective of modules that is introduced in [Unified Repository design][1]. Velero uses these modules to finish data transmission for various purposes. It includes uploaders and the backup repository.  
-**Volume Snapshot Data Movement**: The backup/restore method introduced in [Volume Snapshot Data Movement design][2]. It backs up snapshot data from the volatile and limited production environment into the durable, heterogeneous and scalable backup storage.  
-**VBDM**: Velero Built-in Data Mover as introduced in [Volume Snapshot Data Movement design][2], it is the built-in data mover shipped along with Velero.  
-**Exposer**: Exposer is introduced in [Volume Snapshot Data Movement design][2] and is used to expose the volume snapshots/target volumes for VGDP to access locally.  
-
-## Background
-As the architecture introduced in [Volume Snapshot Data Movement design][2], VGDP instances are running inside the node-agent pods, however, more and more use cases require to run the VGDP instances in dedicated pods, or in another word, make them as micro services, the benefits are as below:
-- This avoids VGDP to access volume data through host path, while host path access involves privilege escalations in some environments (e.g., must run under privileged mode), which makes challenge to users.    
-- This enable users to to control resource (i.e., cpu, memory) request/limit in a granular manner, e.g., control them per backup/restore of a volume
-- This increases the resilience, crash of one VGDP activity won't affect others
-- In the cases that the backup storage must be represented by a Kubernetes persistent volumes (i.e., nfs storage, [COSI][3]), this avoids to dynamically mount the persistent volumes to node-agent pods and cause node-agent pods to restart (this is not accepted since node-agent lose it current state after its pods restart)  
-- This prevents unnecessary full backup. Velero's fs uploaders support file level incremental backup by comparing the file name and metadata. However, at present the files are visited by host path, while pod and PVC's ID are part of the host path, so once the pod is recreated, the same file is regarded as a different file since the pod's ID has been changed. If the fs uploader is in a dedicated pod and files are visited by pod's volume path, files' full path are not changed after pod restarts, so incremental backups could continue.  
-
-## Goals
-- Create a solution to make VGDP instances as micro services
-- Modify the VBDM to offload the VGDP work from node-agent to the VGDP micro service
-- Create the mechanism for VBDM to control and monitor the VGDP micro services in various scenarios
-
-## Non-Goals
-- The current solution covers Volume Snapshot Data Movement backup/restore type only, even though VGDP is also used by pod volume backup. It is less possible to do this for pod volume backup, since it must run inside the source workload pods.  
-- The current solution covers VBDM only. 3rd data movers still follow the **Replacement** section of [Volume Snapshot Data Movement design][2]. That is, 3rd data movers handle the DUCR/DDCR on their own and they are free to make themselves micro service style or monolith service style.  
-
-
-## Overview
-The solution is based on [Volume Snapshot Data Movement design][2], the architecture is followed as is and existing components are not changed unless it is necessary.  
-Below lists the changed components, why and how:  
-**Exposer**: Exposer is to expose the snapshot/target volume as a path/device name/endpoint that are recognizable by VGDP. Varying from the type of snapshot/target volume, a pod may be created as part of the expose. Now, since we run the VGDP instance in a separate pod, a pod is created anyway, we assume exposer creates a pod all the time and make the appropriate exposing configurations to the pod so that VGDP instance could access the snapshot/target volume locally inside the pod. The pod is still called as backupPod or restorePod.  
-Then we need to change the command the backupPod/restorePod is running, the command launches VGDP-MS (VGDP Micro Service, see below) when the container starts up.  
-For CSI snapshot, the backupPod/restorePod is created as the result of expose, the only thing left is to change the backupPod/restorePod's image.  
-**VBDM**: VBDM contains the data mover controller, while the controller calls the Exposer and launches the VGDP instances.  Now, since the VGDP instance is launched by the backupPod/restorePod, the controller should not launch the VGDP instance again. However, the controller still needs to monitor and control the VGDP instance. Moreover, in order to avoid any contest situations, the controller is still the only place to update DUCRs and DDCRs.    
-
-Besides the changes to above existing components, we need to add below new components:  
-**VGDP Watcher**: We create a new module to help the data mover controller to watch activities of the VGDP instance in the backupPod/restorePod. VGDP Watcher is a part of VBDM.  
-**VGDP-MS**: VGDP Micro Service is the binary for the command backupPod/restorePod runs. It accepts the parameters and then launches the VGDP instance according to the request type, specifically, backup or restore. VGDP-MS also runs other modules to sync-up with the data mover controller. VGDP-MS is also a part of VBDM.  
-
-Below diagram shows how these components work together:  
-![vgdp-ms-1.png](vgdp-ms-1.png)  
-
-The [Node-agent concurrency][4] is still used to control the concurrency of VGDP micro services. When there are too many volumes in the backup/restore, which takes too much computing resources(CPU, memory, etc.) or Kubernetes resources(pods, PVCs, PVs, etc.), users could set the concurrency in each node so as to control the total number of concurrent VGDP micro services in the cluster.  
-
-## Detailed Design
-### Exposer
-At present, the exposer creates backupPod/restorePod and sets ```velero-helper pause``` as the command run by backupPod/restorePod.  
-Now, VGDP-MS command will be used, and the ```velero``` image will be running inside the backupPod/restorePod. The command is like below:  
-```velero data-mover backup --volume-path xxx --volume-mode xxx --data-upload xxx --resource-timeout xxx --log-format xxx --log-level xxx```  
-Or:  
-```velero data-mover restore --volume-path xxx --volume-mode xxx --data-download xxx --resource-timeout xxx --log-format xxx --log-level xxx```  
-
-The first one is for backup and the other one is for restore.  
-Below are the parameters of the commands:  
-**volume-path**: Deliver the full path inside the backupPod/restorePod for the volume to be backed up/restored.  
-**volume-mode**: Deliver the mode for the volume be backed up/restored, at present either ```Filesystem``` mode or ```Block``` mode.  
-**data-upload**: DUCR for this backup.  
-**data-download**: DDCR for this backup. 
-**resource-timeout**: resource-timeout is used to control the timeout for operations related to resources. It has the same meaning with the resource-timeout for node-agent.  
-**log-format** and **log-level**: This is to control the behavior of log generation inside VGDP-MS. 
-
-In order to have the same capability and permission with node-agent, below pod configurations are inherited from node-agent and set to backupPod/restorePod's spec:
-- Volumes: Some configMaps will be mapped as volumes to node-agent, so we add the same volumes of node-agent to the backupPod/restorePod
-- Environment Variables
-- Security Contexts  
-We may not actually need all the capabilities in the VGDP-MS as the node-agent. At present, we just duplicate all of them, if we find any problem in future, we can filter out the capabilities that are not required by VGDP-MS.  
-The backupPod/restorePod is not run in Privileged mode as it is not required since the volumes are visisted by pod path.  
-The root user is still required, especially by the restore (in order to restore the file system attributes, owners, etc.), so we will use root user for backupPod/restorePod.  
-We set backupPod/restorePod's ```RestartPolicy``` to ```RestartPolicyNever```, so that once VGDP-MS terminates in any reason, backupPod/restorePod won't restart and the DUCR/DDCR is marked as one of the terminal phases (Completed/Failed/Cancelled) accordingly.  
-
-
-### VGDP Watcher
-#### Dual mode event watch
-The primary task of VGDP Watcher is to watch the status change from backupPod/restorePod or the VGDP instance, so as to inform the data mover controller in below situations:
-- backupPod/restorePod starts
-- VGDP instance starts
-- Progress update
-- VGDP instance completes/fails/cancelled
-- backupPod/restorePod stops
-
-We use two mechanism to make the watch:  
-**Pod Phases**: VGDP Watcher watches the backupPod/restorePod's phases updated by Kubernetes. That is, VGDP Watcher creates an informer to watch the pod resource for the backupPod/restorePod and detect that the pod reaches to one of the terminated phases (i.e., PodSucceeded, PodFailed). We also check the availability & status of the backupPod/restorePod at the beginning of the watch so as to detect the starting of the backupPod/restorePod.  
-**Custom Kubernetes Events**: VGDP-MS generates Kubernetes events and associates them to the DUCR/DDCR at the time of VGDP instance starting/stopping and progress update, then VGDP Watcher creates another informer to watch the Event resource associated to the DUCR/DDCR.  
-
-Pod Phases watch covers the entire lifecycle of the backupPod/restorePod, but we don't know the status of the VGDP instance through it; and it can only deliver information by then end of the pod lifecycle.   
-Custom Event watch generates details of the VGDP instances and the events could be generated any time; but it cannot generate notifications before VGDP starts or in the case that VGDP crashes or shutdown abnormally.  
-
-Therefore, we adopt the both mechanisms to VGDP Watcher. In the end, there will be two sources generating the result of VGDP-MS:  
-- The termination message of backupPod/restorePod
-- The message along with the VGDP Instance Completes/Fails/Cancelled event  
-
-On the one hand, in some cases only the backupPod/restorePod's termination message is available, e.g., the backupPod/restorePod crashes or or backupPod/restorePod quits before VGDP instance is started. So we refer to the first mechanism to get the notifications.  
-On the other hand, if they are both available, we have the results from them for mutual verification.   
-
-Conclusively, under the help of VGDP Watcher, data mover controller starts VGDP-MS controllably and waits until VGDP-MS ends under any circumstances.   
-
-#### AsyncBR adapter
-VGDP Watcher needs to notify the data mover controller when one of the watched event happens, so that the controller could do the operations as if it receives the same callbacks from VGDP as the current behavior. In order not to break the existing code logics of data mover controllers, we make VGDP Watcher as an adapter of AsyncBR which is the interface implemented by VGDP and called by the data mover controller.  
-Since the parameters to call VGDP Watcher is different from the ones to call VGDP, we change the AsyncBR interface to hide some parameters from one another, the new interface is as below:  
-```
-type AsyncBR interface {
-	// Init initializes an asynchronous data path instance
-	Init(ctx context.Context, res *exposer.ExposeResult, param interface{}) error
-
-	// StartBackup starts an asynchronous data path instance for backup
-	StartBackup(dataMoverConfig map[string]string, param interface{}) error
-
-	// StartRestore starts an asynchronous data path instance for restore
-	StartRestore(snapshotID string, dataMoverConfig map[string]string) error
-
-	// Cancel cancels an asynchronous data path instance
-	Cancel()
-
-	// Close closes an asynchronous data path instance
-	Close(ctx context.Context)
-}
-```
-Some parameters are hidden into ```param```, but the functions and calling logics are not changed.  
-
-VGDP Watcher should be launched by the data mover controller before VGDP instance starts, otherwise, multiple corner problems may happen. E.g., VGDP-MS may run the VGDP instance immediately after the backupPod/restorePod is launched and completes it before the data mover controller starts VGDP Watcher, as a result, multiple informs are missed from VGDP Watcher.  
-Therefore, the controller launches VGDP Watcher first and then set the DUCR/DDCR to ```InProgress```; on the other hand, VGDP-MS waits DUCR/DDCR turns to ```InProgress``` before running the VGDP instance.  
-
-### VGDP-MS
-VGDP-MS is represented by ```velero data-mover``` subcommand and has its own subcommand ```backup``` and ```restore```.  
-Below diagram shows the VGDP-MS workflow:  
-![vgdp-ms-2.png](vgdp-ms-2.png)  
-
-**Start DUCR/DDCR Watcher**: VGDP-MS needs to watch the corresponding DUCR/DDCR so as to react on some events happening to the DUCR/DDCR. E.g., when the data movement is cancelled, a ```Cancel``` flag is set to the DUCR/DDCR, by watching the DUCR/DDCR, VGDP-MS is able to see it and cancel the VGDP instance.  
-**Wait DUCR/DDCR InProgress**: As mentioned above, VGDP-MS won't start the VGDP instance until DUCR/DDCR turns to ```InProgress```, by which time VGDP Watcher has been started.  
-**Record VGDP Starts**: This generates the VGDP Instance Starts event.  
-**VGDP Callbacks**: When VGDP comes to one of the terminal states (i.e., completed, failed, cancelled), the corresponding callback is called.  
-**Record VGDP Ends**: This generates the VGDP Instance Completes/Fails/Cancelled event, and also generates backupPod/restorePod termination message.    
-**Record VGDP Progress**: This periodically generates/updates the Progress event with totalBytes/bytesDone to indicate the progress of the data movement.  
-**Set VGDP Output**: This writes the termination message to the backupPod/restorePod's termination log (by default, it is written to ```/dev/termination-log```).  
-
-If VGDP completes, VGDP Instance Completes event and backupPod/restorePod termination shares the same message as below:  
-```
-type BackupResult struct {
-	SnapshotID    string              `json:"snapshotID"`
-	EmptySnapshot bool                `json:"emptySnapshot"`
-	Source        exposer.AccessPoint `json:"source,omitempty"`
-}
-```
-```
-type RestoreResult struct {
-	Target exposer.AccessPoint `json:"target,omitempty"`
-}
-```  
-``` 
-type AccessPoint struct {
-	ByPath  string                        `json:"byPath"`
-	VolMode uploader.PersistentVolumeMode `json:"volumeMode"`
-}
-``` 
-
-The existing VGDP result structures are actually being reused, we just add the json markers so that they can be marshalled.  
-
-As mentioned above, once VGDP-MS ends in any way, the backupPod/restorePod terminates and never restarts, so the end of VGDP-MS means the end of DU/DD.  
-
-For Progress update, the existing Progress structure is being reused:  
-``` 
-type Progress struct {
-	TotalBytes int64 `json:"totalBytes,omitempty"`
-	BytesDone  int64 `json:"doneBytes,omitempty"`
-}
-``` 
-
-### Log Collection
-During the running of VGDP instance, some logs are generated which are important for troubleshooting. This includes all the logs generated by the uploader and repository. Therefore, it is important to collect these logs.  
-On the other hand, the logs are now generated in the backupPod/restorePod, while the backupPod/restorePod is deleted immediately after the data movement completes. Therefore, by default, ```velero debug``` is not able to collect these logs.  
-
-As a solution, we use logrus's hook mechanism to redirect the backupPod/restorePod's logs into node-agent's log, so that ```velero debug``` could collect VGDP logs as is without any changes.  
-
-Below diagram shows how VGDP logs are redirected:  
-![vgdp-ms-3.png](vgdp-ms-3.png) 
-
-This log redirecting mechanism is thread safe since the hook acquires the write lock before writing the log buffer, so it guarantees that in the node-agent log there is no corruptions after redirecting the log, and the redirected logs and the original node-agent logs are not projected into each other.     
-
-### Resource Control
-The CPU/memory resource of backupPod/restorePod is configurable, which means users are allowed to configure resources per volume backup/restore.  
-By default, the [Best Effort policy][5] is used, and users are allowed to change it through the ConfigMap specified by `velero node-agent` CLI's parameter `--node-agent-configmap`. Specifically, we add below structures to the ConfigMap:  
-``` 
-type Configs struct {
-	// PodResources is the resource config for various types of pods launched by node-agent, i.e., data mover pods.
-	PodResources *PodResources `json:"podResources,omitempty"`
-}
-
-type PodResources struct {
-	CPURequest    string `json:"cpuRequest,omitempty"`
-	MemoryRequest string `json:"memoryRequest,omitempty"`
-	CPULimit      string `json:"cpuLimit,omitempty"`
-	MemoryLimit   string `json:"memoryLimit,omitempty"`
-}
-```
-The string values must mactch Kubernetes Quantity expressions; for each resource, the "request" value must not be larger than the "limit" value. Otherwise, if any one of the values fail, all the resource configurations will be ignored.  
-
-The configurations are loaded by node-agent at start time, so users can change the values in the configMap any time, but the changes won't effect until node-agent restarts.    
-
-
-## node-agent
-node-agent is still required. Even though VGDP is now not running inside node-agent, node-agent still hosts the data mover controller which reconciles DUCR/DDCR and operates DUCR/DDCR in other steps before the VGDP instance is started, i.e., Accept, Expose, etc.  
-Privileged mode and root user are not required for node-agent anymore by Volume Snapshot Data Movement, however, they are still required by PVB(PodVolumeBackup) and PVR(PodVolumeRestore). Therefore, we will keep the node-agent deamonset as is, for any users who don't use PVB/PVR and have concern about the privileged mode/root user, they need to manually modify the deamonset spec to remove the dependencies.  
-
-## CRD Changes
-There is no changes to any CRD.  
-
-## Installation Changes
-No changes to installation, the backupPod/restorePod's configurations are all inherited from node-agent.  
-
-## Upgrade
-Upgrade is not impacted.  
-
-## CLI
-CLI is not changed.
-
-
-
-[1]: ../unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
-[2]: ../volume-snapshot-data-movement/volume-snapshot-data-movement.md
-[3]: https://kubernetes.io/blog/2022/09/02/cosi-kubernetes-object-storage-management/
-[4]: ../node-agent-concurrency.md
-[5]: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/
-

design/Implemented/volume-group-snapshot.md

@@ -1,611 +0,0 @@
-# Add Support for VolumeGroupSnapshots
-
-This proposal outlines the design and implementation plan for incorporating VolumeGroupSnapshot support into Velero. The enhancement will allow Velero to perform consistent, atomic snapshots of groups of Volumes using the new Kubernetes [VolumeGroupSnapshot API](https://kubernetes.io/blog/2024/12/18/kubernetes-1-32-volume-group-snapshot-beta/). This capability is especially critical for stateful applications that rely on multiple volumes to ensure data consistency, such as databases and analytics workloads.
-
-## Glossary & Abbreviation
-
-Terminology used in this document:
-- VGS: VolumeGroupSnapshot
-- VS: VolumeSnapshot
-- VGSC: VolumeGroupSnapshotContent
-- VSC: VolumeSnapshotContent
-- VGSClass: VolumeGroupSnapshotClass
-- VSClass: VolumeSnapshotClass
-
-## Background
-
-Velero currently enables snapshot-based backups on an individual Volume basis through CSI drivers. However, modern stateful applications often require multiple volumes for data, logs, and backups. This distributed data architecture increases the risk of inconsistencies when volumes are captured individually. Kubernetes has introduced the VolumeGroupSnapshot(VGS) API [(KEP-3476)](https://github.com/kubernetes/enhancements/pull/1551), which allows for the atomic snapshotting of multiple volumes in a coordinated manner. By integrating this feature, Velero can offer enhanced disaster recovery for multi-volume applications, ensuring consistency across all related data.
-
-## Goals
-- Ensure that multiple related volumes are snapshotted simultaneously, preserving consistency for stateful applications via VolumeGroupSnapshots(VGS) API.
-- Integrate VolumeGroupSnapshot functionality into Velero’s existing backup and restore workflows.
-- Allow users to opt in to volume group snapshots via specifying the group label.
-
-## Non-Goals
-- The proposal does not require a complete overhaul of Velero’s CSI integration, it will extend the current mechanism to support group snapshots.
-- No any changes pertaining to execution of Restore Hooks
-
-## High-Level Design
-
-### Backup workflow:
-#### Accept the label to be used for VGS from the user:
-  - Accept the label from the user, we will do this in 3 ways:
-    - Firstly, we will have a hard-coded default label key like `velero.io/volume-group-snapshot` that the users can directly use on their PVCs.
-    - Secondly, we will let the users override this default VGS label via a velero server arg, `--volume-group-nsaphot-label-key`, if needed.
-    - And Finally we will have the option to override the default label via Backup API spec, `backup.spec.volumeGroupSnapshotLabelKey`
-    - In all the instances, the VGS label key will be present on the backup spec, this makes the label key accessible to plugins during the execution of backup operation.
-  - This label will enable velero to filter the PVC to be included in the VGS spec.
-  - Users will have to label the PVCs before invoking the backup operation.
-  - This label would act as a group identifier for the PVCs to be grouped under a specific VGS.
-  - It will be used to collect the PVCs to be used for a particular instance of VGS object.  
-
-**Note:** 
-  - Modifying or adding VGS label on PVCs during an active backup operation may lead to unexpected or undesirable backup results. To avoid inconsistencies, ensure PVC labels remain unchanged throughout the backup execution.
-  - Label Key Precedence: When determining which label key to use for grouping PVCs into a VolumeGroupSnapshot, Velero applies overrides in the following order (highest to lowest):
-    - Backup API spec (`backup.spec.volumeGroupSnapshotLabelKey`)
-    - Server flag (`--volume-group-snapshot-label-key`)
-    - Built-in default (`velero.io/volume-group-snapshot`)
-
-    Whichever key wins this precedence is then injected into the Backup spec so that all Velero plugins can uniformly discover and use it during the backup execution.
-#### Changes to the Existing PVC ItemBlockAction plugin:
-  - Currently the PVC IBA plugin is applied to PVCs and adds the RelatedItems for the particular PVC into the ItemBlock.
-  - At first it checks whether the PVC is bound and VolumeName is non-empty.
-  - Then it adds the related PV under the list of relatedItems.
-  - Following on, the plugin adds the pods mounting the PVC as relatedItems.
-  - Now we need to extend this PVC IBA plugin to add the PVCs to be grouped for a particular VGS object, so that they are processed together under an ItemBlock by Velero.
-      - First we will check if the PVC that is being processed by the plugin has the user specified VGS label.
-      - If it is present then we will execute a List call in the namespace with the label as a matching criteria and see if this results in any PVCs (other than the current one).
-      - If there are PVCs matching the criteria then we add the PVCs to the relatedItems list.
-      - This helps in building the ItemBlock we need for VGS processing, i.e. we have the relevant pods and PVCs in the ItemBlock.
-
-**Note:** The ItemBlock to VGS relationship will not always be 1:1. There might be scenarios when the ItemBlock might have multiple VGS instances associated with it.
-Lets go over some ItemBlock/VGS scenarios that we might encounter and visualize them for clarity:
-1. Pod Mounts: Pod1 mounts both PVC1 and PVC2.  
-   Grouping: PVC1 and PVC2 share the same group label (group: A)  
-   ItemBlock: The item block includes Pod1, PVC1, and PVC2.  
-   VolumeGroupSnapshot (VGS): Because PVC1 and PVC2 are grouped together by their label, they trigger the creation of a single VGS (labeled with group: A).  
-
-```mermaid
-flowchart TD
-   subgraph ItemBlock
-   P1[Pod1]
-   PVC1[PVC1 group: A]
-   PVC2[PVC2 group: A]
-   end
-
-   P1 -->|mounts| PVC1
-   P1 -->|mounts| PVC2
-
-   PVC1 --- PVC2
-
-   PVC1 -- "group: A" --> VGS[VGS group: A]
-   PVC2 -- "group: A" --> VGS
-
-```   
-2. Pod Mounts: Pod1 mounts each of the four PVCs.  
-   Grouping:  
-     Group A: PVC1 and PVC2 share the same grouping label (group: A).  
-     Group B: PVC3 and PVC4 share the grouping label (group: B)   
-   ItemBlock: All objects (Pod1, PVC1, PVC2, PVC3, and PVC4) are collected into a single item block.   
-   VolumeGroupSnapshots:  
-      PVC1 and PVC2 (group A) point to the same VGS (VGS (group: A)).      
-      PVC3 and PVC4 (group B) point to a different VGS (VGS (group: B)).    
-```mermaid
-flowchart TD
-    subgraph ItemBlock
-        P1[Pod1]
-        PVC1[PVC1 group: A]
-        PVC2[PVC2 group: A]
-        PVC3[PVC3 group: B]
-        PVC4[PVC4 group: B]
-    end
-
-    %% Pod mounts all PVCs
-    P1 -->|mounts| PVC1
-    P1 -->|mounts| PVC2
-    P1 -->|mounts| PVC3
-    P1 -->|mounts| PVC4
-
-    %% Group A relationships: PVC1 and PVC2
-    PVC1 --- PVC2
-    PVC1 -- "group: A" --> VGS_A[VGS-A group: A]
-    PVC2 -- "group: A" --> VGS_A
-
-    %% Group B relationships: PVC3 and PVC4
-    PVC3 --- PVC4
-    PVC3 -- "group: B" --> VGS_B[VGS-B group: B]
-    PVC4 -- "group: B" --> VGS_B
-```
-
-3. Pod Mounts: Pod1 mounts both PVC1 and PVC2, Pod2 mounts PVC1 and PVC3.  
-   Grouping:   
-     Group A: PVC1 and PVC2  
-     Group B: PVC3  
-   ItemBlock: All objects-Pod1, Pod2, PVC1, PVC2, and PVC3, are collected into a single item block.  
-   VolumeGroupSnapshots:  
-     PVC1 and PVC2 (group A) point to the same VGS (VGS (group: A)).   
-     PVC3 (group B) point to a different VGS (VGS (group: B)).  
-```mermaid
-flowchart TD
-    subgraph ItemBlock
-        P1[Pod1]
-        P2[Pod2]
-        PVC1[PVC1 group: A]
-        PVC2[PVC2 group: A]
-        PVC3[PVC3 group: B]
-    end
-
-    %% Pod mount relationships
-    P1 -->|mounts| PVC1
-    P1 -->|mounts| PVC2
-    P2 -->|mounts| PVC1
-    P2 -->|mounts| PVC3
-
-    %% Grouping for Group A: PVC1 and PVC2 are grouped into VGS_A
-    PVC1 --- PVC2
-    PVC1 -- "Group A" --> VGS_A[VGS Group A]
-    PVC2 -- "Group A" --> VGS_A
-
-    %% Grouping for Group B: PVC3 grouped into VGS_B
-    PVC3 -- "Group B" --> VGS_B[VGS Group B]
-    
-```
-
-#### Updates to CSI PVC plugin:
-The CSI PVC plugin now supports obtaining a VolumeSnapshot (VS) reference for a PVC in three ways, and then applies common branching for datamover and non‑datamover workflows:
-
-- Scenario 1: PVC has a VGS label and no VS (created via the VGS workflow) exists for its volume group:
-    - Determine VGSClass: The plugin will pick `VolumeGroupSnapshotClass` by following the same tier based precedence as it does for individual `VolumeSnapshotClasses`:
-      - Default by Label: Use the one VGSClass labeled
-      ```yaml
-      metadata:
-        labels:
-        velero.io/csi-volumegroupsnapshot-class: "true"
-
-      ```
-      whose `spec.driver` matches the CSI driver used by the PVCs.
-      - Backup‑level Override: If the Backup CR has an annotation
-      ```yaml
-      metadata:
-        annotations:
-        velero.io/csi-volumegroupsnapshot-class_<driver>: <className>
-      ```
-      (with <driver> equal to the PVCs’ CSI driver), use that class.
-      - PVC‑level Override: Finally, if the PVC itself carries an annotation
-      ```yaml
-      metadata:
-        annotations:
-        velero.io/csi-volume-group-snapshot-class: <className>
-      ```
-      and that class exists, use it.
-      At each step, if the plugin finds zero or multiple matching classes, VGS creation is skipped and backup fails.
-    - Create VGS: The plugin creates a new VolumeGroupSnapshot (VGS) for the PVC’s volume group. This action automatically triggers creation of the corresponding VGSC, VS, and VSC objects.
-    - Wait for VS Status: The plugin waits until each VS (one per PVC in the group) has its `volumeGroupSnapshotName` populated. This confirms that the snapshot controller has completed its work. `CSISnapshotTimeout` will be used here.
-    - Update VS Objects: Once the VS objects are provisioned, the plugin updates them by removing VGS owner references and VGS-related finalizers, and by adding backup metadata labels (including BackupName, BackupUUID, and PVC name). These labels are later used to detect an existing VS when processing another PVC of the same group.
-    - Patch and Cleanup: The plugin patches the deletionPolicy of the VGSC to "Retain" (ensuring that deletion of the VGSC does not remove the underlying VSC objects or storage snapshots) and then deletes the temporary VGS and VGSC objects.
-        
-- Scenario 2: PVC has a VGS label and a VS created via an earlier VGS workflow already exists:
-    - The plugin lists VS objects in the PVC’s namespace using backup metadata labels (BackupUID, BackupName, and PVCName).
-    - It verifies that at least one VS has a non‑empty `volumeGroupSnapshotName` in its status.
-    - If such a VS exists, the plugin skips creating a new VGS (or VS) and proceeds with the legacy workflow using the existing VS.
-    - If a VS is found but its status does not indicate it was created by the VGS workflow (i.e. its `volumeGroupSnapshotName` is empty), the backup for that PVC is failed, resulting in a partially failed backup.
-- Scenario 3: PVC does not have a VGS label:
-    - The legacy workflow is followed, and an individual VolumeSnapshot (VS) is created for the PVC.
-- Common Branching for Datamover and Non‑datamover Workflows:
-    - Once a VS reference (`vsRef`) is determined—whether through the VGS workflow (Scenario 1 or 2) or the legacy workflow (Scenario 3)—the plugin then applies the common branching:
-        - Non‑datamover Case: The VS reference is directly added as an additional backup item.
-            
-        - Datamover Case: The plugin waits until the VS’s associated VSC snapshot handle is ready (using the configured CSISnapshotTimeout), then creates a DataUpload for the VS–PVC pair. The resulting DataUpload is then added as an additional backup item.
-
-
-```mermaid
-flowchart TD
-    %% Section 1: Accept VGS Label from User
-    subgraph Accept_Label
-      A1[User sets VGS label key using default velero.io/volume-group-snapshot or via server arg or Backup API spec]
-      A2[User labels PVCs before backup]
-      A1 --> A2
-    end
-
-    %% Section 2: PVC ItemBlockAction Plugin Extension
-    subgraph PVC_ItemBlockAction
-      B1[Check PVC is bound and has VolumeName]
-      B2[Add related PV to relatedItems]
-      B3[Add pods mounting PVC to relatedItems]
-      B4[Check if PVC has user-specified VGS label]
-      B5[List PVCs in namespace matching label criteria]
-      B6[Add matching PVCs to relatedItems]
-      B1 --> B2 --> B3 --> B4
-      B4 -- Yes --> B5
-      B5 --> B6
-    end
-
-    %% Section 3: CSI PVC Plugin Updates
-    subgraph CSI_PVC_Plugin
-       C1[For each PVC, check for VGS label]
-       C1 -- Has VGS label --> C2[Determine scenario]
-       C1 -- No VGS label --> C16[Scenario 3: Legacy workflow - create individual VS]
-
-       %% Scenario 1: No existing VS via VGS exists
-       subgraph Scenario1[Scenario 1: No existing VS via VGS]
-         S1[List grouped PVCs using VGS label]
-         S2[Determine CSI driver for grouped PVCs]
-         S3[If single CSI driver then select matching VGSClass; else fail backup]
-         S4[Create new VGS triggering VGSC, VS, and VSC creation]
-         S5[Wait for VS objects to have nonempty volumeGroupSnapshotName]
-         S6[Update VS objects; remove VGS owner refs and finalizers; add backup metadata labels]
-         S7[Patch VGSC deletionPolicy to Retain]
-         S8[Delete transient VGS and VGSC]
-         S1 --> S2 --> S3 --> S4 --> S5 --> S6 --> S7 --> S8
-		 
-       end
-
-       %% Scenario 2: Existing VS via VGS exists
-       subgraph Scenario2[Scenario 2: Existing VS via VGS exists]
-         S9[List VS objects using backup metadata - BackupUID, BackupName, PVCName]
-         S10[Check if any VS has nonempty volumeGroupSnapshotName]
-         S9 --> S10
-         S10 -- Yes --> S11[Use existing VS]
-         S10 -- No --> S12[Fail backup for PVC]
-       end
-
-       C2 -- Scenario1 applies --> S1
-       C2 -- Scenario2 applies --> S9
-
-       %% Common Branch: After obtaining a VS reference
-       subgraph Common_Branch[Common Branch]
-         CB1[Obtain VS reference as vsRef]
-         CB2[If non-datamover, add vsRef as additional backup item]
-         CB3[If datamover, wait for VSC handle and create DataUpload; add DataUpload as additional backup item]
-         CB1 --> CB2
-         CB1 --> CB3
-       end
-       
-       %% Connect Scenario outcomes and legacy branch to the common branch
-       S8 --> CB1
-       S11 --> CB1
-       C16 --> CB1
-    end
-
-    %% Overall Flow Connections
-    A2 --> B1
-    B6 --> C1
-
-```
-
-
-Restore workflow:
-
-- No changes required for the restore workflow.
-
-## Detailed Design
-
-Backup workflow:
-- Accept the label to be used for VGS from the user as a server argument:
-    - Set a default VGS label key to be used:
-    ```go
-    // default VolumeGroupSnapshot Label
-	defaultVGSLabelKey = "velero.io/volume-group-snapshot"
-    
-    ```
-    - Add this as a server flag and pass it to backup reconciler, so that we can use it during the backup request execution.
-    ```go
-    flags.StringVar(&c.DefaultVGSLabelKey, "volume-group-snapshot-label-key", c.DefaultVGSLabelKey, "Label key for grouping PVCs into VolumeGroupSnapshot")
-    ```
-
-    - Update the Backup CRD to accept the VGS Label Key as a spec value:
-    ```go
-    // VolumeGroupSnapshotLabelKey specifies the label key to be used for grouping the PVCs under
-	// an instance of VolumeGroupSnapshot, if left unspecified velero.io/volume-group-snapshot is used
-	// +optional
-	VolumeGroupSnapshotLabelKey string `json:"volumeGroupSnapshotLabelKey,omitempty"`
-    ```
-    - Modify the [`prepareBackupRequest` function](https://github.com/openshift/velero/blob/8c8a6cccd78b78bd797e40189b0b9bee46a97f9e/pkg/controller/backup_controller.go#L327) to set the default label key as a backup spec if the user does not specify any value:
-    ```go
-    if len(request.Spec.VolumeGroupSnapshotLabelKey) == 0 {
-		// set the default key value
-		request.Spec.VolumeGroupSnapshotLabelKey = b.defaultVGSLabelKey
-	}
-    ```
-
-- Changes to the Existing [PVC ItemBlockAction plugin](https://github.com/vmware-tanzu/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/itemblock/actions/pvc_action.go#L64) (Update the GetRelatedItems function):
-```go
-// Retrieve the VGS label key from the Backup spec.
-	vgsLabelKey := backup.Spec.VolumeGroupSnapshotLabelKey
-	if vgsLabelKey != "" {
-		// Check if the PVC has the specified VGS label.
-		if groupID, ok := pvc.Labels[vgsLabelKey]; ok {
-			// List all PVCs in the namespace with the same label key and value (i.e. same group).
-			pvcList := new(corev1api.PersistentVolumeClaimList)
-			if err := a.crClient.List(context.Background(), pvcList, crclient.InNamespace(pvc.Namespace), crclient.MatchingLabels{vgsLabelKey: groupID}); err != nil {
-				return nil, errors.Wrap(err, "failed to list PVCs for VGS grouping")
-			}
-			// Add each matching PVC (except the current one) to the relatedItems.
-			for _, groupPVC := range pvcList.Items {
-				if groupPVC.Name == pvc.Name {
-					continue
-				}
-				a.log.Infof("Adding grouped PVC %s to relatedItems for PVC %s", groupPVC.Name, pvc.Name)
-				relatedItems = append(relatedItems, velero.ResourceIdentifier{
-					GroupResource: kuberesource.PersistentVolumeClaims,
-					Namespace:     groupPVC.Namespace,
-					Name:          groupPVC.Name,
-				})
-			}
-		}
-	} else {
-		a.log.Info("No VolumeGroupSnapshotLabelKey provided in backup spec; skipping PVC grouping")
-	}
-```
-
-- Updates to [CSI PVC plugin](https://github.com/vmware-tanzu/velero/blob/512199723ff95d5016b32e91e3bf06b65f57d608/pkg/backup/actions/csi/pvc_action.go#L200) (Update the Execute method):
-```go
-func (p *pvcBackupItemAction) Execute(
-    item runtime.Unstructured,
-    backup *velerov1api.Backup,
-) (
-    runtime.Unstructured,
-    []velero.ResourceIdentifier,
-    string,
-    []velero.ResourceIdentifier,
-    error,
-) {
-    p.log.Info("Starting PVCBackupItemAction")
-
-    // Validate backup policy and PVC/PV
-    if valid := p.validateBackup(*backup); !valid {
-        return item, nil, "", nil, nil
-    }
-
-    var pvc corev1api.PersistentVolumeClaim
-    if err := runtime.DefaultUnstructuredConverter.FromUnstructured(item.UnstructuredContent(), &pvc); err != nil {
-        return nil, nil, "", nil, errors.WithStack(err)
-    }
-    if valid, item, err := p.validatePVCandPV(pvc, item); !valid {
-        if err != nil {
-            return nil, nil, "", nil, err
-        }
-        return item, nil, "", nil, nil
-    }
-
-    shouldSnapshot, err := volumehelper.ShouldPerformSnapshotWithBackup(
-        item,
-        kuberesource.PersistentVolumeClaims,
-        *backup,
-        p.crClient,
-        p.log,
-    )
-    if err != nil {
-        return nil, nil, "", nil, err
-    }
-    if !shouldSnapshot {
-        p.log.Debugf("CSI plugin skip snapshot for PVC %s according to VolumeHelper setting", pvc.Namespace+"/"+pvc.Name)
-        return nil, nil, "", nil, nil
-    }
-
-    var additionalItems []velero.ResourceIdentifier
-    var operationID string
-    var itemToUpdate []velero.ResourceIdentifier
-
-    // vsRef will be our common reference to the VolumeSnapshot (VS)
-    var vsRef *corev1api.ObjectReference
-
-    // Retrieve the VGS label key from the backup spec.
-    vgsLabelKey := backup.Spec.VolumeGroupSnapshotLabelKey
-
-    // Check if the PVC has the user-specified VGS label.
-    if group, ok := pvc.Labels[vgsLabelKey]; ok && group != "" {
-        p.log.Infof("PVC %s has VGS label with group %s", pvc.Name, group)
-        // --- VGS branch ---
-        // 1. Check if a VS created via a VGS workflow exists for this PVC.
-        existingVS, err := p.findExistingVSForBackup(backup.UID, backup.Name, pvc.Name, pvc.Namespace)
-        if err != nil {
-            return nil, nil, "", nil, err
-        }
-        if existingVS != nil && existingVS.Status.VolumeGroupSnapshotName != "" {
-            p.log.Infof("Existing VS %s found for PVC %s in group %s; skipping VGS creation", existingVS.Name, pvc.Name, group)
-            vsRef = &corev1api.ObjectReference{
-                Namespace: existingVS.Namespace,
-                Name:      existingVS.Name,
-            }
-        } else {
-            // 2. No existing VS via VGS; execute VGS creation workflow.
-            groupedPVCs, err := p.listGroupedPVCs(backup, pvc.Namespace, vgsLabelKey, group)
-            if err != nil {
-                return nil, nil, "", nil, err
-            }
-            pvcNames := extractPVCNames(groupedPVCs)
-            // Determine the CSI driver used by the grouped PVCs.
-            driver, err := p.determineCSIDriver(groupedPVCs)
-            if err != nil {
-                return nil, nil, "", nil, errors.Wrap(err, "failed to determine CSI driver for grouped PVCs")
-            }
-            if driver == "" {
-                return nil, nil, "", nil, errors.New("multiple CSI drivers found for grouped PVCs; failing backup")
-            }
-            // Retrieve the appropriate VGSClass for the CSI driver.
-            vgsClass := p.getVGSClassForDriver(driver)
-            p.log.Infof("Determined CSI driver %s with VGSClass %s for PVC group %s", driver, vgsClass, group)
-
-            newVGS, err := p.createVolumeGroupSnapshot(backup, pvc, pvcNames, vgsLabelKey, group, vgsClass)
-            if err != nil {
-                return nil, nil, "", nil, err
-            }
-            p.log.Infof("Created new VGS %s for PVC group %s", newVGS.Name, group)
-            
-            // Wait for the VS objects created via VGS to have volumeGroupSnapshotName in status.
-            if err := p.waitForVGSAssociatedVS(newVGS, pvc.Namespace, backup.Spec.CSISnapshotTimeout.Duration); err != nil {
-                return nil, nil, "", nil, err
-            }
-            // Update the VS objects: remove VGS owner references and finalizers; add backup metadata labels.
-            if err := p.updateVGSCreatedVS(newVGS, backup); err != nil {
-                return nil, nil, "", nil, err
-            }
-            // Patch the VGSC deletionPolicy to Retain.
-            if err := p.patchVGSCDeletionPolicy(newVGS, pvc.Namespace); err != nil {
-                return nil, nil, "", nil, err
-            }
-            // Delete the VGS and VGSC
-            if err := p.deleteVGSAndVGSC(newVGS, pvc.Namespace); err != nil {
-                return nil, nil, "", nil, err
-            }
-            // Fetch the VS that was created for this PVC via VGS.
-            vs, err := p.getVSForPVC(backup, pvc, vgsLabelKey, group)
-            if err != nil {
-                return nil, nil, "", nil, err
-            }
-            vsRef = &corev1api.ObjectReference{
-                Namespace: vs.Namespace,
-                Name:      vs.Name,
-            }
-        }
-    } else {
-        // Legacy workflow: PVC does not have a VGS label; create an individual VS.
-        vs, err := p.createVolumeSnapshot(pvc, backup)
-        if err != nil {
-            return nil, nil, "", nil, err
-        }
-        vsRef = &corev1api.ObjectReference{
-            Namespace: vs.Namespace,
-            Name:      vs.Name,
-        }
-    }
-
-    // --- Common Branch ---
-    // Now we have vsRef populated from one of the above cases.
-    // Branch further based on backup.Spec.SnapshotMoveData.
-    if boolptr.IsSetToTrue(backup.Spec.SnapshotMoveData) {
-        // Datamover case:
-        operationID = label.GetValidName(
-            string(velerov1api.AsyncOperationIDPrefixDataUpload) + string(backup.UID) + "." + string(pvc.UID),
-        )
-        dataUploadLog := p.log.WithFields(logrus.Fields{
-            "Source PVC":     fmt.Sprintf("%s/%s", pvc.Namespace, pvc.Name),
-            "VolumeSnapshot": fmt.Sprintf("%s/%s", vsRef.Namespace, vsRef.Name),
-            "Operation ID":   operationID,
-            "Backup":         backup.Name,
-        })
-        // Retrieve the current VS using vsRef
-        vs := &snapshotv1api.VolumeSnapshot{}
-        if err := p.crClient.Get(context.TODO(), crclient.ObjectKey{Namespace: vsRef.Namespace, Name: vsRef.Name}, vs); err != nil {
-            return nil, nil, "", nil, errors.Wrapf(err, "failed to get VolumeSnapshot %s", vsRef.Name)
-        }
-        // Wait until the VS-associated VSC snapshot handle is ready.
-        _, err := csi.WaitUntilVSCHandleIsReady(
-            vs,
-            p.crClient,
-            p.log,
-            true,
-            backup.Spec.CSISnapshotTimeout.Duration,
-        )
-        if err != nil {
-            dataUploadLog.Errorf("Failed to wait for VolumeSnapshot to become ReadyToUse: %s", err.Error())
-            csi.CleanupVolumeSnapshot(vs, p.crClient, p.log)
-            return nil, nil, "", nil, errors.WithStack(err)
-        }
-        dataUploadLog.Info("Starting data upload of backup")
-        dataUpload, err := createDataUpload(
-            context.Background(),
-            backup,
-            p.crClient,
-            vs,
-            &pvc,
-            operationID,
-        )
-        if err != nil {
-            dataUploadLog.WithError(err).Error("Failed to submit DataUpload")
-            if deleteErr := p.crClient.Delete(context.TODO(), vs); deleteErr != nil && !apierrors.IsNotFound(deleteErr) {
-                dataUploadLog.WithError(deleteErr).Error("Failed to delete VolumeSnapshot")
-            }
-            return item, nil, "", nil, nil
-        }
-        dataUploadLog.Info("DataUpload submitted successfully")
-        itemToUpdate = []velero.ResourceIdentifier{
-            {
-                GroupResource: schema.GroupResource{
-                    Group:    "velero.io",
-                    Resource: "datauploads",
-                },
-                Namespace: dataUpload.Namespace,
-                Name:      dataUpload.Name,
-            },
-        }
-        annotations[velerov1api.DataUploadNameAnnotation] = dataUpload.Namespace + "/" + dataUpload.Name
-        // For the datamover case, add the dataUpload as an additional item directly.
-        vsRef = &corev1api.ObjectReference{
-            Namespace: dataUpload.Namespace,
-            Name:      dataUpload.Name,
-        }
-        additionalItems = append(additionalItems, velero.ResourceIdentifier{
-            GroupResource: schema.GroupResource{
-                Group:    "velero.io",
-                Resource: "datauploads",
-            },
-            Namespace: dataUpload.Namespace,
-            Name:      dataUpload.Name,
-        })
-    } else {
-        // Non-datamover case:
-        // Use vsRef for snapshot purposes.
-        additionalItems = append(additionalItems, convertVSToResourceIdentifiersFromRef(vsRef)...)
-        p.log.Infof("VolumeSnapshot additional item added for VS %s", vsRef.Name)
-    }
-
-    // Update PVC metadata with common labels and annotations.
-    labels := map[string]string{
-        velerov1api.VolumeSnapshotLabel: vsRef.Name,
-        velerov1api.BackupNameLabel:     backup.Name,
-    }
-    annotations := map[string]string{
-        velerov1api.VolumeSnapshotLabel:                 vsRef.Name,
-        velerov1api.MustIncludeAdditionalItemAnnotation: "true",
-    }
-    kubeutil.AddAnnotations(&pvc.ObjectMeta, annotations)
-    kubeutil.AddLabels(&pvc.ObjectMeta, labels)
-
-    p.log.Infof("Returning from PVCBackupItemAction with %d additionalItems to backup", len(additionalItems))
-    for _, ai := range additionalItems {
-        p.log.Debugf("%s: %s", ai.GroupResource.String(), ai.Name)
-    }
-
-    pvcMap, err := runtime.DefaultUnstructuredConverter.ToUnstructured(&pvc)
-    if err != nil {
-        return nil, nil, "", nil, errors.WithStack(err)
-    }
-
-    return &unstructured.Unstructured{Object: pvcMap},
-        additionalItems, operationID, itemToUpdate, nil
-}
-
-
-```
-
-## Implementation
-
-This design proposal is targeted for velero 1.16.
-
-The implementation of this proposed design is targeted for velero 1.17.
-
-**Note:**
-- VGS support isn't a requirement on restore. The design does not have any VGS related elements/considerations in the restore workflow.
-
-## Requirements and Assumptions
-- Kubernetes Version:
-  - Minimum: v1.32.0 or later, since the VolumeGroupSnapshot API goes beta in 1.32.
-  - Assumption: CRDs for `VolumeGroupSnapshot`, `VolumeGroupSnapshotClass`, and `VolumeGroupSnapshotContent` are already installed.
-
-- VolumeGroupSnapshot API Availability:
-  - If the VGS API group (`groupsnapshot.storage.k8s.io/v1beta1`) is not present, Velero backup will fail.
-
-- CSI Driver Compatibility
-  - Only CSI drivers that implement the VolumeGroupSnapshot admission and controller support this feature.
-  - Upon VGS creation, we assume the driver will atomically snapshot all matching PVCs; if it does not, the plugin may time out.
-
-## Performance Considerations
-- Use VGS if you have many similar volumes that must be snapped together and you want to minimize API/server load.
-- Use individual VS if you have only a few volumes, or want one‐volume failures to be isolated.
-
-## Testing Strategy
-
-- Unit tests: We will add targeted unit tests to cover all new code paths—including existing-VS detection, VGS creation, legacy VS fallback, and error scenarios.
-- E2E tests: For E2E we would need, a Kind cluster with a CSI driver that supports group snapshots, deploy an application with multiple PVCs, execute a Velero backup and restore, and verify that VGS is created, all underlying VS objects reach ReadyToUse, and every PVC is restored successfully.

design/Implemented/volume-policy-label-selector-criteria.md

@@ -1,202 +0,0 @@
-# Add Label Selector as a criteria for Volume Policy
-
-## Abstract
-Velero’s volume policies currently support several criteria (such as capacity, storage class, and volume source type) to select volumes for backup. This update extends the design by allowing users to specify required labels on the associated PersistentVolumeClaim (PVC) via a simple key/value map. At runtime, Velero looks up the PVC (when a PV has a ClaimRef), extracts its labels, and compares them with the user-specified map. If all key/value pairs match, the volume qualifies for backup.
-
-## Background 
-PersistentVolumes (PVs) in Kubernetes are typically bound to PersistentVolumeClaims (PVCs) that include labels (for example, indicating environment, application, or region). Basing backup policies on these PVC labels enables more precise control over which volumes are processed.
-
-## Goals
-- Allow users to specify a simple key/value mapping in the volume policy YAML so that only volumes whose associated PVCs contain those labels are selected.
-- Support policies that target volumes based on criteria such as environment=production or region=us-west.
-
-## Non-Goals
-- No changes will be made to the actions (skip, snapshot, fs-backup) of the volume policy engine. This update focuses solely on how volumes are selected.
-- The design does not support other label selector operations (e.g., NotIn, Exists, DoesNotExist) and only allows for exact key/value matching.
-
-## Use-cases/scenarios
-1. Environment-Specific Backup:
-- A user wishes to back up only those volumes whose associated PVCs have labels such as `environment=production` and `app=database`.
-- The volume policy specifies a pvcLabels map with those key/value pairs; only volumes whose PVCs match are processed.
-```yaml
-volumePolicies:
-  - conditions:
-      pvcLabels:
-        environment: production
-        app: database
-    action:
-      type: snapshot
-```
-2. Region-Specific Backup:
-- A user operating in multiple regions wants to back up only volumes in the `us-west` region.
-- The policy includes `pvcLabels: { region: us-west }`, so only PVs bound to PVCs with that label are selected.
-```yaml
-volumePolicies:
-  - conditions:
-      pvcLabels:
-        region: us-west
-    action:
-      type: snapshot
-```
-3. Automated Label-Based Backups:
-- An external system automatically labels new PVCs (for example, `backup: true`).
-- A volume policy with `pvcLabels: { backup: true }` ensures that any new volume whose PVC contains that label is included in backup operations.
-```yaml
-version: v1
-volumePolicies:
-  - conditions:
-      pvcLabels:
-        backup: true
-    action:
-      type: snapshot
-```
-## High-Level Design
-
-1. Extend Volume Policy Schema:
-- The YAML schema for volume conditions is extended to include an optional field pvcLabels of type `map[string]string`.
-2. Implement New Condition Type:
-- A new condition, `pvcLabelsCondition`, is created. It implements the `volumeCondition` interface and simply compares the user-specified key/value pairs with the actual PVC labels (populated at runtime).
-3. Update Structured Volume:
-- The internal representation of a volume (`structuredVolume`) is extended with a new field `pvcLabels map[string]string` to store the labels from the associated PVC.
-- A new helper function (or an updated parsing function) is used to perform a PVC lookup when a PV has a ClaimRef, populating the pvcLabels field.
-4. Integrate with Policy Engine:
-- The policy builder is updated to create and add a `pvcLabelsCondition` if the policy YAML contains a `pvcLabels` entry.
-- The matching entry point uses the updated `structuredVolume` (populated with PVC labels) to evaluate all conditions, including the new PVC labels condition.
-## Detailed Design
-
-1. Update Volume Conditions Schema: Define the conditions struct with a simple map for PVC labels:
-```go
-// volumeConditions defines the current format of conditions we parse.
-type volumeConditions struct {
-    Capacity     string            `yaml:"capacity,omitempty"`
-    StorageClass []string          `yaml:"storageClass,omitempty"`
-    NFS          *nFSVolumeSource  `yaml:"nfs,omitempty"`
-    CSI          *csiVolumeSource  `yaml:"csi,omitempty"`
-    VolumeTypes  []SupportedVolume `yaml:"volumeTypes,omitempty"`
-    // New field: pvcLabels for simple exact-match filtering.
-    PVCLabels map[string]string `yaml:"pvcLabels,omitempty"`
-}
-```
-2. New Condition: `pvcLabelsCondition`: Implement a condition that compares expected labels with those on the PVC:
-```go
-// pvcLabelsCondition defines a condition that matches if the PVC's labels contain all the specified key/value pairs.
-type pvcLabelsCondition struct {
-    labels map[string]string
-}
-
-func (c *pvcLabelsCondition) match(v *structuredVolume) bool {
-    if len(c.labels) == 0 {
-        return true // No label condition specified; always match.
-    }
-    if v.pvcLabels == nil {
-        return false // No PVC labels found.
-    }
-    for key, expectedVal := range c.labels {
-        if actualVal, exists := v.pvcLabels[key]; !exists || actualVal != expectedVal {
-            return false
-        }
-    }
-    return true
-}
-
-func (c *pvcLabelsCondition) validate() error {
-    // No extra validation needed for a simple map.
-    return nil
-}
-```
-3. Update `structuredVolume`: Extend the internal volume representation with a field for PVC labels:
-```go
-// structuredVolume represents a volume with parsed fields.
-type structuredVolume struct {
-    capacity     resource.Quantity
-    storageClass string
-    // New field: pvcLabels stores labels from the associated PVC.
-    pvcLabels    map[string]string
-    nfs          *nFSVolumeSource
-    csi          *csiVolumeSource
-    volumeType   SupportedVolume
-}
-```
-4. Update PVC Lookup – `parsePVWithPVC`: Modify the PV parsing function to perform a PVC lookup:
-```go
-func (s *structuredVolume) parsePVWithPVC(pv *corev1.PersistentVolume, client crclient.Client) error {
-    s.capacity = *pv.Spec.Capacity.Storage()
-    s.storageClass = pv.Spec.StorageClassName
-
-    if pv.Spec.NFS != nil {
-        s.nfs = &nFSVolumeSource{
-            Server: pv.Spec.NFS.Server,
-            Path:   pv.Spec.NFS.Path,
-        }
-    }
-    if pv.Spec.CSI != nil {
-        s.csi = &csiVolumeSource{
-            Driver:           pv.Spec.CSI.Driver,
-            VolumeAttributes: pv.Spec.CSI.VolumeAttributes,
-        }
-    }
-    s.volumeType = getVolumeTypeFromPV(pv)
-
-    // If the PV is bound to a PVC, look it up and store its labels.
-    if pv.Spec.ClaimRef != nil {
-        pvc := &corev1.PersistentVolumeClaim{}
-        err := client.Get(context.Background(), crclient.ObjectKey{
-            Namespace: pv.Spec.ClaimRef.Namespace,
-            Name:      pv.Spec.ClaimRef.Name,
-        }, pvc)
-        if err != nil {
-            return errors.Wrap(err, "failed to get PVC for PV")
-        }
-        s.pvcLabels = pvc.Labels
-    }
-    return nil
-}
-```
-5. Update the Policy Builder: Add the new condition to the policy if pvcLabels is provided:
-```go
-func (p *Policies) BuildPolicy(resPolicies *ResourcePolicies) error {
-    for _, vp := range resPolicies.VolumePolicies {
-        con, err := unmarshalVolConditions(vp.Conditions)
-        if err != nil {
-            return errors.WithStack(err)
-        }
-        volCap, err := parseCapacity(con.Capacity)
-        if err != nil {
-            return errors.WithStack(err)
-        }
-        var volP volPolicy
-        volP.action = vp.Action
-        volP.conditions = append(volP.conditions, &capacityCondition{capacity: *volCap})
-        volP.conditions = append(volP.conditions, &storageClassCondition{storageClass: con.StorageClass})
-        volP.conditions = append(volP.conditions, &nfsCondition{nfs: con.NFS})
-        volP.conditions = append(volP.conditions, &csiCondition{csi: con.CSI})
-        volP.conditions = append(volP.conditions, &volumeTypeCondition{volumeTypes: con.VolumeTypes})
-        // If a pvcLabels map is provided, add the pvcLabelsCondition.
-        if con.PVCLabels != nil && len(con.PVCLabels) > 0 {
-            volP.conditions = append(volP.conditions, &pvcLabelsCondition{labels: con.PVCLabels})
-        }
-        p.volumePolicies = append(p.volumePolicies, volP)
-    }
-    p.version = resPolicies.Version
-    return nil
-}
-```
-6. Update the Matching Entry Point: Use the updated PV parsing that performs a PVC lookup:
-```go
-func (p *Policies) GetMatchAction(res interface{}, client crclient.Client) (*Action, error) {
-    volume := &structuredVolume{}
-    switch obj := res.(type) {
-    case *corev1.PersistentVolume:
-        if err := volume.parsePVWithPVC(obj, client); err != nil {
-            return nil, errors.Wrap(err, "failed to parse PV with PVC lookup")
-        }
-    case *corev1.Volume:
-        volume.parsePodVolume(obj)
-    default:
-        return nil, errors.New("failed to convert object")
-    }
-    return p.match(volume), nil
-}
-```
-
-Note: The matching loop (p.match(volume)) iterates over all conditions (including our new pvcLabelsCondition) and returns the corresponding action if all conditions match.

design/concurrent-backup-processing.md

@@ -1,257 +0,0 @@
-# Concurrent Backup Processing
-
-This enhancement will enable Velero to process multiple backups at the same time. This is largely a usability enhancement rather than a performance enhancement, since the overall backup throughput may not be significantly improved over the current implementation, since we are already processing individual backup items in parallel. It is a significant usability improvement, though, as with the current design, a user who submits a small backup may have to wait significantly longer than expected if the backup is submitted immediately after a large backup.
-
-## Background
-
-With the current implementation, only one backup may be `InProgress` at a time. A second backup created will not start processing until the first backup moves on to `WaitingForPluginOperations` or `Finalizing`. This is a usability concern, especially in clusters when multiple users are initiating backups. With this enhancement, we intend to allow multiple backups to be processed concurrently. This will allow backups to start processing immediately, even if a large backup was just submitted by another user. This enhancement will build on top of the prior parallel item processing feature by creating a dedicatede ItemBlock worker pool for each running backup. The pool will be created at the beginning of the backup reconcile, and the input channel will be passed to the Kubernetes backupper just like it is in the current release.
-
-The primary challenge is to make sure that the same workload in multiple backups is not backed up concurrently. If that were to happen, we would risk data corruption, especially around the processing of pod hooks and volume backup. For this first release we will take a conservative, high-level approach to overlap detection. Two backups will not run concurrently if there is any overlap in included namespaces. For example, if a backup that includes `ns1` and `ns2` is running, then a second backup for `ns2` and `ns3` will not be started. If a backup which does not filter namespaces is running (either a whole cluster backup or a non-namespace-limited backup with a label selector) then no other backups will be started, since a backup across all namespaces overlaps with any other backup. Calculating item-level overlap for queued backups is problematic since we don't know which items are included in a backup until backup processing has begun. A future release may add ItemBlock overlap detection, where at the item block worker level, the same item will not be processed by two different workers at the same time. This works together with workload conflict detection to further detect conflicts in a more granular level for shared resources between backups. Eventually, with a more complete understanding of individual workloads (either via ItemBlocks or some higher level model), the namespace level overlap detection may be relaxed in future versions.
-
-## Goals
-- Process multiple backups concurrently
-- Detect namespace overlap to avoid conflicts
-- For queued backups (not yet runnable due to concurrency limits or overlap), indicate the queue position in status
-
-## Non Goals
-- Handling NFS PVs when more than one PV point to the same underlying NFS share
-- Handling VGDP cancellation for failed backups on restart
-- Mounting a PVC for scenarios in which /tmp is too small for the number of concurrent backups
-- Providing a mechanism to identify high priority backups which get preferential treatment in terms of ItemBlock worker availability
-- Item-level overlap detection (future feature)
-- Providing the ability to disable namespace-level overlap detection once Item-level overlap detection is in place (although this may be supported in a future version).
-
-## High-Level Design
-
-### Backup CRD changes
-
-Two new backup phases will be added: `Queued` and `ReadyToStart`. In the Backup workflow, new backups will be moved to the Queued phase when they are added to the backup queue. When a backup is removed from the queue because it is now able to run, it will be moved to the `ReadyToStart` phase, which will allow the backup controller to start processing it.
-
-In addition, a new Status field, `QueuePosition`, will be added to track the backup's current position in the queue.
-
-### New Controller: `backupQueueReconciler`
-
-A new reconciler will be added, `backupQueueReconciler` which will use the current `backupReconciler` logic for reconciling `New` backups but instead of running the backup, it will move the Backup to the `Queued` phase and set `QueuePosition`.
-
-In addition, this reconciler will periodically reconcile all queued backups (on some configurable time interval) and if there is a runnable backup, remove it from the queue, update `QueuePosition` for any queued backups behind it, and update its phase to `ReadyToStart`.
-
-Queued backups will be reconciled in order based on `QueuePosition`, so the first runnable backup found will be processed. A backup is runnable if both of the following conditions are true:
-1) The total number of backups either `InProgress` or `ReadyToStart` is less than the configured number of concurrent backups.
-2) The backup has no overlap with any backups currently `InProgress` or `ReadyToStart` or with any `Queued` backups with a higher (i.e. closer to 1) queue position than this backup.
-
-### Updates to Backup controller
-
-The current `backupReconciler` will change its reconciling rules. Instead of watching and reconciling New backups, it will reconcile `ReadyToStart` backups. In addition, it will be configured to run in parallel by setting `MaxConcurrentReconciles` based on the `concurrent-backups` server arg.
-
-The startup (and shutdown) of the ItemBlock worker pool will be moved from reconciler startup to the backup reconcile, which will give each running backup its own dedicated worker pool. The per-backup worker pool will will use the existing `--item-block-worker-count` installer/server arg. This means that the maximum number of ItemBlock workers for the entire Velero pod will be the ItemBlock worker count multiplied by concurrentBackups. For example, if concurrentBackups is 5, and itemBlockWorkerCount is 6, then there will be, at most, 30 worker threads active, 5 dedicated to each InProgress backup, but this maximum will only be achieved when the maximum number of backups are InProgress. This also means that each InProgress backup will have a dedicated ItemBlock input channel with the same fixed buffer size.
-
-## Detailed Design
-
-### New Install/Server configuration args
-
-A new install/server arg, `concurrent-backups` will be added. This will be an int-valued field specifying the number of backups which may be processed concurrently (with phase `InProgress`). If not specified, the default value of 1 will be used.
-
-### Consideration of backup overlap and concurrent backup processing
-
-The primary consideration for running additional backups concurrently is the configured `concurrent-backups` parameter. If the total number of `InProgress` and `ReadyToStart` backups is equal to `concurrent-backups` then any `Queued` backups will remain in the queue.
-
-The second consideration is backup overlap. In order to prevent interaction between running backups (particularly around volume backup and pod hooks), we cannot allow two overlapping backups to run at the same time. For now, we will define overlap broadly -- requiring that two concurrent backups don't include any of the same namespaces. A backup for `ns1` can run concurrently with a backup for `ns2`, but a backup for `[ns1,ns2]` cannot run concurrently with a backup for `ns1`. One consequence of this approach is that a backup which includes all namespaces (even if further filtered by resource or label) cannot run concurrently with *any other backup*.
-
-When determining which queued backup to run next, velero will look for the next queued backup which has no overlap with any InProgress backup or any Queued backup ahead of it. The reason we need to consider queued as well as running backups for overlap detection is as follows.
-
-Consider the following scenario. These are the current not-completed backups (ordered from oldest to newest)
-1. backup1, includedNamespaces: [ns1, ns2], phase: InProgress
-2. backup2, includedNamespaces: [ns2, ns3, ns5], phase: Queued, QueuePosition: 1
-3. backup3, includedNamespaces: [ns4, ns3], phase: Queued, QueuePosition: 2
-4. backup4, includedNamespaces: [ns5, ns6], phase: Queued, QueuePosition: 2
-5. backup5, includedNamespaces: [ns8, ns9], phase: Queued, QueuePosition: 3
-
-Assuming `concurrent-backups` is 2, on the next reconcile, Velero will be able to start a second backup if there is one with no overlap. `backup2` cannot run, since `ns2` overlaps between it and the running `backup1`. If we only considered running overlap (and not queued overlap), then `backup3` could run now. It conflicts with the queued `backup2` on `ns3` but it does not conflict with the running backup. However, if it runs now, then when `backup1` completes, then `backup2` still can't run (since it now overlaps with running `backup3`on `ns3`), so `backup4` starts instead. Now when `backup3` completes, `backup2` still can't run (since it now conflicts with `backup4` on `ns5`). This means that even though it was the second backup created, it's the fourth to run -- providing worse time to completion than without parallel backups. If a queued backup has a large number of namespaces (a full-cluster backup for example), it would never run as long as new single-namespace backups keep being added to the queue.
-
-To resolve this problem we consider both running backups as well as backups ahead in the queue when resolving overlap conflicts. In the above scenario, `backup2` can't run yet since it overlaps with the running backup on `ns2`. In addition, `backup3` and `backup4` also can't run yet since they overlap with queued `backup2`. Therefore, `backup5` will run now. Once `backup1` completes, `backup2` will be free to run.
-
-### Backup CRD changes
-
-New Backup phases:
-```go
-const (
-	// BackupPhaseQueued means the backup has been added to the
-	// queue by the BackupQueueReconciler.
-	BackupPhaseQueued BackupPhase = "Queued"
-
-	// BackupPhaseReadyToStart means the backup has been removed from the
-	// queue by the BackupQueueReconciler and is ready to start.
-	BackupPhaseReadyToStart BackupPhase = "ReadyToStart"
-)
-```
-
-In addition, a new Status field, `queuePosition`, will be added to track the backup's current position in the queue.
-```go
-	// QueuePosition is the position held by the backup in the queue.
-	// QueuePosition=1 means this backup is the next to be considered.
-	// Only relevant when Phase is "Queued"
-	// +optional
-	QueuePosition int `json:"queuePosition,omitempty"`
-```
-
-### New Controller: `backupQueueReconciler`
-
-A new reconciler will be added, `backupQueueReconciler` which will reconcile backups under these conditions:
-1) Watching Create/Update for backups in `New` (or empty) phase
-2) Watching for Backup phase transition from `InProgress` to something else to reconcile all `Queued` backups
-2) Watching for Backup phase transition from `New` (or empty) to `Queued` to reconcile all `Queued` backups
-2) Periodic reconcile of `Queued` backups to handle backups queued at server startup as well as to make sure we never have a situation where backups are queued indefinitely because of a race condition or was otherwise missed in the reconcile on prior backup completion.
-
-The reconciler will be set up as follows -- note that New backups are reconciled on Create/Update, while Queued backups are reconciled when an InProgress backup moves on to another state or when a new backup moves to the Queued state. We also reconcile Queued backups periodically to handle the case of a Velero pod restart with Queued backups, as well as to handle possible edge cases where a queued backup doesn't get moved out of the queue at the point of backup completion or an error occurs during a prior Queued backup reconcile.
-
-```go
-func (c *backupOperationsReconciler) SetupWithManager(mgr ctrl.Manager) error {
-        // only consider Queued backups, order by QueuePosition
-	gp := kube.NewGenericEventPredicate(func(object client.Object) bool {
-		backup := object.(*velerov1api.Backup)
-		return (backup.Status.Phase == velerov1api.BackupPhaseQueued)
-	})
-	s := kube.NewPeriodicalEnqueueSource(c.logger.WithField("controller", constant.ControllerBackupOperations), mgr.GetClient(), &velerov1api.BackupList{}, c.frequency, kube.PeriodicalEnqueueSourceOption{
-		Predicates: []predicate.Predicate{gp},
-		OrderFunc: queuePositionOrderFunc,
-	})
-
-	return ctrl.NewControllerManagedBy(mgr).
-		For(&velerov1api.Backup{}, builder.WithPredicates(predicate.Funcs{
-				UpdateFunc: func(ue event.UpdateEvent) bool {
-					backup := ue.ObjectNew.(*velerov1api.Backup)
-					return backup.Status.Phase == "" || backup.status.Phase == velerov1api.BackupPhaseNew
-				},
-				CreateFunc: func(event.CreateEvent) bool {
-					return backup.Status.Phase == "" || backup.status.Phase == velerov1api.BackupPhaseNew
-				},
-				DeleteFunc: func(de event.DeleteEvent) bool {
-					return false
-				},
-				GenericFunc: func(ge event.GenericEvent) bool {
-					return false
-				},
-		})).
-		Watch(
-			&source.Kind{Type: &velerov1api.Backup{}},
-			&handler.EnqueueRequestsFromMapFunc{
-				ToRequests: handler.ToRequestsFunc(func(a handler.MapObject) []reconcile.Request {
-					backupList := velerov1api.BackupList{}
-					if err := p.List(ctx, backupList); err != nil {
-						p.logger.WithError(err).Error("error listing backups")
-						return
-					}
-					requests = []reconcile.request{}
-					// filter backup list by Phase=queued
-					// sort backup list by queuePosition
-					return requests
-				}),
-		},
-		builder.WithPredicates(predicate.Funcs{
-				UpdateFunc: func(ue event.UpdateEvent) bool {
-					oldBackup := ue.ObjectOld.(*velerov1api.Backup)
-					newBackup := ue.ObjectNew.(*velerov1api.Backup)
-					return oldBackup.Status.Phase == velerov1api.BackupPhaseInProgress &&
-						newBackup.Status.Phase != velerov1api.BackupPhaseInProgress ||
-						oldBackup.Status.Phase != velerov1api.BackupPhaseQueued &&
-						newBackup.Status.Phase == velerov1api.BackupPhaseQueued
-				},
-				CreateFunc: func(event.CreateEvent) bool {
-					return false
-				},
-				DeleteFunc: func(de event.DeleteEvent) bool {
-					return false
-				},
-				GenericFunc: func(ge event.GenericEvent) bool {
-					return false
-				},
-		}).
-		WatchesRawSource(s).
-		Named(constant.ControllerBackupQueue).
-		Complete(c)
-}
-```
-
-New backups will be queued: Phase will be set to `Queued`, and `QueuePosition` will be set to a int value incremented from the highest current `QueuePosition` value among Queued backups.
-
-Queued backups will be removed from the queue if runnable:
-1) If the total number of backups either InProgress or ReadyToStart is greater than or equal to the concurrency limit, then exit without removing from the queue.
-2) If the current backup overlaps with any InProgress, ReadyToStart, or Queued backup with `QueuePosition < currentBackup.QueuePosition` then exit without removing from the queue.
-3) If we get here, the backup is runnable. To resolve a potential race condition where an InProgress backup completes between reconciling the backup with QueuePosition `n-1` and reconciling the current backup with QueuePosition `n`, we also check to see whether there are any runnable backups in the queue ahead of this one. The only time this will happen is if a backup completes immediately before reconcile starts which either frees up a concurrency slot or removes a namespace conflict. In this case, we don't want to run the current backup since the one ahead of this one in the queue (which was recently passed over before the InProgress backup completed) must run first. In this case, exit without removing from the queue.
-4) If we get here, remove the backup from the queue by setting Phase to `ReadyToStart` and `QueuePosition` to zero. Decrement the `QueuePosition` of any other Queued backups with a `QueuePosition` higher than the current backup's queue position prior to dequeuing. At this point, the backup reconciler will start the backup.
-
-`if len(inProgressBackups)+len(pendingStartBackups) >= concurrentBackups`
-
-```
-	switch original.Status.Phase {
-	case "", velerov1api.BackupPhaseNew:
-		// enqueue backup -- set phase=Queued, set queuePosition=maxCurrentQueuePosition+1
-	}
-	// We should only ever get these events when added in order by the periodical enqueue source
-	// so as long as the current backup has not conflicts ahead of it or running, we should be good to
-	// dequeue
-	case "", velerov1api.BackupPhaseQueued:
-		// list backups, filter on Queued, ReadyToStart, and InProgress
-		// if number of InProgress backups + number of ReadyToStart backups >= concurrency limit, exit
-		// generate list of all namespaces included in InProgress, ReadyToStart, and Queued backups with
-		// queuePosition < backup.Status.QueuePosition
-		// if overlap found, exit
-		// check backups ahead of this one in the queue for runnability. If any are runnable, exit
-		// dequeue backup: set Phase to ReadyToStart, QueuePosition to 0, and decrement QueuePosition
-		// for all QueuedBackups behind this one in the queue
-	}
-
-```
-
-The queue controller will run as a single reconciler thread, so we will not need to deal with concurrency issues when moving backups from New to Queued or from Queued to ReadyToStart, and all of the updates to QueuePosition will be from a single thread.
-
-### Updates to Backup controller
-
-The Reconcile logic will be updated to respond to ReadyToStart backups instead of New backups:
-
-```
-@@ -234,8 +234,8 @@ func (b *backupReconciler) Reconcile(ctx context.Context, req ctrl.Request) (ctr
-        // InProgress, we still need this check so we can return nil to indicate we've finished processing
-        // this key (even though it was a no-op).
-        switch original.Status.Phase {
--       case "", velerov1api.BackupPhaseNew:
--               // only process new backups
-+       case velerov1api.BackupPhaseReadyToStart:
-+               // only process ReadyToStart backups
-        default:
-                b.logger.WithFields(logrus.Fields{
-                        "backup": kubeutil.NamespaceAndName(original),
-```
-
-In addition, it will be configured to run in parallel by setting `MaxConcurrentReconciles` based on the `concurrent-backups` server arg.
-
-```
-@@ -149,6 +149,9 @@ func NewBackupReconciler(
- func (b *backupReconciler) SetupWithManager(mgr ctrl.Manager) error {
-        return ctrl.NewControllerManagedBy(mgr).
-                For(&velerov1api.Backup{}).
-+                WithOptions(controller.Options{
-+                       MaxConcurrentReconciles: concurrentBackups,
-+               }).
-                Named(constant.ControllerBackup).
-                Complete(b)
- }
-```
-
-The controller-runtime core reconciler logic already prevents the same resource from being reconciled by two different reconciler threads, so we don't need to worry about concurrency issues at the controller level.
-
-The workerPool reference will be moved from the backupReconciler to the backupRequest, since this will now be backup-specific, and the initialization code for the worker pool will be moved from the reconciler init into the backup reconcile. This worker pool will be shut down upon exiting the Reconcile method.
-
-### Resilience to restart of velero pod
-
-The new backup phases (`Queued` and `ReadyToStart`) will be resilient to velero pod restarts. If the velero pod crashes or is restarted, only backups in the `InProgress` phase will be failed, so there is no change to current behavior. Queued backups will retain their queue position on restart, and ReadyToStart backups will move to InProgress when reconciled.
-
-### Observability
-
-#### Logging
-
-When a backup is dequeued, an info log message will also include the wait time, calculated as `now - creationTimestamp`. When a backup is passed over due to overlap, an info log message will indicate which namespaces were in conflict.
-
-#### Velero CLI
-
-The `velero backup describe` output will include the current queue position for queued backups.

design/volume-snapshot-data-movement/volume-snapshot-data-movement.md

@@ -37,7 +37,7 @@ Moreover, we would like to create a general workflow to variations during the da
 
 ## Architecture of Volume Snapshot Data Movement
 
-### Workflows  
+## Workflows  
 
 Here are the diagrams that illustrate components and workflows for backup and restore respectively.  
 For backup, we intend to create an extensive architecture for various snapshot types, snapshot accesses and various data accesses. For example, the snapshot specific operations are isolated in Data Mover Plugin and Exposer. In this way, we only need to change the two modules for variations. Likely, the data access details are isolated into uploaders, so different uploaders could be plugged into the workflow seamlessly.  
@@ -52,7 +52,7 @@ Below is the backup workflow:
 Below is the restore workflow:  
 ![restore-workflow.png](restore-workflow.png)  
 
-### Components
+## Components
 Below are the generic components in the data movement workflow:  
 
 **Velero**: Velero controls the backup/restore workflow, it calls BIA/RIA V2 to backup/restore an object that involves data movement, specifically, a PVC or a PV.  
@@ -69,13 +69,13 @@ DMs take the responsibility to handle DUCR/DDCRs, Velero provides a built-in DM
 **Velero Generic Data Path (VGDP)**: VGDP is the collective of modules that is introduced in [Unified Repository design][1]. Velero uses these modules to finish data transmission for various purposes. In includes uploaders and the backup repository.  
 **Uploader**: Uploader is the module in VGDP that reads data from the source and writes to backup repository for backup; while read data from backup repository and write to the restore target for restore. At present, only file system uploader is supported. In future, the block level uploader will be added. For file system and basic block uploader, only Kopia uploader will be used, Restic will not be integrated with VBDM.   
 
-### Replacement
+## Replacement
 3rd parties could integrate their own data movement into Velero by replacing VBDM with their own DMs. The DMs should process DUCR/DDCRs appropriately and finally put them into one of the terminal states as shown in the DataUpload CRD and DataDownload CRD sections.  
 Theoretically, replacing the DMP is also allowed. In this way, the entire workflow is customized, so this is out of the scope of this design.  
 
-## Detailed Design
+# Detailed Design
 
-### Backup Sequence
+## Backup Sequence
 Below are the data movement actions and sequences during backup:  
 ![backup-sequence.png](backup-sequence.png) 
 
@@ -150,7 +150,7 @@ We keep VGDP reused for VBDM, so everything inside VGDP are kept as is. For deta
 When VGDP completes backup, it returns an ID that represent the root object saved into the backup repository for this backup, through the root object, we will be able to enumerate the entire backup data.  
 This Repo Snapshot ID will be saved along with the DUCR.  
 
-### DataUpload CRD
+## DataUpload CRD
 Below are the essential fields of DataUpload CRD. The CRD covers below information:
 - The information to manipulate the specified snapshot
 - The information to manipulate the specified data mover
@@ -351,7 +351,7 @@ spec:
 
 ```
 
-### Restore Sequence
+## Restore Sequence
 
 Below are the data movement actions sequences during restore:  
 ![restore-sequence.png](restore-sequence.png) 
@@ -387,7 +387,7 @@ This also means that Velero should not restore the PV if a data movement restore
 
 For restore, VBDM doesn’t need to persist anything.  
 
-### DataDownload CRD
+## DataDownload CRD
 Below are the essential fields of DataDownload CRD. The CRD covers below information:
 - The information to manipulate the target volume
 - The information to manipulate the specified data mover
@@ -977,6 +977,6 @@ Restore command is kept as is.
 
 
 
-[1]: ../unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
-[2]: ../general-progress-monitoring.md
+[1]: ../Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
+[2]: ../Implemented/general-progress-monitoring.md
 [3]: ../node-agent-concurrency.md

examples/minio/00-minio-deployment.yaml

@@ -107,7 +107,7 @@ spec:
         command:
         - /bin/sh
         - -c
-        - "mc --config-dir=/config alias set velero http://minio:9000 minio minio123 && mc --config-dir=/config mb -p velero/velero"
+        - "mc --config-dir=/config config host add velero http://minio:9000 minio minio123 && mc --config-dir=/config mb -p velero/velero"
         volumeMounts:
         - name: config
           mountPath: "/config"

go.mod

@@ -1,14 +1,14 @@
 module github.com/vmware-tanzu/velero
 
-go 1.24.0
+go 1.22.6
 
 require (
-	cloud.google.com/go/storage v1.55.0
-	github.com/Azure/azure-sdk-for-go/sdk/azcore v1.18.1
-	github.com/Azure/azure-sdk-for-go/sdk/azidentity v1.10.1
+	cloud.google.com/go/storage v1.40.0
+	github.com/Azure/azure-sdk-for-go/sdk/azcore v1.11.1
+	github.com/Azure/azure-sdk-for-go/sdk/azidentity v1.6.0
 	github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute/armcompute/v5 v5.6.0
-	github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/storage/armstorage v1.8.0
-	github.com/Azure/azure-sdk-for-go/sdk/storage/azblob v1.6.1
+	github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/storage/armstorage v1.5.0
+	github.com/Azure/azure-sdk-for-go/sdk/storage/azblob v1.3.2
 	github.com/aws/aws-sdk-go-v2 v1.24.1
 	github.com/aws/aws-sdk-go-v2/config v1.26.3
 	github.com/aws/aws-sdk-go-v2/credentials v1.16.14
@@ -17,66 +17,59 @@ require (
 	github.com/aws/aws-sdk-go-v2/service/s3 v1.48.0
 	github.com/aws/aws-sdk-go-v2/service/sts v1.26.7
 	github.com/bombsimon/logrusr/v3 v3.0.0
-	github.com/evanphx/json-patch/v5 v5.9.11
-	github.com/fatih/color v1.18.0
+	github.com/evanphx/json-patch/v5 v5.8.0
+	github.com/fatih/color v1.16.0
 	github.com/gobwas/glob v0.2.3
-	github.com/google/go-cmp v0.7.0
+	github.com/golang/protobuf v1.5.4
+	github.com/google/go-cmp v0.6.0
 	github.com/google/uuid v1.6.0
 	github.com/hashicorp/go-hclog v0.14.1
 	github.com/hashicorp/go-plugin v1.6.0
 	github.com/joho/godotenv v1.3.0
 	github.com/kopia/kopia v0.16.0
-	github.com/kubernetes-csi/external-snapshotter/client/v8 v8.2.0
-	github.com/onsi/ginkgo/v2 v2.22.0
-	github.com/onsi/gomega v1.36.1
-	github.com/petar/GoLLRB v0.0.0-20210522233825-ae3b015fd3e9
+	github.com/kubernetes-csi/external-snapshotter/client/v7 v7.0.0
+	github.com/onsi/ginkgo v1.16.5
+	github.com/onsi/gomega v1.30.0
 	github.com/pkg/errors v0.9.1
-	github.com/prometheus/client_golang v1.22.0
-	github.com/prometheus/client_model v0.6.2
-	github.com/robfig/cron/v3 v3.0.1
+	github.com/prometheus/client_golang v1.19.0
+	github.com/robfig/cron v1.1.0
 	github.com/sirupsen/logrus v1.9.3
-	github.com/spf13/afero v1.10.0
-	github.com/spf13/cobra v1.8.1
+	github.com/spf13/afero v1.6.0
+	github.com/spf13/cobra v1.7.0
 	github.com/spf13/pflag v1.0.5
-	github.com/stretchr/testify v1.10.0
+	github.com/stretchr/testify v1.9.0
 	github.com/vmware-tanzu/crash-diagnostics v0.3.7
 	go.uber.org/zap v1.27.0
-	golang.org/x/mod v0.26.0
-	golang.org/x/net v0.42.0
-	golang.org/x/oauth2 v0.30.0
-	golang.org/x/text v0.27.0
-	google.golang.org/api v0.241.0
-	google.golang.org/grpc v1.73.0
-	google.golang.org/protobuf v1.36.6
+	golang.org/x/exp v0.0.0-20230522175609-2e198f4a06a1
+	golang.org/x/mod v0.17.0
+	golang.org/x/net v0.26.0
+	golang.org/x/oauth2 v0.19.0
+	golang.org/x/text v0.16.0
+	google.golang.org/api v0.172.0
+	google.golang.org/grpc v1.63.2
+	google.golang.org/protobuf v1.33.0
 	gopkg.in/yaml.v3 v3.0.1
-	k8s.io/api v0.33.3
-	k8s.io/apiextensions-apiserver v0.33.3
-	k8s.io/apimachinery v0.33.3
-	k8s.io/cli-runtime v0.33.3
-	k8s.io/client-go v0.33.3
-	k8s.io/klog/v2 v2.130.1
-	k8s.io/kube-aggregator v0.33.3
-	k8s.io/metrics v0.33.3
-	k8s.io/utils v0.0.0-20241104100929-3ea5e8cea738
-	sigs.k8s.io/controller-runtime v0.21.0
-	sigs.k8s.io/json v0.0.0-20241010143419-9aa6b5e7a4b3
+	k8s.io/api v0.29.0
+	k8s.io/apiextensions-apiserver v0.29.0
+	k8s.io/apimachinery v0.29.0
+	k8s.io/cli-runtime v0.24.0
+	k8s.io/client-go v0.29.0
+	k8s.io/klog/v2 v2.110.1
+	k8s.io/kube-aggregator v0.19.12
+	k8s.io/metrics v0.25.6
+	k8s.io/utils v0.0.0-20230726121419-3b25d923346b
+	sigs.k8s.io/controller-runtime v0.17.2
+	sigs.k8s.io/json v0.0.0-20221116044647-bc3834ca7abd
 	sigs.k8s.io/yaml v1.4.0
 )
 
 require (
-	cel.dev/expr v0.23.0 // indirect
-	cloud.google.com/go v0.121.1 // indirect
-	cloud.google.com/go/auth v0.16.2 // indirect
-	cloud.google.com/go/auth/oauth2adapt v0.2.8 // indirect
-	cloud.google.com/go/compute/metadata v0.7.0 // indirect
-	cloud.google.com/go/iam v1.5.2 // indirect
-	cloud.google.com/go/monitoring v1.24.2 // indirect
-	github.com/Azure/azure-sdk-for-go/sdk/internal v1.11.1 // indirect
-	github.com/Azure/go-ansiterm v0.0.0-20230124172434-306776ec8161 // indirect
-	github.com/AzureAD/microsoft-authentication-library-for-go v1.5.0 // indirect
-	github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp v1.27.0 // indirect
-	github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric v0.51.0 // indirect
-	github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping v0.51.0 // indirect
+	cloud.google.com/go v0.112.1 // indirect
+	cloud.google.com/go/compute v1.24.0 // indirect
+	cloud.google.com/go/compute/metadata v0.2.3 // indirect
+	cloud.google.com/go/iam v1.1.7 // indirect
+	github.com/Azure/azure-sdk-for-go/sdk/internal v1.8.0 // indirect
+	github.com/AzureAD/microsoft-authentication-library-for-go v1.2.2 // indirect
 	github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.5.4 // indirect
 	github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.14.11 // indirect
 	github.com/aws/aws-sdk-go-v2/internal/configsources v1.2.10 // indirect
@@ -91,61 +84,53 @@ require (
 	github.com/aws/aws-sdk-go-v2/service/ssooidc v1.21.6 // indirect
 	github.com/aws/smithy-go v1.19.0 // indirect
 	github.com/beorn7/perks v1.0.1 // indirect
-	github.com/blang/semver/v4 v4.0.0 // indirect
-	github.com/cespare/xxhash/v2 v2.3.0 // indirect
+	github.com/cespare/xxhash/v2 v2.2.0 // indirect
 	github.com/chmduquesne/rollinghash v4.0.0+incompatible // indirect
-	github.com/cncf/xds/go v0.0.0-20250326154945-ae57f3c0d45f // indirect
-	github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc // indirect
+	github.com/davecgh/go-spew v1.1.1 // indirect
 	github.com/dustin/go-humanize v1.0.1 // indirect
-	github.com/edsrzf/mmap-go v1.2.0 // indirect
+	github.com/edsrzf/mmap-go v1.1.0 // indirect
 	github.com/emicklei/go-restful/v3 v3.11.0 // indirect
-	github.com/envoyproxy/go-control-plane/envoy v1.32.4 // indirect
-	github.com/envoyproxy/protoc-gen-validate v1.2.1 // indirect
+	github.com/evanphx/json-patch v5.6.0+incompatible // indirect
 	github.com/felixge/httpsnoop v1.0.4 // indirect
 	github.com/fsnotify/fsnotify v1.7.0 // indirect
-	github.com/fxamacker/cbor/v2 v2.7.0 // indirect
-	github.com/go-ini/ini v1.67.0 // indirect
-	github.com/go-jose/go-jose/v4 v4.0.5 // indirect
-	github.com/go-logr/logr v1.4.3 // indirect
+	github.com/go-logr/logr v1.4.1 // indirect
 	github.com/go-logr/stdr v1.2.2 // indirect
+	github.com/go-logr/zapr v1.3.0 // indirect
 	github.com/go-ole/go-ole v1.3.0 // indirect
-	github.com/go-openapi/jsonpointer v0.21.0 // indirect
+	github.com/go-openapi/jsonpointer v0.19.6 // indirect
 	github.com/go-openapi/jsonreference v0.20.2 // indirect
-	github.com/go-openapi/swag v0.23.0 // indirect
-	github.com/go-task/slim-sprig/v3 v3.0.0 // indirect
-	github.com/goccy/go-json v0.10.5 // indirect
-	github.com/gofrs/flock v0.12.1 // indirect
+	github.com/go-openapi/swag v0.22.3 // indirect
+	github.com/gofrs/flock v0.8.1 // indirect
 	github.com/gogo/protobuf v1.3.2 // indirect
-	github.com/golang-jwt/jwt/v5 v5.2.2 // indirect
-	github.com/golang/protobuf v1.5.4 // indirect
-	github.com/google/btree v1.1.3 // indirect
-	github.com/google/gnostic-models v0.6.9 // indirect
-	github.com/google/pprof v0.0.0-20241029153458-d1b30febd7db // indirect
-	github.com/google/s2a-go v0.1.9 // indirect
-	github.com/googleapis/enterprise-certificate-proxy v0.3.6 // indirect
-	github.com/googleapis/gax-go/v2 v2.14.2 // indirect
-	github.com/gorilla/websocket v1.5.4-0.20250319132907-e064f32e3674 // indirect
+	github.com/golang-jwt/jwt/v5 v5.2.1 // indirect
+	github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da // indirect
+	github.com/google/gnostic-models v0.6.8 // indirect
+	github.com/google/gofuzz v1.2.0 // indirect
+	github.com/google/s2a-go v0.1.7 // indirect
+	github.com/googleapis/enterprise-certificate-proxy v0.3.2 // indirect
+	github.com/googleapis/gax-go/v2 v2.12.3 // indirect
+	github.com/gorilla/websocket v1.5.0 // indirect
 	github.com/hashicorp/cronexpr v1.1.2 // indirect
 	github.com/hashicorp/yamux v0.1.1 // indirect
+	github.com/imdario/mergo v0.3.13 // indirect
 	github.com/inconshreveable/mousetrap v1.1.0 // indirect
 	github.com/jmespath/go-jmespath v0.4.0 // indirect
 	github.com/josharian/intern v1.0.0 // indirect
 	github.com/json-iterator/go v1.1.12 // indirect
-	github.com/klauspost/compress v1.18.0 // indirect
-	github.com/klauspost/cpuid/v2 v2.2.10 // indirect
+	github.com/klauspost/compress v1.17.8 // indirect
+	github.com/klauspost/cpuid/v2 v2.2.6 // indirect
 	github.com/klauspost/pgzip v1.2.6 // indirect
-	github.com/klauspost/reedsolomon v1.12.4 // indirect
+	github.com/klauspost/reedsolomon v1.12.1 // indirect
 	github.com/kylelemons/godebug v1.1.0 // indirect
 	github.com/liggitt/tabwriter v0.0.0-20181228230101-89fcab3d43de // indirect
 	github.com/mailru/easyjson v0.7.7 // indirect
-	github.com/mattn/go-colorable v0.1.14 // indirect
+	github.com/mattn/go-colorable v0.1.13 // indirect
 	github.com/mattn/go-isatty v0.0.20 // indirect
-	github.com/minio/crc64nvme v1.0.1 // indirect
 	github.com/minio/md5-simd v1.1.2 // indirect
-	github.com/minio/minio-go/v7 v7.0.94 // indirect
+	github.com/minio/minio-go/v7 v7.0.69 // indirect
+	github.com/minio/sha256-simd v1.0.1 // indirect
 	github.com/mitchellh/go-testing-interface v1.0.0 // indirect
-	github.com/moby/spdystream v0.5.0 // indirect
-	github.com/moby/term v0.5.0 // indirect
+	github.com/moby/spdystream v0.2.0 // indirect
 	github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd // indirect
 	github.com/modern-go/reflect2 v1.0.2 // indirect
 	github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 // indirect
@@ -154,48 +139,40 @@ require (
 	github.com/natefinch/atomic v1.0.1 // indirect
 	github.com/nxadm/tail v1.4.8 // indirect
 	github.com/oklog/run v1.0.0 // indirect
-	github.com/philhofer/fwd v1.1.3-0.20240916144458-20a13a1f6b7c // indirect
 	github.com/pierrec/lz4 v2.6.1+incompatible // indirect
 	github.com/pkg/browser v0.0.0-20240102092130-5ac0b6a4141c // indirect
-	github.com/planetscale/vtprotobuf v0.6.1-0.20240319094008-0393e58bdf10 // indirect
-	github.com/pmezard/go-difflib v1.0.1-0.20181226105442-5d4384ee4fb2 // indirect
-	github.com/prometheus/common v0.65.0 // indirect
-	github.com/prometheus/procfs v0.15.1 // indirect
-	github.com/rs/xid v1.6.0 // indirect
-	github.com/spiffe/go-spiffe/v2 v2.5.0 // indirect
+	github.com/pmezard/go-difflib v1.0.0 // indirect
+	github.com/prometheus/client_model v0.6.1 // indirect
+	github.com/prometheus/common v0.52.3 // indirect
+	github.com/prometheus/procfs v0.12.0 // indirect
+	github.com/rs/xid v1.5.0 // indirect
 	github.com/stretchr/objx v0.5.2 // indirect
-	github.com/tinylib/msgp v1.3.0 // indirect
 	github.com/vladimirvivien/gexe v0.1.1 // indirect
-	github.com/x448/float16 v0.8.4 // indirect
-	github.com/zeebo/blake3 v0.2.4 // indirect
-	github.com/zeebo/errs v1.4.0 // indirect
-	go.opentelemetry.io/auto/sdk v1.1.0 // indirect
-	go.opentelemetry.io/contrib/detectors/gcp v1.36.0 // indirect
-	go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.61.0 // indirect
-	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.61.0 // indirect
-	go.opentelemetry.io/otel v1.37.0 // indirect
-	go.opentelemetry.io/otel/metric v1.37.0 // indirect
-	go.opentelemetry.io/otel/sdk v1.37.0 // indirect
-	go.opentelemetry.io/otel/sdk/metric v1.36.0 // indirect
-	go.opentelemetry.io/otel/trace v1.37.0 // indirect
-	go.starlark.net v0.0.0-20230525235612-a134d8f9ddca // indirect
+	github.com/zeebo/blake3 v0.2.3 // indirect
+	go.opencensus.io v0.24.0 // indirect
+	go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.49.0 // indirect
+	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.49.0 // indirect
+	go.opentelemetry.io/otel v1.25.0 // indirect
+	go.opentelemetry.io/otel/metric v1.25.0 // indirect
+	go.opentelemetry.io/otel/trace v1.25.0 // indirect
+	go.starlark.net v0.0.0-20201006213952-227f4aabceb5 // indirect
 	go.uber.org/multierr v1.11.0 // indirect
-	golang.org/x/crypto v0.40.0 // indirect
-	golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56 // indirect
-	golang.org/x/sync v0.16.0 // indirect
-	golang.org/x/sys v0.34.0 // indirect
-	golang.org/x/term v0.33.0 // indirect
-	golang.org/x/time v0.12.0 // indirect
-	golang.org/x/tools v0.34.0 // indirect
+	golang.org/x/crypto v0.24.0 // indirect
+	golang.org/x/sync v0.7.0 // indirect
+	golang.org/x/sys v0.21.0 // indirect
+	golang.org/x/term v0.21.0 // indirect
+	golang.org/x/time v0.5.0 // indirect
 	gomodules.xyz/jsonpatch/v2 v2.4.0 // indirect
-	google.golang.org/genproto v0.0.0-20250505200425-f936aa4a68b2 // indirect
-	google.golang.org/genproto/googleapis/api v0.0.0-20250603155806-513f23925822 // indirect
-	google.golang.org/genproto/googleapis/rpc v0.0.0-20250603155806-513f23925822 // indirect
-	gopkg.in/evanphx/json-patch.v4 v4.12.0 // indirect
+	google.golang.org/genproto v0.0.0-20240227224415-6ceb2ff114de // indirect
+	google.golang.org/genproto/googleapis/api v0.0.0-20240314234333-6e1732d8331c // indirect
+	google.golang.org/genproto/googleapis/rpc v0.0.0-20240401170217-c3f982113cda // indirect
 	gopkg.in/inf.v0 v0.9.1 // indirect
-	k8s.io/kube-openapi v0.0.0-20250318190949-c8a335a9a2ff // indirect
-	sigs.k8s.io/randfill v1.0.0 // indirect
-	sigs.k8s.io/structured-merge-diff/v4 v4.6.0 // indirect
+	gopkg.in/ini.v1 v1.67.0 // indirect
+	gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7 // indirect
+	gopkg.in/yaml.v2 v2.4.0 // indirect
+	k8s.io/component-base v0.29.0 // indirect
+	k8s.io/kube-openapi v0.0.0-20231010175941-2dd684a91f00 // indirect
+	sigs.k8s.io/structured-merge-diff/v4 v4.4.1 // indirect
 )
 
-replace github.com/kopia/kopia => github.com/project-velero/kopia v0.0.0-20250722052735-3ea24d208777
+replace github.com/kopia/kopia => github.com/project-velero/kopia v0.0.0-20240417031915-e07d5b7de567