Ramakant Sharma
Ramakant Sharma
@yp969803 one more point i would like to add is, make sure you first validate if non-root user works with apparmor enforcer.
the node has been cordoned, new pods will not be scheduled. right! ``` Taints: node.kubernetes.io/unschedulable:NoSchedule Unschedulable: true ```
@zestysoft we're planning it to get handled in v1.5.4 release. and to exempt those nodes you can make use of tolerations https://github.com/kubearmor/KubeArmor/blob/c933d8cebeda5ed48f0a015db5f0bd012ec7e006/deployments/helm/KubeArmorOperator/crds/operator.kubearmor.com_kubearmorconfigs.yaml#L337
tested locally working as expected.
@tesla59 please rebase the main and squash the commits.
PR tested locally on both containerd and crio setup. CI is failing due to docker pull limits and few tests are flaky.
Hey everyone, Thanks for your interest in the mentorship! There are a few prerequisites we expect to be included in your application. Please provide details or a reference document for...
few tests are failing due to `/readwrite` is missing in image at root directory
Hi @keshav78-78 thanks for your PR, I have few things to discuss before adopting this worker-pool approach: first, the only point where no. of events could be large is during...
@keshav78-78 let's make no of workers configurable using a flag.