Improve Ingress example (#1574)

Author: Chuxel

containers/kubernetes-helm-minikube/README.md

@@ -29,7 +29,10 @@ When configuring [Ingress](https://kubernetes.io/docs/concepts/services-networki
 However, GitHub Codespaces does not yet support this capability, so you'll need to use `kubectl` to forward the port to localhost. This adds minimal overhead since everything is on the same machine. E.g.:
 
 ```bash
-kubectl port-forward service/ingress-nginx 80:80
+minikube start
+minikube addons enable ingress
+# Run this to forward to localhost in the background
+nohup kubectl port-forward --pod-running-timeout=24h -n ingress-nginx service/ingress-nginx-controller :80 &
 ```
 
 ## Using this definition with an existing folder

containers/kubernetes-helm/README.md

@@ -93,7 +93,10 @@ When configuring [Ingress](https://kubernetes.io/docs/concepts/services-networki
 However, GitHub Codespaces does not yet support this capability, so you'll need to use `kubectl` to forward the port to localhost. This adds minimal overhead since everything is on the same machine. E.g.:
 
 ```bash
-kubectl port-forward service/ingress-nginx 80:80
+minikube start
+minikube addons enable ingress
+# Run this to forward to localhost in the background
+nohup kubectl port-forward --pod-running-timeout=24h -n ingress-nginx service/ingress-nginx-controller :80 &
 ```
 
 ## Using this definition with an existing folder

script-library/docs/kubectl-helm.md

@@ -36,14 +36,17 @@ Or as a feature:
 |minikube SHA256| | `automatic`| SHA256 checksum to use to verify the minikube download. `automatic` will download the checksum. |
 |Non-root user| | `automatic`| Specifies a user in the container other than root that will be using the desktop. A value of `automatic` will cause the script to check for a user called `vscode`, then `node`, `codespace`, and finally a user with a UID of `1000` before falling back to `root`. |
 
-## A note on ingress and port forwarding
+## A note on Ingress and port forwarding
 
 When configuring [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) for your Kubernetes cluster, note that by default Kubernetes will bind to a specific interface's IP rather than localhost or all interfaces. This is why you need to use the Kubernetes Node's IP when connecting - even if there's only one Node as in the case of Minikube. Port forwarding in Remote - Containers will allow you to specify `<ip>:<port>` in either the `forwardPorts` property or through the port forwarding UI in VS Code.
 
 However, GitHub Codespaces does not yet support this capability, so you'll need to use `kubectl` to forward the port to localhost. This adds minimal overhead since everything is on the same machine. E.g.:
 
 ```bash
-kubectl port-forward service/ingress-nginx 80:80
+minikube start
+minikube addons enable ingress
+# Run this to forward to localhost in the background
+nohup kubectl port-forward --pod-running-timeout=24h -n ingress-nginx service/ingress-nginx-controller :80 &
 ```
 
 ## Usage