Hi Team, In our Kubernetes (K8s) environment, each application team is assigned their own namespace, and they deploy their own pods within it. While testing the NetApp Trident integration, we observed the following and would appreciate your feedback on how we can address these concerns: Tenant A provisions a PersistentVolumeClaim (PVC) named pvc1. How does the system ensure that Tenant B cannot access pvc1 or its underlying PersistentVolume (PV)? What security mechanisms are in place (e.g., namespace isolation, RBAC, storage-level encryption, etc.) to enforce tenant isolation and prevent unauthorized access? Are there any best practices to enhance security in a multi-tenant Kubernetes environment using NetApp Trident?   In our current setup, PVCs are namespace-scoped, and each application team has access only to their respective namespace. Looking forward to your input. Thanks ... View more

VDI and PC Cloud need to be storage on super speed and strong storage system. How we can speed the adoption to use super fast Virtual Machine to deploy a Desktop on premise and Cloud Services. ... View more

test post ... View more