This message was deleted.
# k3s
a
This message was deleted.
b
I guess because flannel code is included in the k3s binary whereas calico code is not. Therefore, containerd needs to pull the calico images
p
Regarding the image, I use airgapped images, so no pulling time.
Regarding the code being included, I though about it, and calico-node starts as a pod (and calico isn't a single component as flannel), so you are right, but I am not sure this is the only reason.