Antrea Operator

The Antrea Operator is a management tool that simplifies how you install and maintain Antrea, a system that handles network traffic between apps.

  • Infrastructure
  • Tools & Utilities
The Antrea Operator is a management tool that simplifies how you install and maintain Antrea, a system that handles network traffic between apps. It acts like an automated assistant, ensuring your network stays configured correctly and up-to-date without requiring manual effort.

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.

25/100 Low

Maintained
41last commit 318 days ago
Popular
00 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
0
Open issues
0
Last commit
2026-01-07
Activity
stale

Checked 15 days ago - source: GitHub (antrea-io/antrea-operator)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Nodes may be NotReady before Antrea Run kubectl get nodes and don’t panic if nodes show NotReady before Antrea is installed. A Kubernetes cluster often stays NotReady until a CNI (network plugin) is in place; after Antrea installs, nodes should become Ready. source
  • Check Antrea pods are running After install, run kubectl get pods --namespace kube-system -l app=antrea and confirm antrea-controller and antrea-agent pods are Running with READY values filled in. If they are not Running, Antrea cannot set up networking and your pods may fail to communicate. source
  • Prepare Windows nodes first If your cluster has Windows nodes, download and run Prepare-Node.ps1 with the Kubernetes version and node IP to install kubelet and kubeadm. Skipping this can leave the node unable to join the cluster or run Antrea networking properly. source
  • Platform limitation The operator is work-in-progress and currently only works on OpenShift 4; support for other Kubernetes platforms is still in progress. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why might Kubernetes nodes remain NotReady before Antrea is installed?

A Kubernetes cluster often stays NotReady until a CNI network plugin is in place. After Antrea is installed, the nodes should become Ready.

How can I confirm Antrea is running after installation?

Run kubectl get pods in the kube-system namespace with the Antrea label and confirm antrea-controller and antrea-agent pods are Running with READY values filled in. If they are not Running, Antrea cannot set up networking and your pods may fail to communicate.

What must be done before Antrea works on Windows nodes?

Download and run Prepare-Node.ps1 with the Kubernetes version and node IP to install kubelet and kubeadm. Skipping this can leave the node unable to join the cluster or run Antrea networking properly.

Where are Antrea, OVS, and strongSwan logs stored?

Logs for antrea-controller, antrea-agent, OVS, and strongSwan are stored on the node filesystem where those Antrea components run.

Answers sourced from antrea.io, github.com, github.com, github.com

Community

Collected 48 days ago - public community threads