antrea-agent-ubuntu-arm
Per-node agent for Antrea, a Kubernetes-native networking solution that delivers Pod networking, Network Policies, and Layer 3/4 security services on ARM (v7)…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
72/100 Good
- Maintained
- 100last commit 16 days ago
- Popular
- 651,816 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
- GitHub stars
- 1,816
- Open issues
- 263
- Last commit
- 2026-11-05
- Latest release
- v2.7.0
- License
- Apache-2.0
- Activity
- rising
Checked 16 days ago - source: GitHub (antrea-io/antrea)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Check that Antrea's pods are running After installing Antrea, run `kubectl get pods --namespace kube-system -l app=antrea` from a machine that can reach your Kubernetes cluster; kubectl is the command-line tool for Kubernetes. It should show antrea-controller and antrea-agent pods as Running; if they do not, cluster networking may not be set up yet. source
- Expect NotReady nodes before CNI Run `kubectl get nodes` before and after installing Antrea; nodes can show NotReady until a CNI, the plugin that connects containers to the network, is installed. After Antrea is working, they should become Ready, which means the cluster network is usable. source
- Install antctl for troubleshooting Download antctl, Antrea's command-line tool for inspecting Antrea, for your OS and CPU, make it executable, and put it in a PATH folder so you can type `antctl`. It is optional, but it gives you useful diagnostics if pods or cluster networking misbehave. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Why should I pull antrea/antrea-agent-ubuntu instead of antrea/antrea-agent-ubuntu-arm?
The antrea-agent-ubuntu-arm image is specific to arm/v7. Users are encouraged to use the multi-platform antrea/antrea-agent-ubuntu image instead.
Why does kubectl logs on an antrea-agent pod require a container name?
The pod may contain multiple containers, so choose the antrea-agent or antrea-ovs container name. That lets you inspect the correct Antrea component logs.
Why can nodes remain NotReady after installing Antrea?
Nodes can show NotReady until a CNI, the plugin that connects containers to the network, is installed. After Antrea is working, they should become Ready.
How can I get Antrea diagnostics when pods or cluster networking misbehave?
Download antctl for your OS and CPU, make it executable, and put it in a PATH folder. It is optional, but it gives useful diagnostics for Antrea.
How do I access the antrea-agent API directly?
Log into the node that runs the antrea-agent or exec into the antrea-agent container. Then access the local endpoint directly using the Bearer Token stored in the file system.
Answers sourced from community.broadcom.com, github.com, github.com, github.com, hub.docker.com
Community
- TKGS Antrea | Tanzu (other)
Collected 47 days ago - public community threads