Skip to content

Latest commit

 

History

History
36 lines (22 loc) · 1 KB

README.md

File metadata and controls

36 lines (22 loc) · 1 KB

calico-route-sync

Introduction

Nodes outside the k8s cluster synchronize calico routing information to directly access pods.

This project only uses the listwatch method of node/blockaffinit/ippool resources and will not change any resources of the k8s cluster.

img.png

Usage

bin：

sudo ./calico-route-sync --kubeconfig=/home/root/.kube/config

docker:

docker run --rm -it --name calico-route-sync \
 --network=host --cap-add NET_ADMIN \
 -v ~/.kube/config:/root/config \
 q946666800/calico-route-sync:0.2 \
 --kubeconfig=/root/config

Notice

The usage scenario is limited to only supporting Calico, and vm-01 is in the same network as the Kubernetes nodes.

The advantage is simplicity, efficiency, and stability (similar to Calico node). Traffic flows directly from vm-01 to the Kubernetes nodes without going through other routers or tunnels.

If you want vm-01 to be in a different network, you can use the project k8s-tun.