Proposal documentation found here: https://github.com/mhmxs/calico-route-reflector-operator-proposal. Please feel free to share your ideas !!!
- Kubernetes cluster up and running
- Calico network on Kubernetes data store a.k.a.
KDD
. - Configured Calico
BGPPeer
s one for route reflector mesh and an other for clients. More info
This Kubernetes operator can monitor and scale Calico route refloctor pods based on node number per zone. The operator owns a few environment variables:
ROUTE_REFLECTOR_CLUSTER_ID
Route reflector cluster ID, default224.0.0.%d
ROUTE_REFLECTOR_MIN
Minimum number of route reflector pods per zone, default3
ROUTE_REFLECTOR_MAX
Maximum number of route reflector pods per zone, default25
ROUTE_REFLECTOR_RATIO
Node / route reflector pod ratio, default0.005
(1000 * 0.005 = 5
)ROUTE_REFLECTOR_NODE_LABEL
Node label of the route reflector nodes, defaultcalico-route-reflector=
ROUTE_REFLECTOR_ZONE_LABEL
Node label of the zone, default ``ROUTE_REFLECTOR_TOPOLOGY
Selected topology of route reflectors [simple, multi], defaulr:simple
During the api/core/v1/Node
reconcile phases it calculates the right number of route refloctor nodes per zone. It supports linear scaling only and it multiplies the number of nodes with the given ratio and than updates the route reflector replicas to the expected number.
This is a standard Kubebuilder opertor so building and deploying process is similar as a stock Kubebuilder project.
Use official image:
kustomize build config/crd | kubectl apply -f -
kustomize build config/default | kubectl apply -f -
Build your own image:
IMG_REPO=[IMG_REPO] IMG_NAME=[IMG_NAME] IMG_VERSION=[IMG_VERSION] make test docker-push install deploy
- Etcd data store support (Currently you have to edit manager's yaml manually)
- Use custom resource instead of environment variables
- Dedicated or preferred node label
- Disallow node label
- Handle taints and tolerations
We appreciate your help!
To contribute, please read our contribution guidelines: CONTRIBUTION.md