When NSX Manager is behind HTTPS proxy, NSX config fails to be applied

[rvanderp3]

When NSX Manager is behind HTTPS proxy, NSX config fails to be applied.

Environment

• Red Hat OpenShift Container Platform 4.7.2
• nsx-container-plugin-operator-3.1.1.17559186

Description
In the environment in which I am attempting to deploy the nsx-container-plugin-operator the NSX manager API is only accessible via an HTTPS proxy. As a result, the nsx-ncp deployment can't interact with the NSX manager API.

Workaround
In order to provide a proxy to the nsx-ncp deployment, the HTTP(S)_PROXY and NO_PROXY variables need to manually added to the nsx-ncp deployment.

Suggested Change
OpenShift provides a clusterproxy resource[https://docs.openshift.com/container-platform/4.7/networking/enable-cluster-wide-proxy.html] which is intended to be consumed by operators for inclusion in applicable deployments.

[salv-orlando]

Thanks for bringing up this issue.
You are right, this is a use case we did not consider so far.

While clusterproxy seems an obvious choice, we need to keep in mind that this operator can also be leverage in vanilla K8S environment, hence I'd lean towards providing proxy info as ENV variables to the operator deployment