Antrea-migrator

Antrea-migrator is a Kubernetes migration tool that imports an existing CNI plugin's network configuration and security policies into Antrea.

  • Infrastructure
  • Tools & Utilities
Antrea-migrator is a Kubernetes migration tool that imports an existing CNI plugin's network configuration and security policies into Antrea. It lets cluster administrators switch to Antrea networking without manually rebuilding their Pod networking or rules.

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 not supported.

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

First-install notes

  • Check Antrea pods are running After install, use kubectl (the Kubernetes command-line tool) to list pods in the kube-system namespace with -l app=antrea, and confirm the agent and controller pods are Running. If they are stuck or restarting, Antrea cannot wire up pod networking, so containers may fail to get IPs or talk to each other. source
  • NotReady nodes before install are normal A brand-new cluster may show kubectl get nodes output as NotReady before Antrea is installed because Kubernetes needs a CNI plugin (a network add-on) to connect pods. That does not mean the nodes are broken; recheck after Antrea is installed. source
  • If using L7 policy, set Helm flags If you want L7NetworkPolicy (application-layer network rules), include featureGates.L7NetworkPolicy=true and disableTXChecksumOffload=true in the Helm (Kubernetes package installer) command. Without those settings, that optional policy feature may not work correctly. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

When should I deploy antrea-migrator?

Deploy it after Antrea is up and running in the cluster.

How does antrea-migrator run in the cluster?

It runs as a DaemonSet named antrea-migrator.

What does antrea-migrator do to Pods during migration?

It restarts all non hostNetwork Pods in the cluster in-place and performs necessary network resource cleanup.

How can I verify Antrea is running before proceeding?

Use kubectl to list pods in the kube-system namespace with -l app=antrea and confirm the agent and controller pods are Running.

Answers sourced from antrea.io, github.com

Community

Collected 48 days ago - public community threads