Added instructions for Rancher Desktop (#9035)

Signed-off-by: Gunasekhar Matamalam <[email protected]> Signed-off-by: Gunasekhar Matamalam <[email protected]>
kubernetes · Sep 9, 2022 · b212b5a · b212b5a
1 parent 981ce38
commit b212b5a
Showing 1 changed file with 9 additions and 0 deletions.
diff --git a/docs/deploy/index.md b/docs/deploy/index.md
@@ -20,6 +20,7 @@ ingress controller for your particular environment or cloud provider.
 
 - [Environment-specific instructions](#environment-specific-instructions)
   - ... [Docker Desktop](#docker-desktop)
+  - ... [Rancher Desktop](#rancher-desktop)
   - ... [minikube](#minikube)
   - ... [MicroK8s](#microk8s)
   - ... [AWS](#aws)
@@ -186,6 +187,14 @@ will be assigned the `EXTERNAL-IP` of `localhost`, which means that it will be r
 doesn't work, you might have to fall back to the `kubectl port-forward` method described in the 
 [local testing section](#local-testing).
 
+#### Rancher Desktop
+
+Rancher Desktop provides Kubernetes and Container Management on the desktop. Kubernetes is enabled by default in Rancher Desktop. 
+
+Rancher Desktop uses K3s under the hood, which in turn uses Traefik as the default ingress controller for the Kubernetes cluster. To use NGINX ingress controller in place of the default Traefik, disable Traefik from Preference > Kubernetes menu.
+
+Once traefik is disabled, the NGINX ingress controller can be installed on Rancher Desktop using the default [quick start](#quick-start) instructions. Follow the instructions described in the [local testing section](#local-testing) to try a sample.
+
 ### Cloud deployments
 
 If the load balancers of your cloud provider do active healthchecks on their backends (most do), you can change the