-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
-
False
-
Supports injecting custom CA certificates and also detects cluster wide egress proxy configuration to configure the operator and the operand with HTTP_PROXY, HTTPS_PROXY and NO_PROXY.
Cross-posted: https://github.com/openshift/cert-manager-operator/issues/72
This is a blocker for deploying to 1500+ sites at a customer.
As it is, the cert-manager operator does not inject the needed cluster proxy and custom root CA configuration into the running Pods.
You can inject the environmental variables for HTTP_PROXY, HTTPS_PROXY, and NO_PROXY into the operator Subscription, which will apply them to the controller, but the controller does not pass them to the Deployments that are created by the CertManager instance.
This is useful in case a cluster is behind an outbound proxy and needs to communicate with an ACME server on the internet, such as the Sectigo OV ACME server.
- relates to
-
CM-33 cert-manager operator GA
- Closed
- links to