Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
p
powerful-summer-42797
08/17/2022, 8:59 AMHello,
Does anyone use calico instead of flannel with k3s?
I can observe the node is taking far more time to start with calico than with flannel (pods are running after 200s instead of 30s).
Any clue on how to fix that?
b
bland-account-99790
08/17/2022, 11:04 AMI guess because flannel code is included in the k3s binary whereas calico code is not. Therefore, containerd needs to pull the calico images
p
powerful-summer-42797
08/17/2022, 11:24 AMRegarding 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.