System Requirements

This document outlines the minimum and supported requirements for running ARMO’s Kubernetes-integrated modules.

1. Kubernetes Version

ARMO supports Kubernetes clusters starting from version v1.26 onward.
While it may work on earlier versions, those are not officially tested or supported.

2. Supported Kubernetes Distributions

ARMO is compatible with a broad set of Kubernetes distributions and environments.
The following table shows the current support status:

Kubernetes Distribution	Support Status	Comments
EKS	Supported	—
AKS	Supported	—
GKE	Supported	—
GKE Autopilot	Supported	—
OKE	Supported	—
OpenShift	Supported	—
Rancher	Supported	—
Mirantis	Supported	—
Nutanix	Supported	—
VMware Tanzu	Supported	—
Self-managed (on-prem / VM)	Supported	—
Minikube	Supported	Good for test/dev environments
kind	Supported	Good for CI/test
k0s	Supported
k3s	Supported	Lightweight/edge cluster usage
k3d	Supported	Docker-based local k3s cluster
microk8s	Supported	Local development cluster
AWS Fargate	Partially Supported	Requires direct node access for full functionality
Docker Desktop Kubernetes	Partially Supported	Limited for full runtime agent deployment

3. Linux Kernel Version

The node-agent relies on eBPF technology, which is exclusively implemented on Linux kernels. Consequently, this feature is only functional on Linux distributions, and the Linux kernel version on the node must be >= 5.4

4. CPU Architectures

X86
ARM64

5. Summary

Use Kubernetes v1.26+ or newer.
If your cluster runs on a distribution not listed above, it may work but is untested.
For serverless environments (e.g., AWS Fargate), ARMO’s runtime/agent model may not be fully compatible — please evaluate accordingly.
Confirm your distribution is among the supported list (or contact ARMO for validation).