Backport: Update Envoy Gateway to v1.9.3 (10.5)

What does this MR do?

Backport !5540 (merged) to GitLab chart 10.5 (GitLab 19.5): 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).

The default distroless-v1.39.5 Envoy Proxy image of v1.9.3 still trusts the compromised CAs, so this follows upstream's remediation, Upgrading Envoy Proxy to v1.39.6. The image is set on the chart's EnvoyProxy only when the bundled Envoy Gateway is installed and gatewayApiResources.envoy.proxySpec sets neither container.image nor container.imageRepository; an externally managed Envoy Gateway keeps its own default.

The EnvoyProxy CRD accepts only one of image and imageRepository, so a proxySpec that sets imageRepository for a mirror is left unchanged, and the chart prints a warning in the NOTES that Envoy Gateway's default tag still trusts the compromised CAs. A new Envoy Proxy image section in doc/advanced/gateway-api/_index.md explains how to set the patched image for a mirror with container.image.

Envoy Gateway v1.9.3 has no breaking changes. helm template with the CI default settings and Gateway API enabled renders the same objects as before, apart from the image tags. spec/configuration/gatewayapi_spec.rb passes (87 examples).

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-helm version 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

🤖 Generated with Claude Code

Edited by Clemens Beck

Merge request reports

Loading
Loading