From 590cac5fb53d10a3cf6e2e1e32f801a53db4b211 Mon Sep 17 00:00:00 2001 From: Charle Demers Date: Fri, 4 Dec 2020 10:35:39 -0500 Subject: [PATCH] Update content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md Co-authored-by: Tim Bannister --- .../port-forward-access-application-cluster.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md b/content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md index eb37432feb..1a6cb26711 100644 --- a/content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md +++ b/content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md @@ -190,8 +190,8 @@ the slightly simpler syntax: kubectl port-forward deployment/redis-master :6379 ``` -An allocated local port in the upper range will be displayed as a result, the output -will be similar to this: +The `kubectl` tool finds a local port number that is not in use (avoiding low ports numbers, +because these might be used by other applications). The output is similar to: ``` Forwarding from 127.0.0.1:62162 -> 6379