Describe the solution you'd like
A clear and concise description of what you want to happen.

The usage environment is k8s: 1.25.6 / trident 22.10 / ubuntu 20.04 LTS.
My entire environment has storage 8 nodes /110 worker nodes / 6000 LUNs in total and uses onap-san-economy.
I upgraded from 22.10 to 23.07 version.
After the upgrade, all LUN belonging to the vserver begin to appear as multipath devices on the server.
After this, since the number of LUN is large, the response of multipathd is also slowed, and the number of pods is large, resulting in many errors.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

I tested with the test environment provided by NetApp, and the same phenomenon occurs.

Additional context
Add any other context or screenshots about the feature request here.

https://kb.netapp.com/Cloud/Astra/Trident/Error_when_Pods_are_rescheduled_-_error_publishing_ontap-san_driver%3A_problem_mapping_LUN._attr%3A_LUN_already_mapped_to_initiator(s)_in_this_group

It is understood that the ontap-san-economy transitions to per-node-group from 23.07.
I don't know under what conditions it is transitioned to per-node-group.
In the test environment, we tested about 2 nodes and 3 pods,
I did not consistently switch to per-node-group when I tried various things such as server reboot/ pod, pvc deletion and reproduction, but eventually switched to per-node-group.
Since my environment is heavy, I need to quickly switch to per-node-group.
I need a good way to do an excellent upgrade.