#Hi, any update on https://github.com/NetApp/trident/issues/592?

1 messages · Page 1 of 1 (latest)

runic fable
#

We really like to be able to set resource Limits and requests for Trident pods.

frank spindle
#

I would suggest adding a comment to the issue to ask for an update.

solemn geyser
#

In addition to updating the Github with your request:
In case this is helpful...see below:

Customers can use the below options to set limits:

  1. Set default memory, cpu limits at trident namespace, so that pods with have the
    https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/
    https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace/
Kubernetes
Configure Default Memory Requests and Limits for a Namespace

Define a default memory resource limit for a namespace, so that every new Pod in that namespace has a memory resource limit configured.

Kubernetes
Configure Default CPU Requests and Limits for a Namespace

Define a default CPU resource limits for a namespace, so that every new Pod in that namespace has a CPU resource limit configured.

#
  1. Customer can use tridentctl to install and set the limits in custom yaml and modify as per need. (see item 3 below)

Above approaches would help them set the resources without any enhancement in trident.
If customer faces challenges/issues that trident pods consume more memory than expected, we can analyze to see if any fix is needed.