-
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
Fixes for platforms where init container fails to run #16815
Conversation
fe06a58
to
3fbb0e3
Compare
test-me-please |
3fbb0e3
to
a5efa19
Compare
Looking into the conformance-test-ipv6 failure - resolved the issue. |
a5efa19
to
865635f
Compare
test-me-please |
AKS failure -
AWS-CNI failure -
|
ea3f7e6
to
c11ca03
Compare
We need to mount cgroup2 filesystem on the underlying host in order to enable socket-based load-balancing in environments with container runtime cgroupv2 configurations. See issues for more details - cilium/cilium#16259 and cilium/cilium#16815.
We need to mount cgroup2 filesystem on the underlying host in order to enable socket-based load-balancing in environments with container runtime cgroupv2 configurations. See issues for more details - cilium/cilium#16259 and cilium/cilium#16815. Signed-off-by: Aditi Ghag <aditi@cilium.io>
Checking the ongoing backports, I see that this PR is labelled as |
@qmonnet The PR is already backported to v1.10. I updated the label. Thanks for checking! |
See commit messages.
Fixes: #16814 / #16828
Fixes: #16771
Fixes: fa8bea4 ("cilium-daemonset: Fix ineffective socket-lb caused by incorrect cgroup2 fs mount")
Release note