I'm working on setting up Cilium in a dual-stack mode on my Raspberry Pi cluster, which has two nodes and a fresh installation. I've disabled Flannel and used the following switches: `--cluster-cidr=10.42.0.0/16,fd12:3456:789a:14::/56` and `--service-cidr=10.43.0.0/16,fd12:3456:789a:43::/112`. I installed Cilium using Helm with some specific values, including enabling kube-proxy replacement and setting related IPv6 configurations. However, I'm facing an issue where the Cilium pods are throwing a warning: "Waiting for k8s node information" with the error of required IPv6 PodCIDR not available. When I disable IPv6, everything works fine, but since I'm learning, I want to figure out IPv6 as well. Also, I'm using ULA address space, and both nodes have an IPv6 address from that space. Any help would be appreciated!
2 Answers
It looks like you're facing issues with the IPv6 settings. The message about the 'required IPv6 PodCIDR not available' usually indicates that Cilium can't find the proper IPv6 PodCIDR. Since you mentioned that you set the `clusterPoolIPv6MaskSize` to 56, it's worth noting that the default value is 120, which might limit the range too much. However, it seems you tried setting it to 120, and now it's saying the CIDR size is too large. If you're using a k3s setup, consider the advice from the GitHub issue you linked. Installing it with `--cluster-cidr=/104` or `/112` is worth a shot to see if that resolves your issue. If you're fine with not having active IPv6 functionality for now, you can run without it while you learn! Good luck!
You're on the right path! The `clusterPoolIPv6MaskSize` should typically be set to a number that fits your DHCP setup. Using /120 with that CIDR might overlap with the Pod CIDR range, causing conflicts. The advice to use /104 or /112 in k3s actually aligns with most of the current practices for dual-stack setups. If IPv6 isn't crucial for your learning at this point, you could temporarily disable it and focus on familiarizing yourself with other Cilium functionalities. When you're ready to dive into IPv6, reconfigure accordingly!
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically