-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
3
-
None
-
None
-
CLOUD Sprint 281-tmp, CLOUD Sprint 282
Background
All controllers in OpenShift are expected to observe the cluster wide proxy configuration. For this, we will need to inject the expected env vars into deployments for the operands deployed by the capi-operator.
We can follow the patterns set out in Machine API operator for this, it will require updating any deployment/daemonset that comes in via an operand manifest configmap
Steps
- Review how cluster wide proxy is implemented for Machine API operator
- Implement cluster wide proxy injection in CAPI operator
- Ensure via E2E that the proxy configuration is observed correctly
- Ensure that any operand (container in a CAPx) has the correct Go env vars injected into the containers.
Stakeholders
- Cluster Infra
Definition of Done
- When configured, cluster wide proxy details should be injected into the pods created by deployment/daemonsets deployed by the CAPI operator
- Docs
- <Add docs requirements for this card>
- Testing
- <Explain testing that will be added>
- relates to
-
OCPBUGS-37297 [CAPI] Machine stuck in Pending status with http_proxy-no_privatelink cluster
-
- Closed
-