whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add review suggestions

Browse Source 
Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
Ricardo Katz
2021-02-26 17:34:57 -03:00
committed by GitHub
parent a799505a5e
commit c0bb986cd6
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/network-policies.md
+3 -2
View File
@@ -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" >}} {{< 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: 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. * When using `endPort` field, the `port` field must be numeric.
{{< note >}} {{< 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 >}} {{< /note >}}
## What you can't do with network policies (at least, not yet) ## What you can't do with network policies (at least, not yet)