Skip to content
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

Closed
DennisGlindhart opened this issue May 24, 2022 · 3 comments

Comments

@DennisGlindhart
Copy link

DennisGlindhart commented May 24, 2022

When using environment IP6_AUTODETECTION_METHOD = kubernetes-internal-ip on a node, I get the following error on all but the first node starting.

[INFO][10] startup/autodetection_methods.go 225: Including CIDR information from host interface. CIDR="2a00:1234:100:0:5:0:3:1/64"
[INFO][10] startup/startup.go 563: Node IPv6 changed, will check for conflicts
[WARNING][10] startup/startup.go 990: Calico node 'srvpwh-k8sworker0' is already using the IPv6 address 2a00:1234:100::.
[INFO][10] startup/startup.go 393: Clearing out-of-date IPv6 address from this node IP="2a00:1234:100::/64"
[WARNING][10] startup/utils.go 49: Terminating

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

Addresses:
  InternalIP:  2a00:1234:100:0:5:0:3:0
  Hostname:    srvpwh-k8sworker0

describe node srvpwh-worker1

Addresses:
  InternalIP:  2a00:1234:100:0:5:0:3:1
  Hostname:    srvpwh-k8sworker1

Your Environment

  • Calico 3.23.1
  • Kubernetes 1.23.4
  • OpenSuse Kubic
@fasaxc
Copy link
Member

fasaxc commented May 24, 2022

Original PR adding the feature: projectcalico/node#1242

@caseydavenport
Copy link
Member

Another issue reporting the same behavior: #6141

@remram44
Copy link

Fixed by #6228

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
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
Projects
None yet
Development

No branches or pull requests

4 participants