CU want to setup environment variables for proxy in the keda-operator, however some problems when using proxy settings in the custom-metrics-autoscaler-operator pod is getting the proxy settings as expected, but "custom-metrics-autoscaler-operator" pod will also create "keda-operator".

The proxy settings will not be propagated  on the "keda-operator" pod.

Current workaround is:

Set max-pods for "custom-metrics-autoscaler-operator" to 0

Set proxy configuration to the deployment of the keda-operator.

The problem is, that the custom-metrics-autoscaler-operator needs to be placed to 0 otherwise he will overwrite the configuration of the keda-operator.