flannel VS calico

$ kubectl apply -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml

--pod-network=10.244.0.0/16: This is the default CIDR for flannel, and also avoids a conflict with my internal network if calico is used (which is the plan)

The installation of K8s id done by kubeadm. In this installation Containerd is used as CRI and flannel is used as CNI.

K8s is installed through kubeadm ad uses Containerd as CRI and Flannel as CNI. You can also install longhorn for the persistent storage and nginx ingress controller for the ingress rules.

This terraform module will deploy a high available Kubernetes (K8s) cluster on Amazon AWS, using mixed on-demand and spot instances. K8s is installed through kubeadm ad usesContainerd as CRI and Flannel as CNI. You can also install longhorn for the persistent storage and nginx ingress controller for the ingress rules. Please note, this is only an example on how to Deploy a Kubernetes cluster. For a production environment you should use EKS or ECS.

I don't use flannel but perhaps check this old issue: https://github.com/flannel-io/flannel/issues/663

It is definitively not normal behaviour. Cluster-internal subnets should be reachable from any node. Not being able to do so is a typical symptom of missing or misconfigured CNI. For flannel did you check this page?

Ask on Github.

I have Ubuntu 20.x and 21.x installed in my cluster, mostly because I am familiar with Ubuntu and figured the latest LTS versions would be a good idea to use for docker swarm and now kubernetes.... But there is a kernel bug, (k3s issue link and flannel issue link) with VXLAN that makes the default flannel container networking interface not work..... So I decided to Calico as the CNI to experiment with it, but I have been running to issues with BIRD is not ready: errors on only 2 of my nodes..... Which is an improvement then all of my nodes having the error like a couple of days ago.... but it is frustrating that only 2 have the error....

wget -O calicoctl https://github.com/projectcalico/calico/releases/latest/download/calicoctl-linux-amd64 chmod +x calicoctl sudo mv calicoctl /usr/local/bin/

You could use Calico in Google Cloud GKE. Apart from the CNI, you can also use Calico for defining network policies. Feel free to join the Calico communities on slack and Github. You can visit the Project Calico slack community https://slack.projectcalico.org/ or GitHub https://github.com/projectcalico/calico

We use Calico and they view this as a paid feature. https://github.com/projectcalico/calico/issues/1035

In eBPF mode we had this one: https://github.com/projectcalico/calico/issues/7110, fixed in the upcoming v3.26.0 release.

Another thread discusses setting it up and whether the L2 with ipaddresspool is supported is here https://github.com/projectcalico/calico/issues/6789 but it seems it is not tested .

$ kubectl apply -k ./ --dry-run='client' error: accumulating resources: accumulation err='accumulating resources from 'https://github.com/projectcalico/calico/manifests/tigera-operator.yaml?ref=v3.24.4': URL is a git repository': '/tmp/kustomize-3674962985/manifests/tigera-operator.yaml' refers to file 'tigera-operator.yaml'; expecting directory

If you do kubectl get pods --all-namespaces will show all the pods in Pending state, that's because we don't have any network plugin configured with our Kubernetes cluster. I use Calico network plugin for this demo but you can use any Kubernetes network plugin of your choice as long it has ability to define host gateway routes.