Configuration of Control Plane via Helm values.yml or ConfigMap?

[BernH4]

Configuring the logging level for the Control Plane is explained in the "Install with Helm" section of the documentation, and I can clearly see the relevant parameter in the values.tmpl.yaml.

I would expect that all Control Plane configurations should be done via Helm values. However, when reading through the Gateway Observability section of the docs, the examples for enabling the OpenTelemetry sink and disabling Prometheus metrics rely on editing the ConfigMap installed by default, rather than setting Helm values.

This raises two questions:
Persistence: As far as I know, editing the ConfigMap directly is not persistent, the default configuration will return if the control plane restarts. How can I make this configuration persistent?
If I define my own ConfigMap that is applied via Flux/ArgoCD, won't this create some kind of inconsistency during updates? (e.g., Helm updates envoy gateway and restores the default ConfigMap, overwriting mine, causing Flux to detect drift and overwrite it back).

Helm Support: I assumed I could configure these settings persistently via values.yaml, but I cannot find any parameters corresponding to OpenTelemetry or Prometheus metrics in the values.tmpl.yaml.

Thanks!

I also wanted to mention that I evaluated the setup experience with Kong, Traefik and Envoy Gateway and I found Envoy Gateway to be the easiest to configure by far, one reason being the high quality documentation. Thanks for that!

[arkodg]

you should be able to set the same values in

gateway/charts/gateway-helm/values.tmpl.yaml

Line 102 in 5da2aac

envoyGateway:

[BernH4]

@arkodg Thank you!
Is there a reason the documentation explains the other approach, editing the config map directly? My guess would be that it is independent of the installation method used, e.g., not using Helm and installing with Kubernetes YAML.

[arkodg]

cant think of reason to not add it, feel free to add the helm upgrade option in the docs