Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grpc: fix maximum gRPC message size changelogs #33369

Merged
merged 2 commits into from
Apr 8, 2024
Merged

grpc: fix maximum gRPC message size changelogs #33369

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5cae379
fix grpc change logs
botengyao Apr 5, 2024
914d533
fix format
botengyao Apr 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions changelogs/current.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -458,6 +458,11 @@ new_features:
change: |
The ``/stats/prometheus`` endpoint can now emit prometheus ``summary`` metric types by explicitly setting the
``histogram_buckets`` query parameter to ``summary``.
- area: grpc
change: |
Added maximum gRPC message size that is allowed to be received in Envoy gRPC. If a message over this limit is received,
the gRPC stream is terminated with the RESOURCE_EXHAUSTED error. This limit is applied to individual messages in the
streaming response and not the total size of streaming response. Defaults to 0, which means unlimited.

deprecated:
- area: listener
Expand All @@ -469,8 +474,3 @@ deprecated:
deprecated :ref:`split_spans_for_request <envoy_v3_api_field_config.trace.v3.ZipkinConfig.split_spans_for_request>`
in favor of :ref:`spawn_upstream_span
<envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.Tracing.spawn_upstream_span>`.
- area: grpc
change: |
Added maximum gRPC message size that is allowed to be received in Envoy gRPC. If a message over this limit is received,
the gRPC stream is terminated with the RESOURCE_EXHAUSTED error. This limit is applied to individual messages in the
streaming response and not the total size of streaming response. Defaults to 0, which means unlimited.