Why Change to Network Manager?
Netplan is a YAML network configuration abstraction for various backends. Using Network Manager has several advantages for easy configuration of network devices. Netplan is easy to understand and strait forward because it uses YAML configuration.
Requirements
Installing requirements for using Network Manager with Netplan.
network-manager - network management framework (daemon and userspace tools)
Installing Requirements
Configuration Steps
Backup your YAML 00-installer-config.yaml files.
Create a new YAML file like 00-installer-confg.yaml and insert the below lines to it.
network:
version: 2
renderer: NetworkManager
Apply the new configuration and check IP details.
Output after a Netplan apply command.
lo UNKNOWN 127.0.0.1/8 enp32s0f0 UP 10.166.5.107/24 enp32s0f1 DOWN enp59s0f0 UP enp32s0f2 DOWN enp32s0f3 DOWN enp59s0f1 DOWN enp216s0f0 UP enp216s0f1 UP enp216s0f2 UP enp216s0f3 UP docker0 DOWN 172.17.0.1/16 cilium_net@cilium_host UP cilium_host@cilium_net UP 10.0.0.122/32 cilium_vxlan UNKNOWN
OK, done with out configuration with Network Manager using Netplan but now we want to configure a static address for our Kubernetes server. We use NMTUI from the CLI
Below shows we have a static address with interface enp59s0f0 with a 192.168.2.1/24 range.
lo UNKNOWN 127.0.0.1/8 enp32s0f0 UP 10.166.5.107/24 enp32s0f1 DOWN enp59s0f0 UP 192.168.2.1/24 enp32s0f2 DOWN enp32s0f3 DOWN enp59s0f1 DOWN enp216s0f0 UP enp216s0f1 UP enp216s0f2 UP enp216s0f3 UP docker0 DOWN 172.17.0.1/16 cilium_net@cilium_host UP cilium_host@cilium_net UP 10.0.0.122/32 cilium_vxlan UNKNOWN
We now have a static address on interface enp59s0f0 with a range of 192.168.2.1/24.
That's it, your done and ready for production or testing.
