define resource limits to avoid eviction about csi-driver-host-path HOT 14 OPEN

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from csi-driver-host-path.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from csi-driver-host-path.

/remove-lifecycle rotten

from csi-driver-host-path.

In addition to resource requests, we should recommend a pod priority

As mentioned on the mailing list. An important DaemonSet should also have a blanket toleration.

DaemonSets that are system-critical are recommended to include a blanket-toleration. Such a pod will never be evicted by a taint.

For example,
$ k get ds -n kube-system kube-proxy -oyaml
apiVersion: extensions/v1beta1
kind: DaemonSet
#snip
spec:
#snip
      tolerations:
      - effect: NoExecute
        operator: Exists
      - effect: NoSchedule
        operator: Exists

from csi-driver-host-path.

/help

from csi-driver-host-path.

@msau42:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

from csi-driver-host-path.

if we deploy it under kube-system, we may use system-node-critical priority class directly.

from csi-driver-host-path.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from csi-driver-host-path.

/remove-lifecycle stale

from csi-driver-host-path.

@pohly can we have generic resources limits of memory and cpu define for each yaml? or should i implement all resource limit of memory and cpu as default in yaml define in docs

from csi-driver-host-path.

What do you mean with "generic resource limits"?

I don't know what the recommended way of determining resource limits is. It probably implies running the pods and then measuring, but I don't know how or what.

from csi-driver-host-path.

@pohly here i would like to know that is that any criteria for defining resources for each pod, example for csi-hostpath-attacher pod , what would be the resource limit for cpu and memory.

from csi-driver-host-path.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from csi-driver-host-path.

/remove-lifecycle stale
/lifecycle frozen

from csi-driver-host-path.