Enhance and add more evictionHard thresholds in example yaml to encourage holistic parameter changes

[vaibhav2107]

This is a Bug Report

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 example. 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:
https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/

[k8s-ci-robot]

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 triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vaibhav2107]

/language en

[dipesh-rawat]

/retitle Enhance and add more evictionHard thresholds in example yaml to encourage holistic parameter changes

[sftim]

/remove-kind bug
/kind feature

[Affan-7]

/assign