Conversation
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
|
@envoyproxy/maintainers please do a scan and see what if anything I missed. |
| 1.16.0 (Pending) | ||
| ================ | ||
| 1.16.0 (October 8, 2020) | ||
| ======================== |
There was a problem hiding this comment.
is the // intended in
build: added visibility rules for upstream. If these cause visibility related breakage, see notes in //BUILD.?
| @@ -51,7 +50,7 @@ Minor Behavior Changes | |||
| * router: now consumes all retry related headers to prevent them from being propagated to the upstream. This behavior may be reverted by setting runtime feature `envoy.reloadable_features.consume_all_retry_headers` to false. | |||
| * stats: the fake symbol table implemention has been removed from the binary, and the option "--use-fake-symbol-table" is now a no-op with a warning. | |||
There was a problem hiding this comment.
render as :option:--use-fake-symbol-table (and --enable-fine-grain-logging) for consistency?
There was a problem hiding this comment.
ah, turns out I had to revert this one - as a "not real flag" it's not documented, so flagging it as an option causes problems.
| * stats: the fake symbol table implemention has been removed from the binary, and the option "--use-fake-symbol-table" is now a no-op with a warning. | ||
| * thrift_proxy: special characters {'\0', '\r', '\n'} will be stripped from thrift headers. | ||
| * watchdog: replaced single watchdog with separate watchdog configuration for worker threads and for the main thread :ref:`Watchdogs<envoy_v3_api_field_config.bootstrap.v3.Bootstrap.watchdogs>`. It works with :ref:`watchdog<envoy_v3_api_field_config.bootstrap.v3.Bootstrap.watchdog>` by having the worker thread and main thread watchdogs have same config. | ||
| * watchdog: replaced single watchdog with separate watchdog configuration for worker threads and for the main thread configured via :ref:`Watchdogs<envoy_v3_api_field_config.bootstrap.v3.Bootstrap.watchdogs>`. It works with :ref:`watchdog<envoy_v3_api_field_config.bootstrap.v3.Bootstrap.watchdog>` by having the worker thread and main thread watchdogs have same config. |
There was a problem hiding this comment.
sorry for not being able to comment exactly inline
but maybe truncate rocketmq_proxy network-level filter: to rocketmq_proxy:?
| * ext_authz filter: request timeout will now count from the time the check request is created, instead of when it becomes active. This makes sure that the timeout is enforced even if the ext_authz cluster's circuit breaker is engaged. | ||
| This behavior can be reverted by setting runtime feature ``envoy.reloadable_features.ext_authz_measure_timeout_on_check_created`` to false. When enabled, a new `ext_authz.timeout` stat is counted when timeout occurs. See :ref:`stats | ||
| // <config_http_filters_ext_authz_stats>`. | ||
| This behavior can be reverted by setting runtime feature ``envoy.reloadable_features.ext_authz_measure_timeout_on_check_created`` to false. When enabled, a new `ext_authz.timeout` stat is counted when timeout occurs. See :ref:`stats <config_http_filters_ext_authz_stats>`. |
There was a problem hiding this comment.
this and envoy.restart_features.use_apple_api_for_dns_lookups are the only features that have double back ticks. single for consistency?
| * http: added :ref:`CDN Loop filter <envoy_v3_api_msg_extensions.filters.http.cdn_loop.v3alpha.CdnLoopConfig>` and :ref:`documentation <config_http_filters_cdn_loop>`. | ||
| * http: added :ref:`MaxStreamDuration proto <envoy_v3_api_msg_config.route.v3.RouteAction.MaxStreamDuration>` for configuring per-route downstream duration timeouts. | ||
| * http: introduced new HTTP/1 and HTTP/2 codec implementations that will remove the use of exceptions for control flow due to high risk factors and instead use error statuses. The old behavior is used by default, but the new codecs can be enabled for testing by setting the runtime feature `envoy.reloadable_features.new_codec_behavior` to true. The new codecs will be in development for one month, and then enabled by default while the old codecs are deprecated. | ||
| * http: introduced new HTTP/1 and HTTP/2 codec implementations that will remove the use of exceptions for control flow due to high risk factors and instead use error statuses. The old behavior is used by default for HTTP/1.1 and HTTP/2 server connections. The new codecs can be enabled for testing by setting the runtime feature `envoy.reloadable_features.new_codec_behavior` to true. The new codecs will be in development for one month, and then enabled by default while the old codecs are deprecated. |
| * ext_authz: the :ref:`dynamic metadata <envoy_v3_api_field_service.auth.v3.OkHttpResponse.dynamic_metadata>` field in :ref:`OkHttpResponse <envoy_v3_api_msg_service.auth.v3.OkHttpResponse>` | ||
| has been deprecated in favor of :ref:`dynamic metadata <envoy_v3_api_field_service.auth.v3.CheckResponse.dynamic_metadata>` field in :ref:`CheckResponse <envoy_v3_api_msg_service.auth.v3.CheckResponse>`. |
There was a problem hiding this comment.
no problem :-)
I've got a check_format fix queued for this - we had a few in the last release as well and it's an easy one to automate!
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
rojkov
left a comment
There was a problem hiding this comment.
Thank you for correcting building.rst!
docs/root/install/building.rst
Outdated
|
|
||
| Please see the linked :repo:`CI <ci/README.md>` and :repo:`Bazel <bazel/README.md>` documentation | ||
| for more information on performing manual builds. | ||
| Please note that for Clang/LLVM 8 and lower, Envoy must be built with `--define tcmalloc=gperftools` |
There was a problem hiding this comment.
You could also emphasize the fact that only x86 builds may need --define tcmalloc=gperftools. And since the new tcmalloc wants C++17 GCC 8+ may also suffice.
mattklein123
left a comment
There was a problem hiding this comment.
LGTM with one comment! Thanks!
| *Changes that are expected to cause an incompatibility if applicable; deployment changes are likely required* | ||
|
|
||
| * build: added visibility rules for upstream. If these cause visibility related breakage, see notes in //BUILD. | ||
| * build: added visibility rules for upstream. If these cause visibility related breakage, see notes in `BUILD <https://github.com/envoyproxy/envoy/blob/master/BUILD>`_. |
| | 1.13.0 | 2019/12/31 | 2020/01/20 | +20 days | 2021/01/20 | | ||
| | 1.14.0 | 2020/03/31 | 2020/04/08 | +8 days | 2021/04/08 | | ||
| | 1.15.0 | 2020/06/30 | 2020/07/07 | +7 days | 2021/07/07 | | ||
| | 1.16.0 | 2020/09/30 | | | | |
There was a problem hiding this comment.
@envoyproxy/stable-maintainers do we have a release manager lined up for Q4?
Risk Level: n/a
Testing: n/a
Release Notes: yes