feat: add full dir-staging deployment setup

Signed-off-by: Ramiz Polic <rpolic@cisco.com>

Author: ramizpolic

README.md

@@ -130,6 +130,9 @@ in the same cluster, as they may conflict with each other.
 <details>
 <summary><strong>View Production Setup</strong></summary>
 
+<br/>
+<br/>
+
 1. Create Minikube cluster
 
 ```bash
@@ -141,6 +144,7 @@ minikube start -p dir-prod
 The deployment uses `*.test` domain for Ingress resources. 
 
 For local testing purposes, Minikube Ingress controller is required to route traffic to our Ingress resources.
+
 Otherwise, if you are deploying to a cloud provider with its own Ingress controller,
 make sure that it supports SSL Passthrough.
 
@@ -159,7 +163,9 @@ kubectl patch deployment -n ingress-nginx ingress-nginx-controller --type='json'
 The deployment uses `*.test` domain for Ingress resources. 
 
 For local testing purposes, we need to configure DNS resolution
-inside Minikube cluster to resolve `*.test` domain to Minikube IP address.
+inside Minikube cluster to resolve `*.test` domain to Minikube IP address
+using [minikube/ingress-dns](https://minikube.sigs.k8s.io/docs/handbook/addons/ingress-dns) guide.
+
 Otherwise, if you are deploying to a cloud provider with its own Ingress controller,
 you can skip this step.
 
@@ -180,6 +186,7 @@ The deployment uses CertManager `letsencrypt` issuer to issue TLS certificates f
 
 For local testing purposes, we will create a self-signed root CA certificate
 and configure CertManager to use it as `letsencrypt` issuer.
+
 Otherwise, if you are deploying to a cloud provider with its own CertManager,
 you can skip this step, but ensure that `letsencrypt` issuer is available.