1.15 readme and implemented designs

Signed-off-by: Lyndon-Li <lyonghui@vmware.com>

README.md

@@ -42,11 +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.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.
 

design/Implemented/backup-pvc-config.md

@@ -90,5 +90,5 @@ Once `backupPVC.readOnly` is set to true, users must make sure that the storage
 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]: Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
+[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

@@ -120,4 +120,4 @@ kubectl apply -f <yaml file name>
 
 
 
-[1]: Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
+[1]: unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md

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

@@ -215,9 +215,9 @@ CLI is not changed.
 
 
 
-[1]: ../Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
+[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]: ../Implemented/node-agent-concurrency.md
+[4]: ../node-agent-concurrency.md
 [5]: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/
 

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

@@ -977,6 +977,6 @@ Restore command is kept as is.
 
 
 
-[1]: ../Implemented/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
-[2]: ../Implemented/general-progress-monitoring.md
+[1]: ../unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
+[2]: ../general-progress-monitoring.md
 [3]: ../node-agent-concurrency.md