This message was deleted.
# k3sa
adamant-kite-43734
07/01/2024, 3:42 PMThis message was deleted.
l
late-barista-75996
07/01/2024, 5:20 PMThat upgrade for me caused k3s to restart in a loop due to https://github.com/k3s-io/k3s/issues/10419 . Had to roll back to v1.29.5
late-barista-75996
07/01/2024, 5:20 PMBut that seemingly only rears its head with ipv6
e
eager-exabyte-12639
07/02/2024, 1:03 PMThank you for your response. For us, a rollback to v1.29.5 also solved the problem, even though we are not using any special IPv6 settings. A rollback using
curl -sfL <https://get.k3s.io> | K3S_TOKEN="..." INSTALL_K3S_VERSION="v1.29.5+k3s1" sh -s - server --server <https://10.1.0.50:6443> --bind-address 10.1.0.50 --flannel-iface enp1s0 --disable traefikl
late-barista-75996
07/02/2024, 3:31 PMYou might consider logging a bug, then
late-barista-75996
07/02/2024, 3:32 PM(when I say "consider" I mean "please do that" 😛 )
late-barista-75996
07/09/2024, 8:59 PMJust upgraded to v1.29.6+k3s2 which solved my networking issues, but now I'm hitting THIS issue. Any chance you logged a bug?
late-barista-75996
07/09/2024, 8:59 PM@creamy-pencil-82913 any idea what this might be?
late-barista-75996
07/09/2024, 9:09 PMI went ahead and logged https://github.com/k3s-io/k3s/issues/10474, please add any details you have @eager-exabyte-12639
late-barista-75996
07/09/2024, 9:23 PMSounds like this is https://github.com/k3s-io/k3s/issues/10444. Looks like you're also using
--bind-address33 Views