What would you like to be added:
The gardenervali allows to set a ProxyURL config key in environments where a HTTP(S) Proxy needs to be used. Checking the code, there is a config map key HTTPProxy
|
"HTTPProxy", "httpProxy", "http_proxy", |
which would allow to set the proxy but it does not seem to be wired. My understanding is that the only way to currently set a HTTP Proxy is through the
HTTP_PROXY environment variable to the fluent-bit container (
https://docs.fluentbit.io/manual/administration/http-proxy)
Why is this needed:
Fluent-bit is deployed via a ManagedResource and does not seem to be configurable, so there is no way to set the HTTP_PROXY env variable of the container. The env vars are hardcoded in the respective observability component of gardener. Therefore logs cannot be sent to endpoints in an environment where a HTTP Proxy is required.
Depending on the upstream needs/feedback, it should either be possible to inject the environment variable to the container or to add a wiring of the HTTPProxy field from the output config. I’m happy to contribute, I wanted to check the direction first in case you'd prefer the env-var-injection route on the gardener side, or already have this planned.
What would you like to be added:
The
gardenervaliallows to set aProxyURLconfig key in environments where a HTTP(S) Proxy needs to be used. Checking the code, there is a config map keyHTTPProxylogging/cmd/fluent-bit-output-plugin/plugin_config.go
Line 108 in a19bfae
HTTP_PROXYenvironment variable to the fluent-bit container (https://docs.fluentbit.io/manual/administration/http-proxy)Why is this needed:
Fluent-bit is deployed via a ManagedResource and does not seem to be configurable, so there is no way to set the
HTTP_PROXYenv variable of the container. The env vars are hardcoded in the respective observability component ofgardener. Therefore logs cannot be sent to endpoints in an environment where a HTTP Proxy is required.Depending on the upstream needs/feedback, it should either be possible to inject the environment variable to the container or to add a wiring of the HTTPProxy field from the output config. I’m happy to contribute, I wanted to check the direction first in case you'd prefer the env-var-injection route on the gardener side, or already have this planned.