From c0bb986cd6537034d523e917cfc2728aa56e6a9d Mon Sep 17 00:00:00 2001 From: Ricardo Katz Date: Fri, 26 Feb 2021 17:34:57 -0300 Subject: [PATCH] Add review suggestions Co-authored-by: Tim Bannister --- .../en/docs/concepts/services-networking/network-policies.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/network-policies.md b/content/en/docs/concepts/services-networking/network-policies.md index 2a829b3ab4..d5c14f9465 100644 --- a/content/en/docs/concepts/services-networking/network-policies.md +++ b/content/en/docs/concepts/services-networking/network-policies.md @@ -225,7 +225,7 @@ You must be using a {{< glossary_tooltip text="CNI" term_id="cni" >}} plugin tha {{< feature-state for_k8s_version="v1.21" state="alpha" >}} -When writing a Network Policy, you can target a range of Ports instead of a single port. +When writing a NetworkPolicy, you can target a range of ports instead of a single port. This is achiveable with the usage of the `endPort` field, as the following example: @@ -260,7 +260,8 @@ The following restrictions apply when using this field: * When using `endPort` field, the `port` field must be numeric. {{< note >}} -You must be using a {{< glossary_tooltip text="CNI" term_id="cni" >}} plugin that supports endPort field in NetworkPolicies ports specification. +Your cluster must be using a {{< glossary_tooltip text="CNI" term_id="cni" >}} plugin that +supports the `endPort` field in NetworkPolicy specifications. {{< /note >}} ## What you can't do with network policies (at least, not yet)