-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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.11 backports 2022-02-22 #18888
v1.11 backports 2022-02-22 #18888
Conversation
/test-backport-1.11 Job 'Cilium-PR-K8s-1.19-kernel-4.9' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment Job 'Cilium-PR-K8s-1.18-kernel-4.9' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment |
runtime provision fail, retesting |
/test-runtime |
There's a known issue with runtime provisioning at the moment, which we hope to resolve in #18886 . If that's the only problem we have with runtime then I'll be inclined to ignore it to 🚢 . |
[ upstream commit 28f0dae ] Envoy Go API is updated to contain the generated validation code. Envoy image is updated to support the new EndpointId option for the bpf_metadata listener filter. NPDS field 'Policy' is renamed as 'EndpointID'. 'Policy' field was not used for anything, so might as well recycle it while this API is not yet public. Envoy retries may fail on "address already in use" when the original source address and port are used on upstream connections. Cilium typically does this in the egress proxy listeners. Fix this by using a Cilium Envoy build that always sets SO_REUSEADDR when original source address and port is used. Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
35a3a18
to
8bf468b
Compare
[ upstream commit 571a484 ] Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
8bf468b
to
b76df4d
Compare
/test-backport-1.11 |
Two failures:
|
Once this PR is merged, you can update the PR labels via: