The Canonical-developed Netplan has served for Linux network configuration on Ubuntu Server and Cloud versions for years. With the recent Ubuntu 23.10 release, Netplan is now being used by default on the desktop. Canonical is committing to fully leveraging Netplan for network configuration with the upcoming Ubuntu 24.04 LTS release and in turn also marking the Netplan 1.0 release.
Netplan is Canonical’s network configuration manager for Linux systems with network interfaces being described via YAML files. Netplan considers itself as a “network configuration abstraction renderer” that in turn interfaces with NetworkManager or systemd-networkd. Netplan finally made its way to the Ubuntu 23.10 desktop by default with having better integration for knowing when connections are created/modified through NetworkManager.
For Ubuntu 24.04 LTS, Canonical plans to polish the Netplan codebase and deliver a Netplan 1.0 release with API/ABI stability. They are also hoping other Linux distributions begin adopting Netplan. Debian so far has decided to go with Netplan for their nework stack on Debian Cloud images.
How is it better than using NetworkManager or systemd-networkd directly?
Why is it worth the extra complexity?
It has a structured yaml with a test command for potentially destructive config changes over ssh. Other than that: none. It was a real pain upgrading some servers, as always with Ubuntu.
I just moved to Ubuntu from Fedora Silverblue, for some $reasons. I regret it already.
You know what can also test destructive changes?
Cockpit’s networkmanager interface.
It literally has no benefits, and is only a pain to use.
Actually, it does have one benefit: it integrates with Canonical’s other tech. For example, MAAS uses ot for networking, and I bet lxc uses it somehow.
I like yaml generally but netplan was a huge unnecessary pain in the ass.