-
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
Test KubeArmor on AWS Graviton #1063
Comments
Hello @Ankurk99 I'll work on this issue. Please assign it to me. |
Hey @HariVamsiK, if you need any assistance in setting up the cluster or if you want access to AWS Graviton, feel free to ask. |
Yeah sure. Thanks @Ankurk99 |
Hey @HariVamsiK, were you able to setup the cluster? |
Did it yesterday..My AWS account was having some issues. I'm yet to test it. |
@Ankurk99 Do I need to test it on any other platform(like microk8s or minikube)? If not I can update the support matrix and raise the PR. |
Hey @HariVamsiK it seems that KubeArmor is running fine. Can you please perform the items mentioned in the description checklist? For enforcement you can try applying any policies and see if the resources are being correctly blocked. Similarly we will be expecting logs for the corresponding enforcement. This should be verified with Please let us know if you face any difficulty |
Yeah sure. |
Hey @HariVamsiK, were you able to test the enforcement and observability? |
Lets verify with Amazon Linux 2 as well. We can update the support-matrix post that. |
@HariVamsiK Can you please update the support matrix with AWS Graviton support here: https://github.com/kubearmor/KubeArmor/blob/main/getting-started/support_matrix.md? |
Feature Request
Short Description
We already support KubeArmor on ARM based processors (tested on Raspberry Pi 4, M1). The aim of this issue is to test and confirm KubeArmor working on AWS ARM based processor - Graviton.
karmor probe
Ref: https://aws.amazon.com/ec2/graviton/
The text was updated successfully, but these errors were encountered: