Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: As we know that, in eviction hard thresholds, when we change the default value of any one of the four parameters (memory.available, nodefs.available, imagefs.available, nodefs.inodesFree), then the value of other parameters will be set to 0. Although this is an expected behaviour but I think it's not a good motivation for user to change only the one parameter as given in this . As setting other parameters to 0 is not a good scenario. Proposed Solution: Is there any good case by setting the other parameters to 0 or we should change the example to motivate users to change all parameters Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language en
/retitle Enhance and add more evictionHard thresholds in example yaml to encourage holistic parameter changes
/remove-kind bug /kind feature
/assign

Discussion:
port: 20250 serializeImagePulls: false evictionHard: <del> memory.available:  "200Mi" </del> <ins> memory.available:  "100Mi" nodefs.available:  "10%" nodefs.inodesFree: "5%" imagefs.available: "15%" </ins> ``` <del> In the example, the kubelet is configured to serve on IP address 192.168.0.8 and port 20250, pull images in parallel, and evict Pods when available memory drops below 200Mi. Since only one of the four evictionHard thresholds is configured, 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. </del> <ins> In this example, the kubelet is configured with the following settings: 1. `address`: The kubelet will serve on IP address `192.168.0.8`. 2. `port`: The kubelet will serve on port `20250`. 3. `serializeImagePulls`: Image pulls will be done in parallel. 4. `evictionHard`: The kubelet will evict Pods under one of the following conditions: - When the node's available memory drops below 100MiB. - When the node's main filesystem's available space is less than 10%. - When the image filesystem's available space is less than 15%. - When more than 95% of the node's main filesystem's inodes are in use. </ins> {{< note >}} In the example, by changing the default value of only one parameter for

the threshold values respectively. {{< /note >}} <ins> The `imagefs` is an optional filesystem that container runtimes use to store container images and container writable layers. </ins> ## Start a kubelet process configured via the config file {{< note >}}