Difference between revisions of "Minikube tunnel"
Jump to navigation
Jump to search
| Line 27: | Line 27: | ||
* <code>[[minikube addons enable ingress]]</code> | * <code>[[minikube addons enable ingress]]</code> | ||
* [[minikube start --listen-address]] | * [[minikube start --listen-address]] | ||
| + | * [[minikube service]] | ||
== See also == | == See also == | ||
Latest revision as of 14:29, 6 February 2024
minikube tunnel Status: machine: minikube pid: 60364 route: 10.96.0.0/12 -> 192.168.64.5 minikube: Running services: [my-release-ingress-nginx-controller, istio-ingressgateway] errors: minikube: no errors router: no errors loadbalancer emulator: no errors
minikube tunnel ✅ Tunnel successfully started 📌 NOTE: Please do not close this terminal as this process must stay alive for the tunnel to be accessible ... ❗ The service/ingress grafana requires privileged ports to be exposed: [80 443] 🔑 sudo permission will be asked for it. 🏃 Starting tunnel for service grafana.
Related terms[edit]
See also[edit]
- minikube: [
status|start|stop|version|addons|addons list|addons enable|dashboard|logs|tunnel|ssh|config|image | delete],config setminikube start --vm=true, kicbase,~/.minikube/, minikube --help, Minikube changelog
Advertising:
