Barun Acharya

@alexeysofin this maks sense. We need a way to limit what we annotate incase AppArmor is used an enforcer. I have added it to our Roadmap. One way to avoid...

> Thank you for the advice @daemon1024, I'll try switching to bpf enforcer, although bpf is still a pretty [early technology](https://www.form3.tech/blog/engineering/bypassing-ebpf-tools). Just for some clarification we are not using bpf...

@tico88612 Thanks for the interest. Just to provide some context. It will involve two aspects. 1. Supporting this configuration in the KubeArmor Operator helmchart itself, so as to deploy Operator...

@tico88612 > I've added the toleration fields for `helm/KubeArmor` (controller & relay) and `helm/KubeArmorOperator Nice. > But I was thinking about the CRD part. Should I add `KubeArmorRelayToleration` and `KubeArmorControllerToleration`...

- [x] EKS - Barun - [x] GKE - Barun - [ ] RHEL and Marketplace - Ramakant - [x] VM Support - Rudraksh - [x] Minikube - Prashant -...

Yes @yp969803

@MeenuyD Thanks a lot for the the interest. For starters, you can try setting up a minikube/microk8s environment on a Ubuntu Machine. Follow https://github.com/kubearmor/KubeArmor/blob/main/getting-started/deployment_guide.md to play around with KubeArmor. Once...

We have - [ ] k0s ( Will be supported after #1399 ) - [x] k3s ( Already being used in PRs ) - [ ] Minikube - [ ]...

Just a disclaimer, Expect KinD to not work since it depends on the underlying Host. So we can start with Minikube. @MeenuyD and @swastik959 You can collaborate on Slack if...

Keeping it open, since it's not properly fixed