This message was deleted.

Calico is primarily a CNI (Container Network Interface) plugin that can optionally serve as a BGP-based network provider. Traefik is primarily an Ingress Controller. Calico and Traefik can coexist in a Kubernetes environment, but conflicts might arise depending on how they are configured. Calico’s IP addressing and NAT rules might conflict with Traefik’s LoadBalancer or external IP configurations. If Traefik is exposed using a LoadBalancer service and Calico is configured to manage external BGP routes, route advertisement or NAT traversal issues might occur.

Thanks, that last bit is what I'm looking for. We're not doing any external router adverts or mucking with NAT. It seems a bit mysterious that the K3S install docs for Calico just want you to disable Traefik, but don't provide much info as to the why's or when's keeping Traefik might be ok.