Skip to main content
NetApp Knowledge Base

Trident and Capsule compatibility

  1. Last updated
  2. Save as PDF
Views:
26
Visibility:
Public
Votes:
0
Category:
astra
Specialty:
snapx
Last Updated:

Applies to

  • Trident
  • Capsule managed Kubernetes Cluster

Issue

Trident namespace label enforcement makes it incompatible with Capsule k8s multi-tenant framework;
Upon installing and at every reconcile, Trident Operator checks if the trident installation namespace already exists.
If the namespace already exists, trident operator tries to patch the namespace with the label pod-security.kubernetes.io/enforce: privileged, even if it already exists. 
Capsule denies the request as the trident-operator service account isn't a tenant owner.
Trident treats namespace errors as fatal, so you currently cannot install trident on a cluster running Capsule.

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.