Hey all! I'm in the process of revamping my Kubernetes cluster for development and I'm leaning towards using Flux. I'm wondering if anyone has successfully set up Talos without a CNI and with kube-proxy turned off, then installed Cilium through Flux afterward. My nodes seem to always end up in a NotReady state after I bootstrap with Talos, so I'd love to hear if anyone's cracked this and how they did it. Thanks in advance!
5 Answers
It's not a dumb idea at all to think of installing components like CNI during bootstrap! A lot of folks use Ansible for that—install Talos and then set up the CNI, secrets provider, and ArgoCD all in one go. This can streamline the process significantly and ensure everything's configured from the get-go. Just remember, playing around is also part of the learning process!
Exactly, I do similar with my clusters too, integrating everything from the start.
You can deploy the cluster without CNI and use inline manifests to install Cilium. This method's been effective for others, and implementing Flux afterward should work fine as long as you manage the timing correctly for deployments!
I've had the same experience—install Cilium directly via kubectl initially and then let Flux take over.
Absolutely! That usually leads to a smoother setup.
You could certainly use the Helm method through Flux! There's some documentation from Talos that specifically lays out deploying Cilium—might be a good starting point for the timing issues you're facing.
In the past, I’d set up the VMs with Terraform using Talos and then go ahead with the Cilium installation before bringing Flux into the picture. It works well when your cluster bootstraps with everything set properly, then you can let Flux manage updates and configurations. Just make sure you have a solid base setup to avoid headaches later!
You can set it up, but be careful! There are challenges with Flux needing CNI to operate normally. If you're using the all-in-one Flux pod featured on GitHub, it might help avoid some of the communication issues during deployment. Cozystack could be an interesting alternative to explore for Talos and Flux integration too!
Cozystack definitely simplifies some setups; it's worth checking out!
Right, it takes the edge off the CNI dependency issues! Good to keep in mind.
Right? It's all about finding the balance between learning and getting things done efficiently.