Description

Use thread safe way to handle custom HTTP headers from gopowerstore.

GitHub Issues

Checklist:

• I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
• I have verified that new and existing unit tests pass locally with my changes
• I have not allowed coverage numbers to degenerate
• I have maintained at least 90% code coverage
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• Backward compatibility is not broken

How Has This Been Tested?

1. Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration
   Unit tests

ok      github.com/dell/csi-powerstore/v2/pkg/array     1.268s  coverage: 93.2% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/common    3.339s  coverage: 96.1% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/common/fs 1.324s  coverage: 90.6% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/common/k8sutils   2.658s  coverage: 90.8% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/controller        2.707s  coverage: 90.7% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/identity  1.187s  coverage: 100.0% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/interceptors      4.018s  coverage: 90.1% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/node      4.282s  coverage: 90.2% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/provider  1.257s  coverage: 100.0% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/service   1.304s  coverage: 95.3% of statements
ok      github.com/dell/csi-powerstore/v2/pkg/tracer    1.202s  coverage: 100.0% of statements

2. Ran shared NFS and iSCSI provisioning of volumes to the order of about 400 volumes, using cert-csi (test scaling). Verified there are no controller pod crashes. In the past, about 100+ would often panic the controller pod.
3. Ran provisioning on OCP and K8S clusters.