-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
iso: Add FANOTIFY_ACCESS_PERMISSIONS to kernel configs. #15232
Conversation
Hi @eiffel-fl. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Can one of the admins verify this patch? |
ok-to-build-iso |
Hi @eiffel-fl, we have updated your PR with the reference to newly built ISO. Pull the changes locally if you want to test with them or update your PR further. |
@eiffel-fl Do you have your repo restricted from allowing others to push to your fork?
|
Actually, it looks like the branch creation is failing. Looks like the bot assumes the repo is under your own user but I see you're using a fork under an org. https://github.com/kinvolk/minikube/tree/francis/fanotify-perm We'll need to look into making that work, but in the meantime could you run the following:
|
Hi.
I updated my branch to add "for test purpose only" commit which modifies the ISO reference, so you cant now run |
We want those changes to get merged though, it's updating the ISO to use when starting minikube, and once we merge this PR we want to use the ISO built in this PR as it's the most up to date. |
/ok-to-test |
I understood, thank you for the clarification. |
kvm2 driver with docker runtime
Times for minikube ingress: 28.3s 28.3s 28.8s 28.3s 25.3s Times for minikube start: 54.9s 55.1s 54.2s 54.2s 54.7s docker driver with docker runtime |
Feel free to squash your commit |
This options enables fanotify to make permissions decisions on filesystem events. Signed-off-by: Francis Laniel <flaniel@linux.microsoft.com>
42265a8
to
0194cc3
Compare
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
kvm2 driver with docker runtime
Times for minikube ingress: 27.7s 29.3s 28.7s 25.1s 28.2s Times for minikube start: 53.7s 54.5s 54.8s 55.1s 54.7s docker driver with docker runtime
Times for minikube ingress: 81.5s 22.5s 21.5s 22.5s 82.0s Times for minikube start: 29.2s 24.1s 28.1s 28.4s 26.4s docker driver with containerd runtime
Times for minikube start: 22.1s 25.7s 22.4s 25.8s 23.1s Times for minikube ingress: 27.0s 27.0s 27.0s 26.0s 26.0s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
/retest-this-please |
kvm2 driver with docker runtime
Times for minikube start: 55.1s 54.2s 54.0s 54.2s 55.4s Times for minikube ingress: 28.7s 28.7s 28.6s 28.2s 29.2s docker driver with docker runtime
Times for minikube start: 26.8s 25.8s 29.7s 25.6s 29.1s Times for minikube ingress: 23.0s 22.5s 26.0s 22.0s 25.5s docker driver with containerd runtime
Times for minikube start: 22.4s 22.3s 26.0s 22.6s 22.4s Times for minikube ingress: 27.0s 27.0s 27.5s 27.0s 57.0s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eiffel-fl, spowelljr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thank you for the merge! |
Bump minikube to include fanotity permission added to latest version. Details, kubernetes/minikube#15232.
Bump minikube to include fanotity permission added to latest version. Details, kubernetes/minikube#15232.
Bump minikube to include fanotity permission added to latest version. Details, kubernetes/minikube#15232.
Bump minikube to include fanotity permission added to latest version. Details, kubernetes/minikube#15232.
Bump minikube to include fanotity permission added to latest version. Details, kubernetes/minikube#15232.
Hi.
In this PR, I added
CONFIG_FANOTIFY_ACCESS_PERMISSIONS
tominikube
ISO kernel configs.Inspektor Gadget makes use of
fanotify
to detect when new containers are created.To do so, we rely on
CONFIG_FANOTIFY_ACCESS_PERMISSIONS
which is sadly not present inminikube
kernel packaged in the ISO.As a consequence, we fallback to
podinformer
but this implementation does not permit our tool to trace early events after container creation.As you can see, with the default ISO, we fallback to
podinformer
.While with the new ISO, we use
fanotify
:I am sure this contribution can be of other use for other projects in the Kubernetes landscape and will empower other developers.
Of course, if you have any question and/or remark to make this contribution better, feel free to share :) !
Best regards and thank you in advance.