From 91cbc4095663e0e95d8522a834dc19900bcf3542 Mon Sep 17 00:00:00 2001 From: Lyndon-Li Date: Fri, 6 Feb 2026 18:46:41 +0800 Subject: [PATCH] move implemented design for 1.18 Signed-off-by: Lyndon-Li --- changelogs/CHANGELOG-1.18.md | 4 ++-- design/{ => Implemented}/backup-repo-cache-volume.md | 0 design/{ => Implemented}/bsl-certificate-support_design.md | 0 design/{ => Implemented}/concurrent-backup-processing.md | 0 design/{ => Implemented}/wildcard-namespace-support-design.md | 0 5 files changed, 2 insertions(+), 2 deletions(-) rename design/{ => Implemented}/backup-repo-cache-volume.md (100%) rename design/{ => Implemented}/bsl-certificate-support_design.md (100%) rename design/{ => Implemented}/concurrent-backup-processing.md (100%) rename design/{ => Implemented}/wildcard-namespace-support-design.md (100%) diff --git a/changelogs/CHANGELOG-1.18.md b/changelogs/CHANGELOG-1.18.md index d8a8aa6d8..66c486ddf 100644 --- a/changelogs/CHANGELOG-1.18.md +++ b/changelogs/CHANGELOG-1.18.md @@ -16,7 +16,7 @@ https://velero.io/docs/v1.18/upgrade-to-1.18/ #### Concurrent backup In v1.18, Velero is capable to process multiple backups concurrently. This is a significant usability improvement, especially for multiple tenants or multiple users case, backups submitted from different users could run their backups simultaneously without interfering with each other. -Check design https://github.com/vmware-tanzu/velero/blob/main/design/concurrent-backup-processing.md for more details. +Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/concurrent-backup-processing.md for more details. #### Cache volume for data movers In v1.18, Velero allows users to configure cache volumes for data mover pods during restore for CSI snapshot data movement and fs-backup. This brings below benefits: @@ -24,7 +24,7 @@ In v1.18, Velero allows users to configure cache volumes for data mover pods dur - Solve the problem that multiple data mover pods fail to run concurrently in one node when the node's ephemeral disk is limited - Working together with backup repository's cache limit configuration, cache volume with appropriate size helps to improve the restore throughput -Check design https://github.com/vmware-tanzu/velero/blob/main/design/backup-repo-cache-volume.md for more details. +Check design https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/backup-repo-cache-volume.md for more details. #### Incremental size for data movers In v1.18, Velero allows users to observe the incremental size of data movers backups for CSI snapshot data movement and fs-backup, so that users could visually see the data reduction due to incremental backup. diff --git a/design/backup-repo-cache-volume.md b/design/Implemented/backup-repo-cache-volume.md similarity index 100% rename from design/backup-repo-cache-volume.md rename to design/Implemented/backup-repo-cache-volume.md diff --git a/design/bsl-certificate-support_design.md b/design/Implemented/bsl-certificate-support_design.md similarity index 100% rename from design/bsl-certificate-support_design.md rename to design/Implemented/bsl-certificate-support_design.md diff --git a/design/concurrent-backup-processing.md b/design/Implemented/concurrent-backup-processing.md similarity index 100% rename from design/concurrent-backup-processing.md rename to design/Implemented/concurrent-backup-processing.md diff --git a/design/wildcard-namespace-support-design.md b/design/Implemented/wildcard-namespace-support-design.md similarity index 100% rename from design/wildcard-namespace-support-design.md rename to design/Implemented/wildcard-namespace-support-design.md