Kubeadm cluster with own Cidr using canal cni

5 views
Skip to first unread message

Vaishnavi Rajulu

unread,
Oct 14, 2024, 2:37:15 AM10/14/24
to submariner-users
Hi Guys,

I am trying to deploy a kubeadm cluster for submariner. But kubeadm's pod and svc cidr should be unique eg: 10.50.0.0/16 and 10.51.0.0/16 with canal CNI.
I have initialized kubeadm using these cidrs and installed canal cni. Now when I join this to submariner broker. The submariner pods and default kube-proxy, coredns, scheduer all the pods are starting to get crashloopback or error in loop. 

My doubt is changing canal's default cidr to my own cidr cause these kind of issue in kubeadm?
Reply all
Reply to author
Forward
0 new messages