diff --git a/getting-started/deployment_guide.md b/getting-started/deployment_guide.md
index 77b59a68de..37e97b5bcf 100644
--- a/getting-started/deployment_guide.md
+++ b/getting-started/deployment_guide.md
@@ -94,42 +94,7 @@ karmor log
 ## Prerequisites
 1. [K3s](../deployments/k3s)
 2. [MicroK8s](../contribution/microk8s)
-
-  
-3. <details>
-    <summary>Minikube</summary>
-      If virtualbox and vagrant are not installed on your machine, please the following commands in advance.
-
-      ```
-      $ cd KubeArmor/contribution/minikube
-      ~/KubeArmor/contribution/minikube$ ./install_virtualbox.sh
-      ~/KubeArmor/contribution/minikube$ sudo reboot
-      ```
-
-      After rebooting the machine, please keep running the following commands.
-
-      ```
-      $ cd KubeArmor/contribution/minikube
-      ~/KubeArmor/contribution/minikube$ ./install_minikube.sh
-      ```
-
-      Ensure to use virtualbox driver when running minikube. This step is necessary in order to mount roofs as read/write.
-
-      ```
-      $ minikube config set driver virtualbox
-      ```
-
-      In order to use KubeArmor, Minikube needs to support eBPF capabilities. Unfortunately, Minikube doesn't suport them by default. We have compiled Minikube's Kernel with eBPF capablities and AppArmor which is required to enforce security policies. Thus, please run the following command rather than simply running "minikube start".
-
-      ```
-      ~/KubeArmor/contribution/minikube$ ./start_minikube.sh
-      ```
-
-      It will use the minikube image with Linux kernel 5.4.40 with AppArmor service enabled by default.
-
-      If you see no error, you're ready to test KubeArmor.
-  </details>
-
+3. [Minikube](../contribution/minikube)
 4. [Self-managed K8s](../contribution/self-managed-k8s)
 5. [Amazon Elastic Kubernetes Service (EKS)](../deployments/EKS#prerequisite-for-the-deployment)