You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cilium install does NOT respect k8s pod CIDR that was used to during cluster creation, instead it sits itself with 10.0.0.0/8 in the way of everything and breaks connectivity of the node as it creates routes on the nodes.
quote from installation docs: It will automatically detect and use the best configuration possible for the Kubernetes distribution you are using.
One should safely assume this would mean the k8s pod CIDR is detected.
Ways to resolve:
detect k8s pod CIDR
document this behaviour and do not pretend setting up cilium is easy as cilium install
bonus points: easy argument as --pod-cidr for install command 👍
The text was updated successfully, but these errors were encountered:
Hi @korncola, thanks for the feedback. Could you share which Kubernetes distribution you're using? It's possible that the autodetection just didn't properly take into account the configuration from that environment. Hopefully it's a relatively small change to fix that up and improve the experience for all users going forward.
cilium install
does NOT respect k8s pod CIDR that was used to during cluster creation, instead it sits itself with 10.0.0.0/8 in the way of everything and breaks connectivity of the node as it creates routes on the nodes.quote from installation docs:
It will automatically detect and use the best configuration possible for the Kubernetes distribution you are using.
One should safely assume this would mean the k8s pod CIDR is detected.
Ways to resolve:
cilium install
--pod-cidr
for install command 👍The text was updated successfully, but these errors were encountered: