From 25b4555d90d6e061ce552b2817d2a8a4da6021df Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20Str=C3=B6mberg?= Date: Wed, 29 May 2019 11:39:48 -0700 Subject: [PATCH] Mention NodePort ranges --- docs/networking.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/networking.md b/docs/networking.md index df9aed72e8..11c7aaa54b 100644 --- a/docs/networking.md +++ b/docs/networking.md @@ -22,6 +22,16 @@ We also have a shortcut for fetching the minikube IP and a service's `NodePort`: `minikube service --url $SERVICE` + +### Increasing the NodePort range + +By default, minikube only exposes ports 30000-32767. If this is not enough, you can configure the apiserver to allow all ports using: + +`minikube start --extra-config=apiserver.service-node-port-range=1-65535` + +This flag also accepts a comma separated list of ports and port ranges. + + ## Access to LoadBalancer services using `minikube tunnel` Services of type `LoadBalancer` can be exposed via the `minikube tunnel` command.