-
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
install: add mountPropagation directive to bpf-maps volume in cilium DS #18438
Conversation
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.
Nice catch!
Looking at how this happened, it seems it was just an oversight and there isn't much I think we can do to avoid it happening again. We did follow the process thoroughly when making that backport, so neither tests nor reviews were skipped.
Yep, I think this specific backport was just particularly tricky as master had diverged quite a bit from v1.10 wrt the helm templates |
/test-backport-1.10 Job 'Cilium-PR-K8s-GKE' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment |
/mlh new-flake Cilium-PR-K8s-GKE 👍 created #18439 |
e5fcdf2
to
beee219
Compare
@jibi You will need to rebase before starting the end-to-end tests, due to the recent CI breakage. |
The original backport was missing the "mountPropagation: Bidirectional" directive for the bpf-maps volume, causing the bpffs to not get mounted in the host. Fixes: d221704 ("install/kubernetes: use bidirectional mounts to mount bpf fs") Signed-off-by: Gilberto Bertin <gilberto@isovalent.com>
beee219
to
f733e14
Compare
/test-backport-1.10 Job 'Cilium-PR-K8s-GKE' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment |
Restarting a couple CI jobs as they failed due to a full disk: The GKE CI job failed with known test breakage #18285. |
GKE failed with a known issue, l4lb didn't start but it would fail anyway as the fix for that test hasn't been backported yet, marking as ready to merge |
net-next run failed provisioning, but the likelihood that mountpropagation setting changes only cause a problem on that build and none of the other test runs seems pretty low: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.23-kernel-net-next/187/ Merging. |
The original backport was missing the "mountPropagation: Bidirectional"
directive for the bpf-maps volume, causing the bpffs to not get mounted
in the host.
Fixes: d221704 ("install/kubernetes: use bidirectional mounts to mount bpf fs")