docs: 1.3.0 release notes #926
Conversation
|
@lyft/network-team and everyone else. Please have a look. There may be a few straggling things that we get in here but this is pretty close. |
docs/intro/version_history.rst
Outdated
| configuration. | ||
| * TCP level :ref:`listener <config_listeners_per_connection_buffer_limit_bytes>` and | ||
| :ref:`cluster <config_cluster_manager_cluster_per_connection_buffer_limit_bytes>` connections now | ||
| have configurable buffer limits at which point connection level back pressure is applied. Full end |
There was a problem hiding this comment.
We technically don't have back pressure yet, we're only using them on the receive side to ensure we start pushing the buffers down the filter chain when we hit the limits.
docs/intro/version_history.rst
Outdated
| a route's retry policy in addition to via the :ref:`x-envoy-upstream-rq-per-try-timeout-ms | ||
| <config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms>` HTTP header. | ||
| * :ref:`HTTP virtual host matching <config_http_conn_man_route_table_vhost>` now includes support | ||
| for wildcard domains. |
There was a problem hiding this comment.
I think this is just prefix wildcard or suffix. Not arbitrary wildcard is it?
| * The :ref:`HTTP rate limit filter <config_http_filters_rate_limit>` can now be applied to internal, | ||
| external, or all requests via the `request_type` option. | ||
| * :ref:`Listener binding <config_listeners>` now requires specifying an `address` field. This can be | ||
| used to bind a listener to both a specific address as well as a port. |
There was a problem hiding this comment.
This bit needs to move to top and probably be called out as a breaking change in the config.
There was a problem hiding this comment.
The breaking change policy starts at 1.3.0, so I'm not going to list out every breaking change. I will clarify the text a bit to make this clear.
|
And do you expect the zipkin stuff to get in by 1.3 time frame ? |
I will take a look at the PR tomorrow and try to get a feel for how close it is. Releases are obviously totally arbitrary and most people are running master, so making it by a particular release is not super important IMO. |
| <config_listener_ssl_context>` setting. Additionally, URI type SANs can be verified. | ||
| * HTTP filters can now be passed :ref:`opaque configuration | ||
| <config_http_conn_man_route_table_opaque_config>` specified on a per route basis. | ||
| * By default Envoy now has a built in crash handler that will print a back trace. This behavior can |
There was a problem hiding this comment.
Yes will refresh this PR today.
Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
No description provided.