You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
Trident 22.07 introduced the feature of per-node igroup for the ONTAP-SAN driver. We would like to have this feature for the ONTAP-SAN-ECONOMY driver
Describe alternatives you've considered
None
Additional context
We are using on-prem OpenShift 4.6.8 with CoreOS and the ONTAP-SAN-ECONOMY driver. We have reached a high number of PVs in the cluster - about 650+. Due to the way iscsid and multipathd work, each node need to scan all of its devices periodically and when creating a new device. And so, we hope that the per-node mapping of PVs with help us with the performance and scalability of hundreds of PVs per cluster (we are looking for this feature for performance reasons and not security reasons).
This is dark site environment with no internet connectivity so we are limited with log collection and screenshots.
Pasting from the release notes of 22.07:
"ONTAP-SAN volumes will now use per-node igroups and only map LUNs to igroups while actively published to those nodes to improve our security posture. Existing volumes will be opportunistically switched to the new igroup scheme when Trident determines it is safe to do so without impacting active workloads."
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
Trident 22.07 introduced the feature of per-node igroup for the ONTAP-SAN driver. We would like to have this feature for the ONTAP-SAN-ECONOMY driver
Describe alternatives you've considered
None
Additional context
We are using on-prem OpenShift 4.6.8 with CoreOS and the ONTAP-SAN-ECONOMY driver. We have reached a high number of PVs in the cluster - about 650+. Due to the way iscsid and multipathd work, each node need to scan all of its devices periodically and when creating a new device. And so, we hope that the per-node mapping of PVs with help us with the performance and scalability of hundreds of PVs per cluster (we are looking for this feature for performance reasons and not security reasons).
This is dark site environment with no internet connectivity so we are limited with log collection and screenshots.
Pasting from the release notes of 22.07:
"ONTAP-SAN volumes will now use per-node igroups and only map LUNs to igroups while actively published to those nodes to improve our security posture. Existing volumes will be opportunistically switched to the new igroup scheme when Trident determines it is safe to do so without impacting active workloads."
The text was updated successfully, but these errors were encountered: