Update Envoy Gateway to v1.9.3
What does this MR do?
Update the bundled Envoy Gateway from v1.9.2 to v1.9.3 and default its Envoy Proxy image to docker.io/envoyproxy/envoy:distroless-v1.39.6, for the eMudhra intermediate CA compromise (CVE-2026-111943).
- Envoy Gateway v1.9.3 ships Envoy v1.39.5 and fixes CVE-2026-35189 and the
golang.org/x/netHTTP/2 CVEs. Its breaking changes section is empty. - The default
distroless-v1.39.5Envoy Proxy image still trusts the compromised CAs. Upstream's remediation is to override the image todistroless-v1.39.6, see Upgrading Envoy Proxy to v1.39.6. - The chart attaches its own
EnvoyProxyto the GatewayClass without amergeType, so the gateway-helmglobal.images.envoyProxy.imagedefault does not apply to it.templates/envoy/proxy.yamltherefore sets the image on the Deployment or DaemonSet of thatEnvoyProxy, when the bundled Envoy Gateway is installed (global.gatewayApi.installEnvoy) andgatewayApiResources.envoy.proxySpecsets neithercontainer.imagenorcontainer.imageRepository. An externally managed Envoy Gateway keeps its own default. - The EnvoyProxy CRD accepts only one of
imageandimageRepository, so aproxySpecthat setsimageRepositoryfor a mirror is left unchanged. The chart then prints a warning in the NOTES, because Envoy Gateway uses its default tag with that repository, which still trusts the compromised CAs. - A new Envoy Proxy image section in
doc/advanced/gateway-api/_index.mdexplains which image the chart sets and how to set the patched image for a mirror withcontainer.image. - The
gateway-crds-helmversion in the docs moves to v1.9.3. This supersedes the docs-only Renovate MR !5538 (closed).
helm template with the CI default settings and Gateway API enabled renders the same objects as before, apart from the Envoy Gateway image tags and the new EnvoyProxy image. spec/configuration/gatewayapi_spec.rb passes (94 examples), with new examples for the default, DaemonSet, explicit image, image repository and externally managed cases.
Related issues
Related to https://gitlab.com/gitlab-org/charts/gitlab/-/issues/6741
Related https://gitlab.com/gitlab-org/release/tasks/-/work_items/28133+s
Author checklist
For general guidance, please follow our Contributing guide.
Required
For anything in this list which will not be completed, please provide a reason in the MR discussion.
- Merge Request Title and Description are up to date, accurate, and descriptive.
- MR targeting the appropriate branch.
- MR has a green pipeline.
- Documentation created/updated. (Envoy Proxy image section,
gateway-crds-helmversion references) - Tests added/updated.
- Have you validated that your change works end-to-end on a real cluster deployment?
- Describe how you did it in a comment.
- Equivalent MR/issue for omnibus-gitlab opened. (N/A: chart dependency only)
- When ready for review, MR is marked as ready (not a draft) and assigned to a reviewer.
Reviewers checklist
- As soon as you begin reviewing, select Start a review on your first comment so the MR shows Reviewer started review.
- MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab.
- Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab chart.