Remove mention of minikube tunnel

Signed-off-by: Thomas Cooper <code@tomcooper.dev>

Author: tomncooper

README.md

@@ -104,11 +104,10 @@ kubectl apply -k 'https://github.com/streamshub/developer-quickstart//overlays/m
 
 ### Minikube
 
-When using minikube, (if you didn't enable it when you created the minikube cluster) enable the ingress addon and run `minikube tunnel`:
+When using minikube, enable the ingress addon (if not already enabled):
 
 ```bash
 minikube addons enable ingress
-minikube tunnel
 ```
 
 Then use port-forwarding to access the console:

docs/accessing-services.md

@@ -13,15 +13,13 @@ For the Console to startup correctly and be accessible, you need an Ingress cont
 
 #### minikube
 
-Enable the ingress addon (if not already enabled) and start a tunnel:
+Enable the ingress addon (if not already enabled):
 
 ```shell
 minikube addons enable ingress
-minikube tunnel
 ```
 
-You will need to leave the tunnel running in an open terminal.
-Switch to a new terminal and use port-forwarding to access the console:
+Use port-forwarding to access the console:
 
 ```bash
 kubectl port-forward -n streamshub-console svc/streamshub-console-console-service 8090:80

install.sh

@@ -191,6 +191,9 @@ main() {
         echo "  kubectl get prometheus -n monitoring"
         echo "  kubectl get podmonitor -n monitoring"
     fi
+    echo ""
+    echo "Note: It may take several minutes for all resources to become ready."
+    echo ""
 }
 
 main