hello, I'm having problems using the manifest file to deploy cilium after cluster init because it find that the node is not ready. Of course it's not ready because the network is missing so the job pod which should install cilium cannot be scheduled 😄 :

0/1 nodes are available: 1 node(s) had untolerated taint {<http://node.kubernetes.io/not-ready|node.kubernetes.io/not-ready>: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.

am I missing something? Or should I deploy cilium in a different way and then deploy other helm resource using the manifests? Thanks for your help

I find it more manageable to deploy Cilium via Helm directly … and not by injecting a Helm YAML manifest into the K3s manifests dir.

thanks, I'll do it in the same way

This is what the

bootstrap

flag on the HelmChart manifest is for. If you set that to true, it will run it on a server node, and with tolerations for not-ready status.

Cool @creamy-pencil-82913 - thank you

No, it doesn't change anything other than how the install job pod is configured (host net + tolerations)

Thank you for elaborating @creamy-pencil-82913

thanks a lot @creamy-pencil-82913!