-
Notifications
You must be signed in to change notification settings - Fork 362
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
add USERS.md file for collating tetragon users #2143
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.
Would be infinitely better with a commit message explaining why the change, what the change, etc, but otherwise LGTM.
Actually, the commit definitely needs to be signed. Use And, in addition, it needs a label added, e.g. If you do both, then it should go all green hopefully. :D |
The [0] commit added sensor's destroy hook and changed kprobe logic to cleanup genericKprobeTable in there. We also need to change removeAllSensors to do destroy instead of unload so the kprobe hook is executed. [0] 70e4fcd ("pkg/sensors: cleanup kprobe entry from table on destroy") Signed-off-by: Jiri Olsa <[email protected]>
Renaming NOTIFYKILLER to NOTIFYENFORCER action as a first step of the whole rename, so we have schema changes separated. Signed-off-by: Jiri Olsa <[email protected]>
Renaming killer bpf sensor to enforcer including the file object names. Signed-off-by: Jiri Olsa <[email protected]>
Renaming killer spec to enforcer to have the spec changes separated. Signed-off-by: Jiri Olsa <[email protected]>
Renaming killer go code to enforcer. Signed-off-by: Jiri Olsa <[email protected]>
Renaming killer go objects to enforcer. Signed-off-by: Jiri Olsa <[email protected]>
Renaming killer-tester to enforcer-tester. Signed-off-by: Jiri Olsa <[email protected]>
closing this and opening a fresh one on a clean slate :) |
No description provided.