From 29e25a77b03c0c8d34c612a74adffb2362af2bff Mon Sep 17 00:00:00 2001 From: Chuck Lantz Date: Thu, 11 Aug 2022 15:11:00 -0500 Subject: Add notes for Features that have them (#88) Co-authored-by: Brigit Murtaugh --- src/kubectl-helm-minikube/NOTES.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 src/kubectl-helm-minikube/NOTES.md (limited to 'src/kubectl-helm-minikube/NOTES.md') diff --git a/src/kubectl-helm-minikube/NOTES.md b/src/kubectl-helm-minikube/NOTES.md new file mode 100644 index 0000000..b0d1a80 --- /dev/null +++ b/src/kubectl-helm-minikube/NOTES.md @@ -0,0 +1,12 @@ +## 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 `:` 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 +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 & +``` -- cgit v1.2.3