Skip to main content
NetApp Knowledge Base

Is it possible to set priorityClassName for Trident pods when installing via Helm?

  1. Last updated
  2. Save as PDF
Views:
19
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • Trident
  • Helm installation

Answer

No, it is not possible to set priorityClassName for Trident pods when installing via Helm.

Notes:

  • From Trident 22.07 onwards, the trident-node-linux and trident-node-windows DaemonSets have priorityClassName: system-node-critical set by default.
  • The trident-controller and trident-operator Deployments do not have priorityClassName set by default.
  • The priorityClassName for the trident-controller and trident-operator Deployments can be set using the following commands after the installation:
    • kubectl patch deployment -n trident trident-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/priorityClassName", "value": "system-node-critical"}]'
    • kubectl patch deployment -n trident trident-operator --type='json' -p='[{"op": "add", "path": "/spec/template/spec/priorityClassName", "value": "system-node-critical"}] 

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.