DEV Community

Fred Richards
Fred Richards

Posted on • Edited on

NetworkManager, leave Calico Interfaces alone.

#kubernetes #calico

We've all been there. You set up your nifty new Kubernetes cluster, and choose your favorite CNI, Calico, to handle networking.

But then NetworkManager comes along and has to watch and interfere with all of these new virtual interfaces introduced by Calico.

We can tell NetworkManager to ignore these interfaces by making the new file...

/etc/NetworkManager/conf.d/calico.conf
Enter fullscreen mode Exit fullscreen mode

... and including the following content inside of it.

[keyfile]
unmanaged-devices=interface-name:cali*;interface-name:tunl*;interface-name:vxlan.calico
Enter fullscreen mode Exit fullscreen mode

Now those virtual interfaces used by Calico will get ignored and will not see any interference from NetworkManager. Of course, you can also always decide not to use NetworkManager, but this may not be practical in all environments.

Top comments (0)

Read next

willvelida profile image

Building a token refresh service for the Fitbit API with Container App Jobs

Will Velida -

ptuladhar3 profile image

11th Dec 2024 — OpenAI Outage (ChatGPT) Explained: Kubernetes Clusters on Fire!

Puru -

simone_morellato profile image

💡 How Does Sveltos Compare to Other Kubernetes Tools Like Argo CD and Flux CD?

Simone Morellato -

lakhera2015 profile image

Introduction to k8sgpt - Simplifying Kubernetes Troubleshooting - Part 1

Prashant Lakhera -