vmware / vmware/nsx-container-plugin-operator
When NSX Manager is behind HTTPS proxy, NSX config fails to be applied
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 34
- Forks
- 28
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting how the operator creates and updates the nsx-ncp deployment, then review the OpenShift clusterproxy resource documentation linked in the issue. Done means the deployment receives the required HTTP(S)_PROXY and NO_PROXY settings automatically when NSX Manager is reachable only through an HTTPS proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100