From 38e01c4778a138abc91bc5152ffeadeece3a9516 Mon Sep 17 00:00:00 2001 From: Anthony Date: Wed, 23 Aug 2017 07:38:08 +0800 Subject: [PATCH] Update network-policies.md (#5141) modify "tcp" to "TCP" --- docs/concepts/services-networking/network-policies.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/services-networking/network-policies.md b/docs/concepts/services-networking/network-policies.md index 68f5900480..0371cfd3cc 100644 --- a/docs/concepts/services-networking/network-policies.md +++ b/docs/concepts/services-networking/network-policies.md @@ -65,8 +65,8 @@ __ingress__: Each `NetworkPolicy` includes a list of whitelist `ingress` rules. So, the example NetworkPolicy: 1. isolates "role=db" pods in the "default" namespace (if they weren't already isolated) -2. allows connections to tcp port 6379 of "role=db" pods in the "default" namespace from any pod in the "default" namespace with the label "role=frontend" -3. allows connections to tcp port 6379 of "role=db" pods in the "default" namespace from any pod in a namespace with the label "project=myproject" +2. allows connections to TCP port 6379 of "role=db" pods in the "default" namespace from any pod in the "default" namespace with the label "role=frontend" +3. allows connections to TCP port 6379 of "role=db" pods in the "default" namespace from any pod in a namespace with the label "project=myproject" See the [NetworkPolicy getting started guide](/docs/getting-started-guides/network-policy/walkthrough) for further examples.