Describe the bug
Istio control plane and sidecars have options for configuring log verbosity level but are not exposed as something configurable via helm. Also control plane log level requires scope:level and some references in the charts still refer to just a level format.
Gateways include incorrect --log_output_level info example in helm charts:
https://github.com/istio/istio/blob/release-1.1/install/kubernetes/helm/istio/charts/gateways/templates/deployment.yaml#L105
Expected behavior
To be able to configure istio control plane and sidecar proxy log levels via helm.
Envoy proxy instances have --proxyLogLevel trace|debug|info|warning|error|critical|off
Control plane components have different scopes depending on component, but expect to at least be able to configure default log level, i.e. --log_output_level default:warn
Describe the bug
Istio control plane and sidecars have options for configuring log verbosity level but are not exposed as something configurable via helm. Also control plane log level requires
scope:leveland some references in the charts still refer to just alevelformat.Gateways include incorrect
--log_output_level infoexample in helm charts:https://github.com/istio/istio/blob/release-1.1/install/kubernetes/helm/istio/charts/gateways/templates/deployment.yaml#L105
Expected behavior
To be able to configure istio control plane and sidecar proxy log levels via helm.
Envoy proxy instances have
--proxyLogLevel trace|debug|info|warning|error|critical|offControl plane components have different scopes depending on component, but expect to at least be able to configure default log level, i.e.
--log_output_level default:warn