-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
IP AutoDetectionMethod kubernetes-internal-ip seems to throw last part of IP (corresponding to subnet) #6142
Labels
Comments
Original PR adding the feature: projectcalico/node#1242 |
Another issue reporting the same behavior: #6141 |
2 tasks
Fixed by #6228 |
This was referenced Jun 16, 2022
ruslanloman
pushed a commit
to ruslanloman/rke2-charts
that referenced
this issue
Aug 31, 2022
- There is a bug with ip_autodetection mode "k8s-internal-ip" in calico 3.23.1 projectcalico/calico#6142 and it was fixed in 3.23.2 version projectcalico/calico#6228
ruslanloman
pushed a commit
to ruslanloman/rke2-charts
that referenced
this issue
Sep 2, 2022
- There is a bug with ip_autodetection mode "k8s-internal-ip" in calico 3.23.1 projectcalico/calico#6142 and it was fixed in 3.23.2 version projectcalico/calico#6228 - Update tigera-operator version to v1.27.12. It's latest version that supports calico 3.23.3
This was referenced Sep 2, 2022
rbrtbnfgl
pushed a commit
to rancher/rke2-charts
that referenced
this issue
Sep 2, 2022
- There is a bug with ip_autodetection mode "k8s-internal-ip" in calico 3.23.1 projectcalico/calico#6142 and it was fixed in 3.23.2 version projectcalico/calico#6228 - Update tigera-operator version to v1.27.12. It's latest version that supports calico 3.23.3
github-actions bot
pushed a commit
to rancher/rke2-charts
that referenced
this issue
Sep 2, 2022
- There is a bug with ip_autodetection mode "k8s-internal-ip" in calico 3.23.1 projectcalico/calico#6142 and it was fixed in 3.23.2 version projectcalico/calico#6228 - Update tigera-operator version to v1.27.12. It's latest version that supports calico 3.23.3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using environment IP6_AUTODETECTION_METHOD = kubernetes-internal-ip on a node, I get the following error on all but the first node starting.
From the logs my guess it that the logic somehow throws away the last part of the IP-address (/64 in this case). This seems like a duplicate of this #5851 which seems to be same behaviour but for IPv4
describe node srvpwh-worker0
describe node srvpwh-worker1
Your Environment
The text was updated successfully, but these errors were encountered: