-
Notifications
You must be signed in to change notification settings - Fork 245
Description
Hi,
We are running Trident CSI on an OpenShift cluster provisioning NFS volumes on a NetApp SVM that is integrated with Active Directory via LDAP, configured following the NetApp guide TR-4835 - How to configure LDAP in ONTAP.
The LDAP integration on the NetApp SVM side is verified and fully operational. Our next step is ensuring proper management of supplemental group memberships beyond the POSIX 16-group limit on NFS mounts provisioned through Trident.
From my review of the Trident documentation and backend configuration reference, I am unable to find any information regarding:
-
Whether Trident CSI supports or passes through LDAP Groups (supporting users belonging to more than 16 groups) when mounting NFS volumes via a NetApp SVM.
-
Whether any configuration options, flags, or annotations are needed on the Trident side to ensure LDAP integrations are supported for workloads accessing Trident-provisioned volumes.
-
Any impact or requirements relevant to Kubernetes, CSI, or the Trident driver when the ONTAP SVM is configured to use LDAP integrations.
-
If this is purely determined by ONTAP or the Kubernetes node’s NFS client, and Trident is not involved, that would also be valuable to clarify.
We appreciate any clarification or guidance on how Trident CSI supports or expects users to configure supplemental group management (--manage-gids or equivalent), particularly with LDAP integration and NFS in an OpenShift environment.
Thank you for your help!