-
Notifications
You must be signed in to change notification settings - Fork 1.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
calico nodes 3.27.3 and 3.28.0 crash on IPv6 only cluster #8941
Comments
For reference the tigera installation:
|
Interestingly, same result with 3.27.3:
|
Seems like Calico is configured to detect an IPv4 address on the host, which it is failing to do because this is an IPv6 only cluster. Might want to adjust your Installation like this: nodeAddressAutodetectionV4: {} To disable IPv4 auto detection. |
Expected Behavior
calico-node runs
Current Behavior
calico-node crashes
Possible Solution
Unclear
Steps to Reproduce (for bugs)
Run
Result:
Context
This is an 1.30.1 k8s cluster that was running 3.26.4 before the upgrade:
The node on which calico-node crashes has the following IP+ routing information:
Your Environment
logs from 3.26.4
for reference, from a running pod on another node, attached as calico-node-lgjt7-log.txt:
calico-node-lgjt7-log.txt
The text was updated successfully, but these errors were encountered: