Merge pull request #119 from DataDog/docs-broken-links

Fix docs broken links

Author: christophetd

docs/reference/attacks/CE_MODULE_LOAD.md

@@ -25,7 +25,7 @@ Container isolation mechanisms are restricted to user-space execution. If an att
 
 Execution within a container process with the `CAP_SYS_MODULE` capability enabled.
 
-See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setuptest-cluster/attacks/CE_MODULE_LOAD.yaml).
+See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setup/test-cluster/attacks/CE_MODULE_LOAD.yaml).
 
 ## Checks
 

docs/reference/attacks/CE_NSENTER.md

@@ -25,7 +25,7 @@ When both `hostPID: true` and `privileged: true` are set, the pod can see all of
 
 Execution within a container process created with `--privileged` AND the `--pid=host` enabled.
 
-See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setuptest-cluster/attacks/CE_NSENTER.yaml).
+See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setup/test-cluster/attacks/CE_NSENTER.yaml).
 
 ## Checks
 

docs/reference/attacks/CE_PRIV_MOUNT.md

@@ -25,7 +25,7 @@ A container running with `privileged: true` disables almost all the container is
 
 Execution within a privileged container process.
 
-See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setuptest-cluster/attacks/CE_PRIV_MOUNT.yaml).
+See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setup/test-cluster/attacks/CE_PRIV_MOUNT.yaml).
 
 ## Checks
 

docs/reference/attacks/EXPLOIT_CONTAINERD_SOCK.md

@@ -42,7 +42,7 @@ docker run -v /var/run/docker.sock:/var/run/docker.sock:ro --rm -it alpine sh
 docker ps
 ```
 
-See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setuptest-cluster/attacks/EXPLOIT_CONTAINERD_SOCK.yaml).
+See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setup/test-cluster/attacks/EXPLOIT_CONTAINERD_SOCK.yaml).
 
 ## Checks
 

docs/reference/attacks/EXPLOIT_HOST_READ.md

@@ -25,7 +25,7 @@ If a sensitive host directory is exposed to a container, even as readonly, it ca
 
 Execution within a container with a sensitive host path mounted as readonly.
 
-See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setuptest-cluster/attacks/EXPLOIT_HOST_READ_TRAVERSE.yaml).
+See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setup/test-cluster/attacks/EXPLOIT_HOST_READ_TRAVERSE.yaml).
 
 ## Checks
 

docs/reference/attacks/EXPLOIT_HOST_WRITE.md

@@ -25,7 +25,7 @@ If a sensitive host directory is mounted in a container with write permissions t
 
 Execution within a container with a sensitive host directory mounted with write permissions.
 
-See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setuptest-cluster/attacks/EXPLOIT_HOST_WRITE.yaml).
+See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setup/test-cluster/attacks/EXPLOIT_HOST_WRITE.yaml).
 
 ## Checks
 

docs/reference/attacks/SHARE_PS_NAMESPACE.md

@@ -25,7 +25,7 @@ Pods represent one or more containers with shared storage and network resources.
 
 Access to a container within a pod running other containers with shared process namespaces
 
-See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setuptest-cluster/attacks/SHARE_PS_NAMESPACE.yaml).
+See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setup/test-cluster/attacks/SHARE_PS_NAMESPACE.yaml).
 
 ## Checks
 

docs/reference/attacks/TOKEN_VAR_LOG_SYMLINK.md

@@ -25,7 +25,7 @@ A pod running as root and with a mount point to the node’s `/var/log` director
 
 Execution as root within a container process with the host `/var/log/` (or any parent directory) mounted inside the container.
 
-See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setuptest-cluster/attacks/TOKEN_VAR_LOG_SYMLINK.yaml).
+See the [example pod spec](https://github.com/DataDog/KubeHound/tree/main/test/setup/test-cluster/attacks/TOKEN_VAR_LOG_SYMLINK.yaml).
 
 ## Checks