-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
v1.12 backports 2023-10-02 #28351
v1.12 backports 2023-10-02 #28351
Conversation
Note that the BPF fix will need #28295 to land first. |
You beat me to this. Yes, I noticed the pending backport PR, so just mark this one as draft. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix itself is good of course, so pre-approving. Thank you!
[ upstream commit 458479b ] b2de07a ("bpf: Fix missing drop notifications on ct lookup failures") took care of most paths. But we also need to throw a drop notification when ipv6_hdrlen() returns an error. Signed-off-by: Julian Wiedmann <jwi@isovalent.com> Signed-off-by: Tam Mach <tam.mach@cilium.io>
[ upstream commit cc56e70 ] These resources are enabled in cilum-proxy build, and can be used in CiliumEnvoyConfig directly, however, without related imported statements, Cilium agent will fail to marshal/unmarshal objects. Sample error ``` level=warning msg="Ignoring invalid CiliumEnvoyConfig JSON (proto:\u00a0(line 1:405): unable to resolve \"type.googleapis.com/envoy.extensions.filters.http.router.v3.Router\": \"not found\") ``` Signed-off-by: Tam Mach <tam.mach@cilium.io>
606ae53
to
f2626bf
Compare
/test-backport-1.12 |
Reviews are in, CI is also great, marking this ready to merge. |
Once this PR is merged, you can update the PR labels via: