🐛 📝 Fix broken links in document files

Signed-off-by: vankichi <[email protected]>

Makefile.d/k8s.mk

@@ -41,6 +41,7 @@ k8s/manifest/update: \
 		--set manager.index.saver.enabled=true \
 		--set manager.index.creator.enabled=true \
 		--set manager.index.corrector.enabled=true \
+		--set gateway.mirror.enabled=true \
 		--output-dir $(TEMP_DIR) \
 		charts/vald
 	mkdir -p k8s/gateway

docs/api/insert.md

@@ -100,7 +100,7 @@ Inset RPC is the method to add a new single vector.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -226,7 +226,7 @@ It's the recommended method to insert a large number of vectors.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -349,7 +349,7 @@ Please be careful that the size of the request exceeds the limit.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 

docs/api/object.md

@@ -67,7 +67,7 @@ Exists RPC is the method to check that a vector exists in the `vald-agent`.
 |  5   | NOT_FOUND         |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -148,7 +148,7 @@ GetObject RPC is the method to get the metadata of a vector inserted into the `v
 |  5   | NOT_FOUND         |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -242,7 +242,7 @@ Each Upsert request and response are independent.
 |  5   | NOT_FOUND         |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 

docs/api/remove.md

@@ -101,7 +101,7 @@ Remove RPC is the method to remove a single vector.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -222,7 +222,7 @@ RemoveByTimestamp RPC is the method to remove vectors based on timestamp.
 |  5   | NOT_FOUND         |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -344,7 +344,7 @@ It's the recommended method to remove a large number of vectors.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -465,7 +465,7 @@ Please be careful that the size of the request exceeds the limit.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 

docs/api/search.md

@@ -146,7 +146,7 @@ Search RPC is the method to search vector(s) similar to the request vector.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -267,7 +267,7 @@ The vector with the same requested ID should be indexed into the `vald-agent` be
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -403,7 +403,7 @@ Each Search request and response are independent.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -539,7 +539,7 @@ Each SearchByID request and response are independent.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -684,7 +684,7 @@ Please be careful that the size of the request exceeds the limit.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -830,7 +830,7 @@ Please be careful that the size of the request exceeds the limit.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -946,7 +946,7 @@ LinearSearch RPC is the method to linear search vector(s) similar to the request
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -1064,7 +1064,7 @@ You will get a `NOT_FOUND` error if the vector isn't stored.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -1196,7 +1196,7 @@ Each LinearSearch request and response are independent.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -1328,7 +1328,7 @@ Each LinearSearchByID request and response are independent.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -1469,7 +1469,7 @@ Please be careful that the size of the request exceeds the limit.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -1611,7 +1611,7 @@ Please be careful that the size of the request exceeds the limit.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 

docs/api/update.md

@@ -102,7 +102,7 @@ Update RPC is the method to update a single vector.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -231,7 +231,7 @@ It's the recommended method to update the large amount of vectors.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -357,7 +357,7 @@ Please be careful that the size of the request exceeds the limit.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 

docs/api/upsert.md

@@ -105,7 +105,7 @@ Upsert RPC is the method to update the inserted vector to a new single vector or
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -232,7 +232,7 @@ It’s the recommended method to upsert a large number of vectors.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 
@@ -356,7 +356,7 @@ Please be careful that the size of the request exceeds the limit.
 |  10  | ABORTED           |
 |  13  | INTERNAL          |
 
-Please refer to [Response Status Code](./status.md) for more details.
+Please refer to [Response Status Code](../status.md) for more details.
 
 ### Troubleshooting
 

docs/contributing/coding-style.md

@@ -1407,4 +1407,4 @@ Since each package has its purpose, we decided to apply different strategies to
 
 For the rest of the `./pkg` packages, we decided to implement the unit test for the exported function only.
 
-Please follow the [unit test guideline](./unit-test-guideline.md) for more details on how to implement good unit test.
+Please follow the [unit test guideline](../unit-test-guideline.md) for more details on how to implement good unit test.

docs/performance/continuous-benchmark.md

@@ -61,8 +61,8 @@ And, Benchmark Operator also applies it to the Kubernetes cluster based on `Vald
 | search_config              |           | request config for search job                                                                                         | object                                                                   | ref: [config](#search-cfg-props)                                                             |
 | remove_config              |           | request config for remove job                                                                                         | object                                                                   | ref: [config](#remove-cfg-props)                                                             |
 | object_config              |           | request config for object job                                                                                         | object                                                                   | ref: [config](#object-cfg-props)                                                             |
-| client_config              |           | gRPC client config for running benchmark job<BR>Tune if can not getting the expected performance with default config. | object                                                                   | ref: [defaults.grpc](https://github.com/vdaas/vald/blob/main/charts/vald/README.md)          |
-| server_config              |           | server config for benchmark job pod<BR>Tune if can not getting the expected performance with default config.          | object                                                                   | ref: [defaults.server_config](https://github.com/vdaas/vald/blob/main/charts/vald/README.md) |
+| client_config              |           | gRPC client config for running benchmark job<BR>Tune if can not getting the expected performance with default config. | object                                                                   | ref: [defaults.grpc](https://github.com/vdaas/vald/blob/main/charts/vald/values.yaml)          |
+| server_config              |           | server config for benchmark job pod<BR>Tune if can not getting the expected performance with default config.          | object                                                                   | ref: [defaults.server_config](https://github.com/vdaas/vald/blob/main/charts/vald/values.yaml) |
 
 <a id="target-prop" />
 

docs/troubleshooting/client-side.md

@@ -55,4 +55,4 @@ Please check your CPU information.
 
 - [Provisioning Troubleshooting](../troubleshooting/provisioning.md)
 - [API Status](../api/status.md)
-- [FAQ](../support/FAQ.md)
+- [FAQ](/docs/support/faq)

docs/tutorial/get-started-with-faiss-agent.md

@@ -1,6 +1,6 @@
 # Get Started
 
-This tutorial is for those who have already completed [Get Started](https://github.com/vdaas/vald/blob/main/docs/tutorial/get-started.md).
+This tutorial is for those who have already completed [Get Started](../tutorial/get-started.md).
 Please refer to Prepare the Kubernetes Cluster and others there.
 
 ## Deploy Vald on Kubernetes Cluster

docs/tutorial/vald-multicluster-on-k8s.md

@@ -88,7 +88,7 @@ In this section, you will deploy three Vald clusters consisting of `vald-agent-n
    git clone https://github.com/vdaas/vald.git &&　cd vald
    ```
 
-2. Deploy on the `vald-01` Namespace using [dev-vald-01.yaml](https://github.com/vdaas/vald/blob/feature/mirror-gateway-definition/charts/vald/values/multi-vald/dev-vald-01.yaml) and [values.yaml](https://github.com/vdaas/vald/blob/main/example/helm/values.yaml)
+2. Deploy on the `vald-01` Namespace using [dev-vald-01.yaml](https://github.com/vdaas/vald/blob/main/charts/vald/values/multi-vald/dev-vald-01.yaml) and [values.yaml](https://github.com/vdaas/vald/blob/main/example/helm/values.yaml)
 
    ```bash
    helm install vald-cluster-01 charts/vald \
@@ -97,7 +97,7 @@ In this section, you will deploy three Vald clusters consisting of `vald-agent-n
      -n vald-01
    ```
 
-3. Deploy on the `vald-02` Namespace using [dev-vald-02.yaml](https://github.com/vdaas/vald/blob/feature/mirror-gateway-definition/charts/vald/values/multi-vald/dev-vald-02.yaml) and [values.yaml](https://github.com/vdaas/vald/blob/main/example/helm/values.yaml)
+3. Deploy on the `vald-02` Namespace using [dev-vald-02.yaml](https://github.com/vdaas/vald/blob/main/charts/vald/values/multi-vald/dev-vald-02.yaml) and [values.yaml](https://github.com/vdaas/vald/blob/main/example/helm/values.yaml)
 
    ```bash
    helm install vald-cluster-02 charts/vald \
@@ -106,7 +106,7 @@ In this section, you will deploy three Vald clusters consisting of `vald-agent-n
      -n vald-02
    ```
 
-4. Deploy on the `vald-03` Namespace using [dev-vald-03.yaml](https://github.com/vdaas/vald/blob/feature/mirror-gateway-definition/charts/vald/values/multi-vald/dev-vald-03.yaml) and [values.yaml](https://github.com/vdaas/vald/blob/main/example/helm/values.yaml)
+4. Deploy on the `vald-03` Namespace using [dev-vald-03.yaml](https://github.com/vdaas/vald/blob/main/charts/vald/values/multi-vald/dev-vald-03.yaml) and [values.yaml](https://github.com/vdaas/vald/blob/main/example/helm/values.yaml)
 
    ```bash
    helm install vald-cluster-03 charts/vald \
@@ -194,7 +194,7 @@ It requires applying the `ValdMirrorTarget` Custom Resource to the one Namespace
 
 When applied successfully, the destination information is automatically created on other Namespaces when interconnected with each `vald-mirror-gateway`.
 
-This tutorial will deploy the [ValdMirrorTarget](https://github.com/vdaas/vald/tree/main/charts/vald/values/mirror-target.yaml) Custom Resource to the `vald-03` Namespace with the following command.
+This tutorial will deploy the [ValdMirrorTarget](https://github.com/vdaas/vald/blob/main/charts/vald/values/multi-vald/mirror-target.yaml) Custom Resource to the `vald-03` Namespace with the following command.
 
 ```bash
 kubectl apply -f ./charts/vald/values/multi-vald/mirror-target.yaml -n vald-03
@@ -255,7 +255,7 @@ If you are interested, please refer to [SDKs](https://vald.vdaas.org/docs/user-
 
 3. Run Example
 
-   We use [example/client/mirror/main.go](https://github.com/vdaas/vald/blob/feature/mirror-gateway-example/example/client/mirror/main.go) to run the example.
+   We use [example/client/mirror/main.go](https://github.com/vdaas/vald/blob/main/example/client/mirror/main.go) to run the example.
 
    This example will insert and index 400 vectors into the Vald cluster from the Fashion-MNIST dataset via [gRPC](https://grpc.io/).
    And then, after waiting for indexing, it will request to search the nearest vector 10 times to all Vald clusters. You will get the 10 nearest neighbor vectors for each search query.

docs/user-guides/cluster-role-binding.md

@@ -141,7 +141,7 @@ In this section, we will describe how to configure it and how to customize these
 
 ### Cluster role configuration for Vald Mirror Gateway
 
-By looking at the [cluster role configuration](https://github.com/vdaas/vald/blob/main/k8s/gatewat/mirror/clusterrole.yaml), the access right of the following resources are granted to the cluster role `gateway-mirror`.
+By looking at the [cluster role configuration](https://github.com/vdaas/vald/blob/main/k8s/gateway/mirror/clusterrole.yaml), the access right of the following resources are granted to the cluster role `gateway-mirror`.
 
 ```yaml
 apiVersion: rbac.authorization.k8s.io/v1