trident icon indicating copy to clipboard operation
trident copied to clipboard

No limits or requests set on Trident resources

Open cjreyn opened this issue 2 years ago • 4 comments

Describe the bug No limits or requests are set for any Trident pods except the operator pod. This is bad practice, as an issue in Trident could take down the cluster.

Environment Provide accurate information about the environment to help us reproduce the issue.

  • Trident version: 23.07
  • Trident installation flags used: none
  • Container runtime: containerd 1.6.6-3.1
  • Kubernetes version: 1.25.9
  • Kubernetes orchestrator: kubeadm
  • Kubernetes enabled feature gates: na
  • OS: RHEL8
  • NetApp backend types: ONTAP AFF
  • Other:

To Reproduce Install trident with the helm chart. Query the daemonset named "daemonset.apps/trident-node-linux" and all pods it starts. No sign of limits or requests.

Expected behavior The daemonset should set some sensible cpu, mem, and ephemeral storage limits and requests.

Additional context Add any other context about the problem here.

cjreyn avatar Aug 16 '23 12:08 cjreyn