-
Notifications
You must be signed in to change notification settings - Fork 355
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
Made changes in support_matix.md about Amazon Linux 2 by HariVamsiK #1016
Conversation
Signed-off-by: HariVamsiK <[email protected]>
Update: On Amazon Linux 2 with Kernel Version 5.10, Kubearmor is found to be running on systemd mode. The enforcement is sometimes partial with following supported LSM's: "Capability,Yama,Lockdown,SELinux,BPF". Refer [Issue](https://github.com/kubearmor/KubeArmor/issues/919). | ||
|
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.
Hey @HariVamsiK, what does it mean by "enforcement is sometimes partial"?
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.
The issue was solved when I installed a previous version of kubearmor first, then removed it and installed the new version and doing a daemon reload. The command "kubearmor probe" gave the output as enforcement as partial when I installed the new version directly.
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.
Okay, the enforcement as Partial is not correct. In Amazon Linux-2, AppArmor is not available and in karmor probe
we are only watching for AppArmor. We should ideally be also watching for BPF LSM too and we already have an issue for that here: kubearmor/kubearmor-client#211
Except that, in the screenshot you shared, KubeArmor is not running in the first place. The probe is just giving a note that enforcement will work if KubeArmor runs successfully.
Now with issue #919 user mentioned that they were not able to run KubeArmor v0.6 on AL-2. Can you confirm if you were able to successfully deploy KubeArmor (v0.6) or the latest version in systemd mode?
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.
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.
Can you also confirm for the latest KubeArmor version?
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.
@HariVamsiK Can you please also explain how this PR fixes #919? |
🤔 Where is this change made? Sorry but I couldn't understand this point |
Thank you @HariVamsiK for verifying that the issue is resolved. |
Signed-off-by: HariVamsiK [email protected]
Updated support_matrix.md file
Fixes #919
New update about KubeArmor support on Amazon Linux 2 (Kernel Version 5.10) with screenshots attached in the issue thread.
Previously KubeArmor supported only few LSM's. With the latest update in kernel version the support has been increased. This has been added to the support_matrix.md file as an update.