Trident for Kubernetes/Openshift until 20.01
ontap-nas-economyfrom two Trident using Kubernetes or Openshift clusters on the same SVM, the base volume on which such a PV is created may have the export from the other cluster, causing "
access denied" errors in the created pod.
For example, the SVM has two volumes created through ontap-nas-ecnomy, with one cluster having the export of one and one having the export of the other:
trident_qtree_pool_trident_XGNOGQKASX, exported with policy ClusterA
trident_qtree_pool_trident_ZGKVFHAMCS, exported with policy ClusterB
The new PV created by Trident for Cluster A is created as a QTree with quotas on
trident_qtree_pool_trident_ZGKVFHAMCSwith its own
Since the export goes through the root export of the volume, exported to
ClusterBonly, access from Cluster A nodes is denied.