Skip to content

Latest commit

 

History

History
69 lines (59 loc) · 8.5 KB

current.rst

File metadata and controls

69 lines (59 loc) · 8.5 KB

1.21.0 (Pending)

Incompatible Behavior Changes

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

  • xds: * became a reserved name for a wildcard resource that can be subscribed to and unsubscribed from at any time. This is a requirement for implementing the on-demand xDSes (like on-demand CDS) that can subscribe to specific resources next to their wildcard subscription. If such xDS is subscribed to both wildcard resource and to other specific resource, then in stream reconnection scenario, the xDS will not send an empty initial request, but a request containing * for wildcard subscription and the rest of the resources the xDS is subscribed to. If the xDS is only subscribed to wildcard resource, it will try to send a legacy wildcard request. This behavior implements the recent changes in :ref:`xDS protocol <xds_protocol>` and can be temporarily reverted by setting the envoy.restart_features.explicit_wildcard_resource runtime guard to false.

Minor Behavior Changes

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

  • config: the log message for "gRPC config stream closed" now uses the most recent error message, and reports seconds instead of milliseconds for how long the most recent status has been received.
  • dns: now respecting the returned DNS TTL for resolved hosts, rather than always relying on the hard-coded :ref:`dns_refresh_rate. <envoy_v3_api_field_config.cluster.v3.Cluster.dns_refresh_rate>` This behavior can be temporarily reverted by setting the runtime guard envoy.reloadable_features.use_dns_ttl to false.
  • listener: destroy per network filter chain stats when a network filter chain is removed during the listener in place update.

Bug Fixes

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

Removed Config or Runtime

Normally occurs at the end of the :ref:`deprecation period <deprecated>`

  • compression: removed envoy.reloadable_features.enable_compression_without_content_length_header runtime guard and legacy code paths.
  • health check: removed envoy.reloadable_features.health_check.immediate_failure_exclude_from_cluster runtime guard and legacy code paths.
  • http: removed envoy.reloadable_features.add_and_validate_scheme_header and legacy code paths.
  • http: removed envoy.reloadable_features.check_unsupported_typed_per_filter_config, Envoy will always check unsupported typed per filter config if the filter isn't optional.
  • http: removed envoy.reloadable_features.dont_add_content_length_for_bodiless_requests deprecation and legacy code paths.
  • http: removed envoy.reloadable_features.http2_skip_encoding_empty_trailers and legacy code paths. Envoy will always encode empty trailers by sending empty data with end_stream true (instead of sending empty trailers) for HTTP/2.
  • http: removed envoy.reloadable_features.improved_stream_limit_handling and legacy code paths.
  • http: removed envoy.reloadable_features.remove_forked_chromium_url and legacy code paths.
  • http: removed envoy.reloadable_features.return_502_for_upstream_protocol_errors. Envoy will always return 502 code upon encountering upstream protocol error.
  • http: removed envoy.reloadable_features.treat_host_like_authority and legacy code paths.
  • http: removed envoy.reloadable_features.treat_upstream_connect_timeout_as_connect_failure and legacy code paths.
  • upstream: removed envoy.reloadable_features.upstream_host_weight_change_causes_rebuild and legacy code paths.

New Features

Deprecated