Skip to main content
NetApp Knowledge Base

Why does Trident still use PodSecurityPolicy after Kubernetes has deprecated it ?

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

Applies to

  • Trident 21.04 and 21.07
  • Astra Trident 21.10 and higher
  • Kubernetes 1.21 and higher

Answer

The main reason it's still there is backwards compatibility with Kubernetes versions older than 1.21, specifically to still support 1.17.
As long as Trident cannot support 1.25 yet (i.e. until its release), leaving in this compatibility covers more ground.

Additional Information

See Trident Github issue #661 for more information on upcoming changes.
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.