1.30.0 (Pending)

Incompatible behavior changes

Changes that are expected to cause an incompatibility if applicable; deployment changes are likely required

  • http: Remove the hop by hop TE header from downstream request headers if it’s not set to trailers, else keep it. This change can be temporarily reverted by setting envoy.reloadable_features.sanitize_te to false.

  • stats: The runtime flag envoy.reloadable_features.enable_include_histograms is now enabled by default. This causes the includeHistogram() method on Stats::SinkPredicates to filter histograms to be flushed to stat sinks.

Minor behavior changes

Changes that may cause incompatibilities for some users, but should not for most

  • QUIC: Port migration is default turned off. QUIC client connections will no longer attempt to migrate to a new port when connections is degrading. Can be manually turned on via port_migration.

  • adaptive concurrency filter stats: Multiply the gradient value stat by 1000 to make it more granular (values will range between 500 and 2000).

  • aws: AWS region string is now retrieved from environment and profile consistently within aws_request_signer and grpc_credentials/aws_iam extensions. Region field in aws_request_signer is now optional, explicitly configured xDS region will take preference. aws_request_signer documentation now reflects the region chain.

  • dns: Allowing <envoy_v3_api_field_extensions.common.dynamic_forward_proxy.v3.DnsCacheConfig.dns_min_refresh_rate>` to go as low as 1s.

  • golang: Change RegisterHttpFilterConfigFactoryAndParser to RegisterHttpFilterFactoryAndConfigParser.

  • http: Enable obsolete line folding in BalsaParser (for behavior parity with http-parser, the previously used HTTP/1 parser).

  • quic: Server preferred address is now sent to non-quiche quic clients when configured. This behavior can be disabled with runtime flag envoy.reloadable_features.quic_send_server_preferred_address_to_all_clients.

  • upstream: Upstream now excludes hosts set to DRAINING state via EDS from load balancing and panic routing threshold calculation. This feature can be disabled by setting envoy.reloadable_features.exclude_host_in_eds_status_draining to false.

Bug fixes

Changes expected to improve the state of the world and are unlikely to have negative effects

  • UDP and TCP tunneling: fixed a bug where second HTTP response headers received would cause Envoy to crash in cases where propagate_response_headers and retry configurations are enabled at the same time, and an upstream request is retried multiple times.

  • deps: Updated QUICHE dependencies to incorporate fixes for https://github.com/envoyproxy/envoy/issues/32401.

  • http: Fixed crash when HTTP request idle and per try timeouts occurs within backoff interval.

  • jwt_authn: Fixed JWT extractor, which concatenated headers with a comma, resultig in invalid tokens.

  • load balancing: Added randomization in host load-balancing initialization. This helps desynchronizing Envoys across a fleet by randomizing the scheduler starting point. This can be temporarily reverted by setting runtime guard envoy.reloadable_features.edf_lb_host_scheduler_init_fix to false.

  • load balancing: Added randomization in locality load-balancing initialization. This helps desynchronizing Envoys across a fleet by randomizing the scheduler starting point. This can be temporarily reverted by setting runtime guard envoy.reloadable_features.edf_lb_locality_scheduler_init_fix to false.

  • proxy protocol: Fixed a crash when Envoy is configured for PROXY protocol on both a listener and cluster, and the listener receives a PROXY protocol header with address type LOCAL (typically used for health checks).

  • proxy_protocol: Fix crash due to uncaught exception when the operating system does not support an address type (such as IPv6) that is received in a proxy protocol header. Connections will instead be dropped/reset.

  • proxy_protocol: Fixed a bug where TLVs with non utf8 characters were inserted as protobuf values into filter metadata circumventing ext_authz checks when failure_mode_allow is set to true.

  • router: Fix a timing issue when upstream requests are empty when decoding data and send local reply when that happends. This is controlled by envoy_reloadable_features_send_local_reply_when_no_buffer_and_upstream_request.

  • stateful_session: Support 0 TTL for proto-encoded cookies, which disables cookie expiration by Envoy.

  • tcp_proxy: When tunneling TCP over HTTP, closed the downstream connection (for writing only) when upstream trailers are read to support half close semantics during TCP tunneling. This behavioral change can be temporarily reverted by setting runtime guard envoy.reloadable_features.tcp_tunneling_send_downstream_fin_on_upstream_trailers to false.

  • tls: Fix crash due to uncaught exception when the operating system does not support an address type (such as IPv6) that is received in an mTLS client cert IP SAN. These SANs will be ignored. This applies only when using formatter %DOWNSTREAM_PEER_IP_SAN%.

  • tracers: use unary RPC calls for OpenTelemetry trace exports, rather than client-side streaming connections.

  • tracing: Dynatrace resource detector: Only log warning message when no enrichment attributes are found.

  • tracing: Prevent Envoy from crashing at start up when the OpenTelemetry environment resource detector cannot detect any attributes.

  • url matching: Fixed excessive CPU utilization when using regex URL template matcher.

  • xds: Reject xDS configurations where the rate-limit’s fill_rate is set to Infinity or NaN.

Removed config or runtime

Normally occurs at the end of the deprecation period

  • active health check: Removed envoy.reloadable_features.keep_endpoint_active_hc_status_on_locality_update runtime flag and legacy code paths.

  • aws: Removed envoy.reloadable_features.enable_aws_credentials_file runtime flag and legacy code paths.

  • http: Removed envoy.reloadable_features.allow_absolute_url_with_mixed_scheme runtime flag and legacy code paths.

  • http: Removed envoy_reloadable_features_append_xfh_idempotent runtime flag and legacy code paths.

  • http1: Removed envoy.reloadable_features.http1_allow_codec_error_response_after_1xx_headers runtime flag and legacy code paths.

  • overload manager: removed envoy.reloadable_features.overload_manager_error_unknown_action and legacy code paths.

  • resource_monitors: removed envoy.reloadable_features.count_unused_mapped_pages_as_free runtime flag and legacy code paths.

  • upstream: removed envoy_reloadable_features_initialize_upstream_filters and legacy code paths.

New features

  • access log: added support for %UPSTREAM_CONNECTION_ID% for the upstream connection identifier.

  • access_loggers: Added Fluentd access logger to support flushing access logs in Fluentd format.

  • aws_lambda: Added host_rewrite config to be used during signature.

  • aws_lambda: Update aws_lambda filter to support use as an upstream HTTP filter. This allows successful calculation of signatures after the forwarding stage has completed, particularly if the path element is modified.

  • aws_request_signing: Update aws_request_signing filter to support use as an upstream HTTP filter. This allows successful calculation of signatures after the forwarding stage has completed, particularly if the path element is modified.

  • ext_proc: added metadata_options config API to enable sending and receiving metadata from/to the external processing server. Both typed and untyped dynamic metadata may be sent to the server. If receiving_namespaces is defined, returned metadata may be written to the specified allowed namespaces.

  • ext_proc: implemented request_attributes and response_attributes config APIs to enable sending and receiving attributes to/from the external processing server.

  • grpc reverse bridge: Change HTTP status to 200 to respect the gRPC protocol. This may cause problems for incorrect gRPC clients expecting the filter to preserve HTTP 1.1 responses. This behavioral change can be temporarily reverted by setting runtime guard envoy.reloadable_features.grpc_http1_reverse_bridge_change_http_status to false.

  • monitoring: Add Envoy::ExecutionContext, which is notified by ScopeTrackerScopeState’s constructor and destructor. This feature is disabled by default, it can be enabled by runtime feature flag envoy.restart_features.enable_execution_context. For more details, please see https://github.com/envoyproxy/envoy/issues/32012.

  • quic: Added QUIC protocol option send_disable_active_migration to make the server send clients a transport parameter to discourage client endpoints from active migration.

  • rbac: Added uri_template which uses existing UriTemplateMatchConfig to allow use of glob patterns for URI path matching in RBAC.

  • redis: Added support for the ECHO command.

  • tcp_proxy: added an option to dynamically set a per downstream connection idle timeout period object under the key envoy.tcp_proxy.per_connection_idle_timeout_ms. If this filter state value exists, it will override the idle timeout specified in the filter configuration and the default idle timeout.

  • upstream: Added selection_method option to the least request load balancer. If set to FULL_SCAN, Envoy will select the host with the fewest active requests from the entire host set rather than choice_count random choices.

  • wasm: added verify_signature foreign function to verify cryptographic signatures.

Deprecated