Skip to main content
NetApp Knowledge Base

NetApp Trident, Red Hat OpenShift CSI and private registry FAQs

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

Applies to

  • NetApp Trident
  • Red Hat OpenShift CSI

Answer

  • Q.  Which Kubernetes cluster architectures are officially supported by NetApp Trident?A.Supported Kubernetes cluster architecturesTrident is supported with the following Kubernetes architectures:Kubernetes cluster architecturesSupportedDefault installSingle master, computeYesYesMultiple master, computeYesYesMaster, etcd, computeYesYesMaster, infrastructure, computeYesYes Q.  If access to https://docker.io is prohibited in my environment, how would a private registry be used to perform Trident updates?
  • A.  Follow the steps in one of the below articles for the method that was / will be used to deploy Trident:Manually deploy the Trident operator (Offline mode)Deploy Trident operator using Helm (Offline mode)Install using tridentctl
  • Q.  What is the correct procedure to uninstall the Netapp Trident installed via the Operator Hub if I want to try out other installation options like Helm?
  • A.  See "Uninstall Trident Operator" in Install Trident using OpenShift OperatorHub
  • Q.  If Trident pulls update images from Docker.io, and the Docker Hub user is Personal (authenticated) or Unauthenticated, does Trident have a way to circumvent Docker rate limit errors?
  • A.  No, Trident doesn’t have any way to avoid the rate limit errors you are referring to, besides using a private image registry.
  • Q.  Is it mandatory to specify the following parameters in the Trident backend configuration if SVMDR is in use?
    • SVM data LIF
    • SVM name
  • A.  The SVM management LIF is mandatory, but the data LIF varies depending on the driver used:
    • ONTAP SAN
      • Do not specify for iSCSI. Trident uses ONTAP Selective LUN Map to discover the iSCI LIFs needed to establish a multi path session. A warning is generated if dataLIF is explicitly defined. Refer to ONTAP SAN configuration options and examples for details.
    • ONTAP NAS
      • NetApp recommends specifying dataLIF. If not provided, Trident fetches dataLIFs from the SVM. You can specify a fully-qualified domain name (FQDN) to be used for the NFS mount operations, allowing you to create a round-robin DNS to load-balance across multiple dataLIFs. Refer to ONTAP NAS configuration options and examples for details
  • A.  The SVM name is derived if an SVM management LIF is specified
  • Q.  Is it mandatory to specify the following mountOptions parameters in the Trident Storage Class?
    • nfsvers
    • nolock
  • A.  This is dependent on the specific environment:
    • nfsvers - Specifies which version of the NFS protocol to use. This is useful for hosts that run multiple NFS versions. If no version is specified, NFS uses the highest supported version by the kernel and mount command. This option is not supported with NFSv4 and should not be used.
    • nolock - Disables file locking. This setting is occasionally required when connecting to older NFS servers.
  • Q.  Are NFS mount options with Kerberos authentication supported when using OpenShift with NetApp Trident?
  • A.  Trident supports Kerberos encryption over NFSv3 and NFSv4 connections from Red Hat OpenShift and upstream Kubernetes clusters to on-premise ONTAP volumes.
  • Q.  Does enabling encryption cause any adverse side effects like increased latency or others to worry about?
  • A.  No, enabling encryption will not have any adverse side effects.
  • Q.  Can a custom export policy be created with the following parameters?
    • enableForceDetach = true
    • autoExportPolicy = false
  • A.  Yes, however a custom export policy with enableForceDetach = true and autoExportPolicy = false, can only be used if the backend is using the ontap-san or ontap-san-economy driver.

Additional Information

N/A
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.