Skip to main content
NetApp Stage KB

Trident 22.04 Helm installation limits certain adjustments to the setup

Views:
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
SNAPX
Last Updated:

Applies to

Trident for Kubernetes and Openshift  until 22.04

Issue

  • When using a private repository, in certain environments the developers want to re-tag the used container images. For csi-node-driver-registrar:v2.4.0, in a helm or operator based installation, this is not possible, due to using this particular container reference, instead of name and tag separately.
  • In some environments, the containers need to have additional resource definitions to limit certain usage (like CPU). The operator image, however, is missing a resources definition which could be extended.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.
Case Citation
32cf497d-4953-43ed-a9c9-ae84e147020f