Updated the behaviour of evictionHard (#36961)

* Updated the behaviour of evictionHard

* Modified the changes in documenting hard eviction behaviour

* Updated the changes
pull/37140/head
Vaibhav Goel 2022-10-02 20:58:13 +05:30 committed by GitHub
parent 55bbd4bbb2
commit 8ff7e1845d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 13 additions and 0 deletions

View File

@ -154,6 +154,12 @@ The kubelet has the following default hard eviction thresholds:
* `imagefs.available<15%`
* `nodefs.inodesFree<5%` (Linux nodes)
These default values of hard eviction thresholds will only be set if none
of the parameters is changed. If you changed the value of any parameter,
then the values of other parameters will not be inherited as the default
values and will be set to zero. In order to provide custom values, you
should provide all the thresholds respectively.
### Eviction monitoring interval
The kubelet evaluates eviction thresholds based on its configured `housekeeping-interval`

View File

@ -43,6 +43,13 @@ other evictionHard thresholds are reset to 0 from their built-in defaults.
All other Kubelet configuration values are left at their built-in defaults, unless overridden
by flags. Command line flags which target the same value as a config file will override that value.
{{< note >}}
In the example, by changing the default value of only one parameter for
evictionHard, the default values of other parameters will not be inherited and
will be set to zero. In order to provide custom values, you should provide all
the threshold values respectively.
{{< /note >}}
## Start a Kubelet process configured via the config file
{{< note >}}