1.26.0 (Pending)

Minor behavior changes

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

  • healthcheck: If active HC is enabled and a host is ejected by outlier detection, a successful active health check unejects the host and consider it healthy. This also clears all the outlier detection counters. This behavior change can be reverted by setting envoy.reloadable_features_successful_active_health_check_uneject_host to false.

  • quic: Access logging is now deferred to the QUIC ack listener, and roundtrip response time is added as a downstream timing metric. New runtime flag envoy.reloadable_features.quic_defer_logging_to_ack_listener can be used for revert this behavior.

Bug fixes

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

  • eds: added envoy.reloadable_features.multiplex_eds to disable eds multiplexing. Eds multiplexing is enabled by default, so that all subscriptions for the same resource type and management server reuse a single channel/mux. When eds multiplexing is disabled each subscription uses a dedicated channel/mux.

  • router: fixed the bug that custom tags of the route metadata type are not set for upstream spans.

  • stats: now updating upstream total connection stats as happy eyeballs connections are created.

Removed config or runtime

Normally occurs at the end of the deprecation period

  • config: removed envoy.reloadable_features.combine_sds_requests and legacy code paths.

  • dns: removed envoy.reloadable_features.dns_multiple_addresses runtime flag and legacy code paths.

  • http: removed envoy.reloadable_features.allow_concurrency_for_alpn_pool and legacy code path.

  • http: removed envoy.reloadable_features.http2_delay_keepalive_timeout and legacy code paths.

  • http: removed envoy.reloadable_features.local_ratelimit_match_all_descriptors and legacy code paths.

  • http: removed envoy.reloadable_features.use_rfc_connect and legacy code path.

  • router: removed envoy.reloadable_features.get_route_config_factory_by_type runtime flag. The flag is no longer needed as the behavior is now the default.

New features