Skip to content

v0.6 Release Blog

Ankur Kothiwal edited this page Aug 27, 2022 · 22 revisions

THIS IS A WORK-IN-PROGRESS ...

Support for non-orchestrated containers

KubeArmor already has support for K8s orchestrated and Bare-Metal/VM workloads. With the v0.6 stable release, KubeArmor will also support un-orchestrated containerized workloads. KubeArmor supports both observability and policy enforcement in this mode. For the enforcement, KubeArmor generates AppArmor profiles for individual containers based on the policy specified. The containers are required to start with the AppArmor profiles attached (using security-opt apparmor='profile-name'). These profiles can later be dynamically updated by KubeArmor to insert, modify or remove the AppArmor enforcement. Un-orchestrated workloads have a real use case in edge devices where orchestration is hard due to resource restrictions. KubeArmor can now help protect such environment.

Improvements to policy allow listing

Karmor Probe, ability to probe for support of kubearmor

Performance improvements

Ability to watch for system calls events

BCC deprectation in favor of cilium/ebpf

Clone this wiki locally