Skip to content

feat: bump Envoy Gateway to v1.7.0#4534

Draft
electricjesus wants to merge 1 commit intomasterfrom
seth/bump-envoy-gateway-1.7.0
Draft

feat: bump Envoy Gateway to v1.7.0#4534
electricjesus wants to merge 1 commit intomasterfrom
seth/bump-envoy-gateway-1.7.0

Conversation

@electricjesus
Copy link
Member

@electricjesus electricjesus commented Mar 12, 2026

Summary

  • Bumps Envoy Gateway from v1.5.x to v1.7.0 (v1.5 is EOL as of 2026/02/13)
  • Regenerates gateway_api_resources.yaml from updated helm chart
  • Adapts to upstream API breaking changes:
    • ProviderTypeKubernetesEnvoyProxyProviderTypeKubernetes
    • ProxyAccessLogFormat.Type changed from string to *ProxyAccessLogFormatType
    • Gateway API CRD count: 11 → 12
  • Updates go.mod dependencies accordingly

Context

Envoy Gateway v1.5 reached EOL on 2026/02/13. Per the compatibility matrix, v1.7.0 requires:

  • Envoy Proxy: v1.37.0
  • Gateway API: v1.4.1
  • Kubernetes: v1.32–v1.35

Companion PR: https://github.com/tigera/calico-private/pull/11090

Breaking changes between EG 1.5 → 1.7

See release notes for v1.6 and v1.7. Key items:

  • ALPN defaults to [h2, http/1.1] for backend TLS
  • Upstream TLS SNI auto-determined from Host header
  • custom_response filter reordered to execute first
  • Invalid HTTPRoute/GRPCRoute filters now return 500

Test plan

  • CI passes (build + unit tests)
  • Gateway API controller tests pass (verified locally: 13/13)
  • Review gateway_api_resources.yaml diffs for new RBAC requirements
  • Companion calico-private PR builds images successfully
  • E2E gateway tests pass on a test cluster

Update Envoy Gateway dependency to v1.7.0 and regenerate gateway API
resources. Adapts to upstream API changes:
- ProviderTypeKubernetes renamed to EnvoyProxyProviderTypeKubernetes
- ProxyAccessLogFormat.Type changed from string to pointer type
- Gateway API CRD count increased from 11 to 12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants