Replies: 4 comments
-
@docbobo could you share how you've installed Calico and how you enabled / disabled IPv6 in this case? Is this a Calico operator install or something else? If so, could you share your Might be worth raising an issue and filling out the template, which prompts for some of the information that we'll need to diagnose: https://github.com/projectcalico/calico/issues/new/choose |
Beta Was this translation helpful? Give feedback.
-
I have the same problem |
Beta Was this translation helpful? Give feedback.
-
@caseydavenport first of all, me need to disable this went away. But maybe that piece of information is helpful as well. I've installed Calico via the operator, then followed the instructions to enable ipv6 dual stack. The reason I wanted to disable ipv6 again was due to the fact that my nodes were losing their ipv6 addresses after a few hours. As this results in the bird error mentioned above, I wanted to disable ipv6 again. Now, in the meantime I found out that for some weird reason my nodes were not taking into account the default for |
Beta Was this translation helpful? Give feedback.
-
Looks like right now, the code keeps the old value even if IPv6 is disabled: calico/node/pkg/lifecycle/startup/startup.go Lines 559 to 561 in f7d9764 Probably need a way for the operator to tell calico/node to clear any configured IPv6 address.
This is a little bit surprising to me. Do you have the error log from this by chance? |
Beta Was this translation helpful? Give feedback.
-
A few weeks ago I tried enabling ipv6 on my network but had to disable that again due to some weird issues. Ever since, I get the following log outputs in
calico-node
over and over again:I believe this is due to the fact that there is
projectcalico.org/IPv6Address
annotation on each of my nodes, but I have no idea how to get rid of it. As far as I am concerned, I have removed all the settings that would enable ipv6 support, the nodes do not receive an ipv6 address either.I tried manually removing the annotation, but that resulted in
calico-node
failing to start at all.This is on 3.29.1
Beta Was this translation helpful? Give feedback.
All reactions