Skip to content

Commit

Permalink
Merge pull request #10466 from ashwanth1109/fix/issue-10352
Browse files Browse the repository at this point in the history
docs: follow convention for dynamic values
  • Loading branch information
medyagh authored Feb 17, 2021
2 parents d84f178 + eb079e6 commit 40ac52e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions site/content/en/docs/handbook/accessing.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ A NodePort service is the most basic way to get external traffic directly to you
We also have a shortcut for fetching the minikube IP and a service's `NodePort`:

```shell
minikube service --url $SERVICE
minikube service --url <service-name>
```

## Getting the NodePort using kubectl
Expand All @@ -35,7 +35,7 @@ The minikube VM is exposed to the host system via a host-only IP address, that c
To determine the NodePort for your service, you can use a `kubectl` command like this (note that `nodePort` begins with lowercase `n` in JSON output):

```shell
kubectl get service $SERVICE --output='jsonpath="{.spec.ports[0].nodePort}"'
kubectl get service <service-name> --output='jsonpath="{.spec.ports[0].nodePort}"'
```

### Increasing the NodePort range
Expand Down

0 comments on commit 40ac52e

Please sign in to comment.