Skip to content

Support for non orchestrated containers

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

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 an real use case in edge devices where orchestration is hard due to resource restrictions. KubeArmor can help protect such environment.

Clone this wiki locally