Skip to content

envoy: Bump envoy version to 1.34.x #1302

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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Conversation

sayboras
Copy link
Member

@sayboras sayboras commented May 5, 2025

This is part of regular maintenance. Only merge once 1.18 is released, or 1.32 is EOL.

https://github.com/envoyproxy/envoy/releases/tag/v1.34.0

@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch from fb22ec9 to 164ca33 Compare May 5, 2025 05:17
@sayboras sayboras added the dont-merge/preview-only DON'T MERGE label May 5, 2025
@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch 6 times, most recently from b965a47 to 4dc1236 Compare May 7, 2025 02:29
@sayboras
Copy link
Member Author

sayboras commented May 7, 2025

/test

@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch from 4dc1236 to f3bad46 Compare May 7, 2025 02:56
@sayboras sayboras marked this pull request as ready for review May 7, 2025 04:48
@sayboras sayboras requested a review from a team as a code owner May 7, 2025 04:48
@sayboras sayboras requested a review from jrajahalme May 7, 2025 04:48
@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch from f3bad46 to 01e1606 Compare May 7, 2025 23:37
@sayboras sayboras changed the title envoy: Bump envoy version to 1.34.0 envoy: Bump envoy version to 1.34.x May 8, 2025
@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch 5 times, most recently from ed1a44a to be46604 Compare May 12, 2025 09:07
Copy link
Member

@jrajahalme jrajahalme left a comment

Choose a reason for hiding this comment

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

Thanks Tam!

I ran make tests locally (on arm64) without any issues.

Maybe add a reference to the envoy toolchain config into patches/0007-liburing-arm-build.patch so that the flags are less likely to diverge? (even smaller nit: the new patch file is created in an earlier commit for no apparent reason).

@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch from be46604 to 8edafff Compare May 14, 2025 01:28
+ "LD": "/usr/bin/lld-17",
+ },
+ "//conditions:default": {},
+ }),
Copy link
Member

Choose a reason for hiding this comment

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

Just realized that this was just recently removed in main. Any ideas why this would not be needed for Envoy 1.33, but then needed again in 1.34?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think it's related to the new feature introduced in upstream, will dig further once I have time.

Added support for io_uring in the default socket interface.

@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch 6 times, most recently from 0773933 to 606e551 Compare May 26, 2025 07:55
@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch from 606e551 to f66285d Compare May 26, 2025 14:14
@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch from f66285d to b70e2e1 Compare May 26, 2025 14:26
@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch from b70e2e1 to b103f5b Compare June 4, 2025 01:37
sayboras added 6 commits June 19, 2025 20:32
Signed-off-by: Tam Mach <tam.mach@cilium.io>
Signed-off-by: Tam Mach <tam.mach@cilium.io>
Relates: envoyproxy/envoy#39027
Signed-off-by: Tam Mach <tam.mach@cilium.io>
Without this patch, we will have the below error. This might be related
to new feature in envoy 1.34.0.

> Added support for io_uring in the default socket interface.

```
```

Signed-off-by: Tam Mach <tam.mach@cilium.io>
@sayboras sayboras force-pushed the pr/tammach/envoy-1.34 branch from b103f5b to f65298e Compare June 19, 2025 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants