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

Merge pull request #28984 from chirangaalwis/patch-1

Browse Source 
[NetworkPolicy][EndPort] Fix incorrect grammar of the valid range of `endPort` property
This commit is contained in:
Kubernetes Prow Robot
2021-07-17 05:38:50 -07:00
committed by GitHub
parent 5f8fdc6abb 46987cf0e9
commit 0ca94eebab
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/network-policies.md
+1 -1
View File
@@ -255,7 +255,7 @@ The above rule allows any Pod with label `db` on the namespace `default` to comm
The following restrictions apply when using this field: The following restrictions apply when using this field:
* As an alpha feature, this is disabled by default. To enable the `endPort` field at a cluster level, you (or your cluster administrator) need to enable the `NetworkPolicyEndPort` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the API server with `--feature-gates=NetworkPolicyEndPort=true,…`. * As an alpha feature, this is disabled by default. To enable the `endPort` field at a cluster level, you (or your cluster administrator) need to enable the `NetworkPolicyEndPort` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the API server with `--feature-gates=NetworkPolicyEndPort=true,…`.
* The `endPort` field must be equal than or greater to the `port` field. * The `endPort` field must be equal to or greater than the `port` field.
* `endPort` can only be defined if `port` is also defined. * `endPort` can only be defined if `port` is also defined.
* Both ports must be numeric. * Both ports must be numeric.