Antrea Agent Ubuntu
Antrea Agent (Ubuntu) is a Kubernetes node agent for the Antrea networking solution, using Open vSwitch to provide pod networking and Network Policy…
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 Antrea pods after install After installing Antrea, run kubectl get pods --namespace kube-system -l app=antrea and look for Running pods. If they are not running, Pod networking likely won't work. source
- NotReady nodes may be normal at first When you check nodes with kubectl (the Kubernetes command-line tool), they may show NotReady before Antrea is installed because no CNI (the network plugin that lets Pods talk) is present. Installing Antrea helps the nodes become Ready so Pod traffic can work. source
- Use Helm flags for L7 NetworkPolicy If you use Helm to enable Layer 7 NetworkPolicy, add --set featureGates.L7NetworkPolicy=true,disableTXChecksumOffload=true. This turns on the feature and disables TX checksum offload (a network-card performance setting) that the docs recommend turning off. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How can I verify that the Antrea agent is installed correctly?
Run kubectl to list the Antrea pods in the kube-system namespace and look for Running pods. If they are not running, pod networking likely will not work.
What Helm flags should I set to enable L7 NetworkPolicy?
Use --set featureGates.L7NetworkPolicy=true,disableTXChecksumOffload=true. This enables the feature and disables TX checksum offload, which the docs recommend turning off.
Where are the antrea-agent logs stored?
The antrea-agent logs, along with logs for antrea-controller, OVS, and strongSwan daemons, are stored in the filesystem of the Node where the pods are scheduled.
How do I access the antrea-agent API directly?
Log into the node where the antrea-agent runs or exec into the antrea-agent container. Then use the local endpoint with the Bearer Token stored in the file system.
What happens if antrea-agent hangs after its dependencies are corrupted?
The agent can hang and remain unusable. It may not self-heal or terminate so the init pod can reinstall its dependencies.
Answers sourced from antrea.io, github.com, github.com, github.com, github.com
Community
- Reddit (reddit)
Collected 48 days ago - public community threads