Actions
action #124631
closedUsage of netavark and aardvark in podman networks
Start date:
2023-02-15
Due date:
% Done:
0%
Estimated time:
Description
As of podman 4, we can make use of a network stack based on Netavark and Aardvark instead of former CNI:
https://www.redhat.com/sysadmin/podman-new-network-stack
https://blog.podman.io/2023/04/lease-dynamic-ips-with-netavark/
Danish Prakash has compiled some information about how this new network backend can be tested:
https://confluence.suse.com/display/~danishprakash/Podman+Networking+Features+to+Test
Packages to be installed:
zypper in netavark aardvark-dns
To do so, /etc/containers/containers.conf needs to be changed to:
[Network]
network_backend="netavark"
and it's possible to check which network stack it's using:
podman info --format {{.Host.NetworkBackend}}
(by default it should be cni)
We don't need to implement new tests with this, but do the change and then run podman network tests.
Affected versions:
- 15-SP3
- 15-SP4
- 15-SP5
- Tumbleweed
- Leap 15.4
- Leap 15.3
Acceptance criteria¶
- Extend podman_network.pm test module to switch the backend and run all the tests.
- Use https://confluence.suse.com/display/~danishprakash/Podman+Networking+Features+to+Test as a base
- Enable this only for podman > 4.4.2
Actions