●Change8

Migrating to Envoy v1.37.0

Version v1.37.0 introduces 3 breaking changes. This guide details how to update your code.

Released: 1/13/2026

3
Breaking Changes
4
Migration Steps
5
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

HTTP filterProto API Scrubberext_authzOpenTelemetry access logTCP proxy

Breaking Changes

●Issue #1

Default HTTP reset code changed from NO_ERROR to INTERNAL_ERROR. Consumers relying on NO_ERROR for HTTP resets must update their expectations.

●Issue #2

Reset behavior now ignores upstream protocol errors by default. Consumers needing to react to upstream protocol errors must configure this behavior explicitly.

●Issue #3

Proto API Scrubber now returns 404 Not Found instead of 403 Forbidden for blocked methods. Update authorization logic that expects 403.

Migration Steps

  1. 1
    If you rely on the default HTTP reset code being NO_ERROR, update your configuration or expectations to handle INTERNAL_ERROR.
  2. 2
    If you rely on upstream protocol errors triggering specific logic, ensure this logic is re-enabled as it is now ignored by default.
  3. 3
    Update OpenTelemetry access log configuration to use explicit 'http_service' or 'grpc_service' instead of the deprecated 'common_config' field.
  4. 4
    Update authorization logic that expects 403 Forbidden from Proto API Scrubber for blocked methods to expect 404 Not Found.

Release Summary

This release introduces significant expansion to the dynamic module ecosystem, adds new filters for network and request modification, and brings performance optimizations to HTTP/2 and resource utilization. Several breaking changes affect default reset behavior and API scrubber responses.

Need More Details?

View the full release notes and all changes for Envoy v1.37.0.

View Full Changelog