-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flannel Dualstack crash on 1.30.3 #10726
Comments
Just to be clear, this happened when trying to add IPv6 and etcd to a cluster that was started with sqlite and only IPv4? |
My cluster was started from SQLite and IPv4. I switched from SQLite to etcd like 2 months ago. |
same issue here - tried switching from ipv4 to dualstack. Running single node |
You can try deleting the node via The issue is that Kubernetes only assigns pod CIDRs to nodes when the node resource is created. If you try to switch from single-stack to dual-stack after the nodes have already joined the cluster, it won't add an IPv6 pod CIDR. |
Looking Good! Thank you really much. Maybe we can add error handling for this? |
We don't technically support changing CIDRs or other core bits of CNI config after the cluster is up, and we don't want to be in the business of deleting nodes for people... but yes Flannel could probably be fixed to not crash. |
Hi @brandond
Even agents nodes or just the server? |
All the nodes that you want to be dual-stack. As I said, they need to be deleted and recreated to get new CIDRs assigned. |
Hello, |
Environmental Info:
K3s Version: v1.30.3+k3s1 (f646604)
Node(s) CPU architecture, OS, and Version:
Linux REDACTED-server 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 7 15:25:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Linux kube-1 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 7 15:25:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Linux kube-2 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 7 15:25:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration: 1 server, 2 agents. Flannel over wireguard (but works fine on IPv4).
Describe the bug:
Steps To Reproduce:
Have this configuration:
curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.30.2+k3s1 sh -s - server --write-kubeconfig-mode 644 --tls-san REDACTED-public-IPv4 --flannel-iface wg0 --node-ip 10.6.99.1 --node-external-ip REDACTED-public-IPv4 --advertise-address 10.6.99.1
, after that I modified systemd service to add etcd and now IPv6.Wireguard configuration:
The text was updated successfully, but these errors were encountered: