Skip to content

Commit 274fad5

Browse files
authored
Merge pull request #38224 from Shubham82/remove_ref
Removed Reference from the removed Feature Gates.
2 parents c02ad13 + 0b79c2b commit 274fad5

File tree

1 file changed

+0
-13
lines changed

1 file changed

+0
-13
lines changed

content/en/docs/concepts/policy/pid-limiting.md

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -73,13 +73,6 @@ The value you specified declares that the specified number of process IDs will
7373
be reserved for the system as a whole and for Kubernetes system daemons
7474
respectively.
7575

76-
{{< note >}}
77-
Before Kubernetes version 1.20, PID resource limiting with Node-level
78-
reservations required enabling the [feature
79-
gate](/docs/reference/command-line-tools-reference/feature-gates/)
80-
`SupportNodePidsLimit` to work.
81-
{{< /note >}}
82-
8376
## Pod PID limits
8477

8578
Kubernetes allows you to limit the number of processes running in a Pod. You
@@ -89,12 +82,6 @@ To configure the limit, you can specify the command line parameter `--pod-max-pi
8982
to the kubelet, or set `PodPidsLimit` in the kubelet
9083
[configuration file](/docs/tasks/administer-cluster/kubelet-config-file/).
9184

92-
{{< note >}}
93-
Before Kubernetes version 1.20, PID resource limiting for Pods required enabling
94-
the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
95-
`SupportPodPidsLimit` to work.
96-
{{< /note >}}
97-
9885
## PID based eviction
9986

10087
You can configure kubelet to start terminating a Pod when it is misbehaving and consuming abnormal amount of resources.

0 commit comments

Comments
 (0)