Improvement of autoExportPolicy functionality with CustomExportClientIPs to support clusters behind a SNAT.

[nikos445]

Change description

• Improvement of autoExportPolicy to be able, to add custom Client IPs to SVM export policies, using a variable in TridentBackendConfig named customExportClientIPs

• Add missing code for ReconcileVolumeNodeAccess , for volume policies when backend updates

• Add extra variable enableCustomExportPolicySettings for enable/disable custom export policy settings (currently enables/disables only CustomExportClientIPs but may create more in future)

Project tracking

N/A

Do any added TODOs have an issue in the backlog?

N/A

Did you add unit tests? Why not?

No, I can't test it in my environment.

Does this code need functional testing?

Yes, someone from Netapp please implement proper testing. I tested all code manually.

Is a code review walkthrough needed? why or why not?

Yes, not an expert in Netapp Trident Operator, but did my best to follow patterns based on existing code.

Should additional test coverage be executed in addition to pre-merge?

Does this code need a note in the changelog?

Yes

Does this code require documentation changes?

Yes

Additional Information

Related Issue: https://github.com/NetApp/trident/issues/1048