Skip to main content
NetApp Knowledge Base

K8S PSP getting created after setting excludePodSecurityPolicy to true

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

Applies to

Kubernetes version to 1.24 and below

Answer

Kubernetes clusters can be upgraded with objects of removed APIs.
After the upgrade, each is handled in its own way.
Usually they are served by a newer API, but because PodSecurityPolicy (PSP) were removed completely, they effectively disappear from the cluster.
Helm has a bug where charts that contain removed APIs cannot be upgraded or uninstalled

Additional Information

The Trident chart creates PSP -`tridentoperatorpods`, trident-node-linux and trident-controller . The tridentoperatorpods psp must be removed from the chart before it can be upgraded or uninstalled in a v1.25 or above cluster (if the cluster is upgraded without removing the PSP from the chart, the PSP must be removed from the chart manually using the steps here).
The`excludePodSecurityPolicy` value can be used to remove tridentoperatorpods PSP from the chart before upgrading the cluster so that the Trident chart can be upgraded or uninstalled after upgrading the cluster, but does not remove trident-node-linux and trident-controller psps.
The Trident operator detects the Kubernetes version and does not attempt to recreate PSPs if the version is greater than or equal to v1.25.0.
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.