Node xxxx-01 status is now: CIDRNotAvailable

Rancher
1

Hi,

we recently deployed an 7 node (3 master / 4 worker) cluster with rke on bare metal. As a CNI we’re using calico 3.10 and metalb for the LB part.
We notice some weird message after the installation though (see below)

kubectl get events
LAST SEEN   TYPE     REASON             OBJECT                MESSAGE
2m32s       Normal   CIDRNotAvailable   node/xxxx-04   Node xxxx-04 status is now: CIDRNotAvailable
2m21s       Normal   CIDRNotAvailable   node/xxxx-05   Node xxxx-05 status is now: CIDRNotAvailable
2m6s        Normal   CIDRNotAvailable   node/xxxx-06   Node xxxx-06 status is now: CIDRNotAvailable
2m57s       Normal   CIDRNotAvailable   node/xxxx-08   Node xxxx-08 status is now: CIDRNotAvailable
3m1s        Normal   CIDRNotAvailable   node/xxxx-09   Node xxxx-09 status is now: CIDRNotAvailable
2m53s       Normal   CIDRNotAvailable   node/xxxx-10   Node xxxx-10 status is now: CIDRNotAvailable

The output of :
kubectl cluster-info dump | grep -m 1 cluster-cidr

is empty, what it seems strange because we defined it in the rke manifest:

--snip--
kube-controller:
    service_cluster_ip_range: 10.2.228.0/22
    cluster_cidr: 10.2.225.0/24
--snip--

However, I can schedule pods on all worker nodes and they get IP addresses, so I don’t quite know how to interpret that message.
Anyone experiencing the same behavior?

Additional information:

kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:16:51Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:07:57Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}