Installation Requirements
vNode reconfigures containerd on each worker node and registers itself as a Kubernetes RuntimeClass. Before deploying, verify that your nodes and Kubernetes environment meet the following requirements.
Requirements
| Requirement | Minimum | How to verify |
|---|---|---|
| Linux kernel | 6.1+ (6.3+ recommended) | uname -r |
| cgroup | v2 | stat -fc %T /sys/fs/cgroup/ → must return cgroup2fs |
| containerd | 1.7 or 2.0 | containerd --version |
| Kubernetes | 1.24+ | kubectl version |
Notes:
- Kernel 6.3 or later is recommended for full id-mapped tmpfs support.
- cgroup v1 is not supported. If
statreturnstmpfs, the node is on v1. cri-dockerd(Docker Desktop, Orbstack) andcri-o(OpenShift) are not supported container runtimes.
Supported environments
| Environment | Status | Notes |
|---|---|---|
| kind | Supported | — |
| EKS | Supported | AmazonLinux2023 AMI family required. EKS Auto Mode and Bottlerocket AMI not supported. |
| GKE | Supported | Autopilot clusters not supported. |
| AKS | Supported | Kubernetes 1.32.0+ with --os-sku AzureLinux required. |
| K3s | Supported | Verify kernel version and containerd version. |
| K3d | Supported | Verify kernel version and containerd version. |
| Rancher RKE | Supported | Verify kernel version and containerd version. |
Docker Desktop and Orbstack use cri-dockerd. OpenShift uses cri-o. Neither runtime is supported by vNode.
For cluster creation steps and platform-specific Helm install instructions, see Platform setup.