Replies: 2 comments
-
failed to allocate IP 10.43.0.10: provided IP is already allocated The default IP for DNS of the cluster is read the dock https://docs.k3s.io/networking/basic-network-options |
Beta Was this translation helpful? Give feedback.
0 replies
-
In the end I deleted my coredns deployment, restarted k3s, let it recreate the coredns setup, and all is ok. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Every 3 minutes I get this slew of events starting with "Applying manifest at ":
In journalctl I also get:
time="2024-07-23T17:32:34Z" level=error msg="Failed to process config: failed to process /var/lib/rancher/k3s/server/manifests/coredns.yaml: failed to create kube-system/kube-dns /v1, Kind=Service for kube-system/coredns: Service "kube-dns" is invalid: spec.clusterIPs: Invalid value: []string{"10.43.0.10"}: failed to allocate IP 10.43.0.10: provided IP is already allocated"
Can anyone shed any light on these? The cluster operations seem fine. k3s v1.29.4+k3s1
Beta Was this translation helpful? Give feedback.
All reactions