kubearmor
Kubearmor Overview
Secure your stack with a hardened Kubearmor image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.
KubeArmor is a cloud-native runtime security enforcement system that restricts the behavior of pods, containers, and nodes (VMs) at the system level, such as process execution, file access, and networking operations. It leverages Linux Security Modules (LSMs) such as AppArmor, SELinux, or BPF-LSM to enforce user-defined policies, and uses eBPF to generate rich alerts and telemetry tied to container, pod, and namespace identity.
Try It Out
KubeArmor can be deployed with a Helm chart.
Prerequisites
- A running Kubernetes cluster (v1.21 or higher is recommended)
- Helm v3.8 or higher for OCI support (Installation instructions)
kubectlinstalled and configured- A Linux kernel with AppArmor, SELinux, or BPF-LSM enabled for policy enforcement
Step 1: Start Cluster
If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions
Step 2: Add Repository to your Local Client
Add the Helm chart to your local Helm client.
helm repo add kubearmor https://kubearmor.github.io/charts
helm repo updateStep 3: Deploy via Helm Chart
helm upgrade --install kubearmor kubearmor/kubearmor \
-n kubearmor --create-namespace \
--set kubearmor.image.repository=reg.mini.dev/kubearmor \
--set kubearmor.image.tag=latest \
--waitWait a minute and check that the Pods are up and running:
kubectl -n kubearmor get poConfirm that the Minimus image was deployed:
kubectl -n kubearmor describe pods | grep Image:Step 4: Clean Up
Uninstall the chart to delete the namespace and its resources, including Pods, DaemonSets, Deployments, Services, Secrets, ConfigMaps, etc.:
helm uninstall kubearmor -n kubearmorTechnical Considerations
The Kubearmor image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.
Kubearmor built by Minimus:
- Runs as root to support required functions in alignment with the public image.
- Requires elevated privileges and host-level access (Linux capabilities such as
SYS_ADMIN,SYS_PTRACE, andNET_ADMIN, plus host mounts such as/sys/kernel/security,/sys/kernel/debug, and the container runtime socket) to enforce policies via eBPF and Linux Security Modules. - Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.
The Payoff
A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.
- See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
- Review the compliance report to see the default hardening and security configurations for the image.
Terms & Info
Trademark
This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.
Disclaimer
Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.