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.

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

Kick-off release 1.20.1 #18658

Merged
merged 3 commits into from
Oct 27, 2021
Merged

Conversation

mathetake
Copy link
Member

Should've done this before #18421 merged.

Signed-off-by: Takeshi Yoneda <takeshi@tetrate.io>
* listener: fixed an issue on Windows where connections are not handled by all worker threads.
* lua: fix ``BodyBuffer`` setting a Lua string and printing Lua string containing hex characters. Previously, ``BodyBuffer`` setting a Lua string or printing strings with hex characters will be truncated.
* xray: fix the AWS X-Ray tracer bug where span's error, fault and throttle information was not reported properly as per the `AWS X-Ray documentation <https://docs.aws.amazon.com/xray/latest/devguide/xray-api-segmentdocuments.html>`_. Before this fix, server error was reported under the 'annotations' section of the segment data.
* Listener: fix a crash when updating any listener that does not bind to port
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the note for #18421

Signed-off-by: Takeshi Yoneda <takeshi@tetrate.io>
Signed-off-by: Takeshi Yoneda <takeshi@tetrate.io>
@lambdai
Copy link
Contributor

lambdai commented Oct 18, 2021

@mathetake There is another blocking the istio from picking up envoy 1.20. See #18616

As far as I can tell, It impacts listener in place update which occurs on both istio gateways and sidecar proxies.

Do you want to hold 1.20.1 until that fix is landed?

@mathetake
Copy link
Member Author

Yeah but this PR is not for releasing 1.21, but about just cleaning up release notes for 1.20 so this must be merged prior to that anyway.

@mathetake mathetake requested a review from lizan October 19, 2021 01:07
@lambdai
Copy link
Contributor

lambdai commented Oct 19, 2021

Yeah but this PR is not for releasing 1.21, but about just cleaning up release notes for 1.20 so this must be merged prior to that anyway.

Got it. Thanks!
By 1.21 you mean 1.20.1, right?

@mathetake
Copy link
Member Author

Yeah but this PR is not for releasing 1.21, but about just cleaning up release notes for 1.20 so this must be merged prior to that anyway.

Got it. Thanks! By 1.21 you mean 1.20.1, right?

Ah yes:D

@mathetake mathetake merged commit 94a0813 into envoyproxy:release/v1.20 Oct 27, 2021
@mathetake mathetake deleted the kickoff1.20.1 branch October 27, 2021 06:52
@lobkovilya
Copy link
Contributor

Hello @lizan @mathetake!
Could you please help me to figure out what is the timeline for Envoy 1.20.1?

@lizan
Copy link
Member

lizan commented Nov 2, 2021

@lobkovilya we don't cut point release unless there's a security fix, so there's no ETA for 1.20.1. meanwhile you can use latest commit of v1.20 branch or v1.20-latest tag from docker.

aidanhahn pushed a commit to datawire/envoy that referenced this pull request Jan 13, 2022
Signed-off-by: Takeshi Yoneda <takeshi@tetrate.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants