From 25cb5a399a31870d69c6c4b7bfa4df8a862a1a00 Mon Sep 17 00:00:00 2001
From: Paul Wright <pwright@redhat.com>
Date: Fri, 15 Nov 2024 09:02:59 +0000
Subject: [PATCH] networkBackend

---
 cli/networkBackend.adoc | 35 +++++++++++++++++++++++++++++++++++
 cli/podman.adoc         | 23 ++---------------------
 2 files changed, 37 insertions(+), 21 deletions(-)
 create mode 100644 cli/networkBackend.adoc

diff --git a/cli/networkBackend.adoc b/cli/networkBackend.adoc
new file mode 100644
index 0000000..f4c0f26
--- /dev/null
+++ b/cli/networkBackend.adoc
@@ -0,0 +1,35 @@
+include::../partials/attributes.adoc[]
+// Category: skupper-cli
+// Type: procedure
+[id='podman-networkbackend']
+= Configuring Podman networkBackend for {skupper-name}
+
+By default, Podman v4 and later use Netavark which works with {skupper-name}.
+However, if you upgraded from an earlier version of Podman, you might need to configure Podman to use Netavark.
+
+If you are using CNI, for example, if you upgrade from Podman v3, you must also install the `podman-plugins` package.
+For example, `dnf install podman-plugins` for RPM based distributions.
+
+NOTE: CNI will be deprecated in the future in preference of Netavark.
+
+.Procedure
+
+. To install `netavark` on rpm based Linux, for example, RHEL8:
++
+----
+$ sudo dnf install netavark
+----
+
+. Configure podman to use `netavark` by making sure the following lines exist in the `/etc/containers/containers.conf` file:
++
+----
+[network]
+network_backend = "netavark"
+----
+
+. Confirm that `netavark` is configured as the podman network backend:
++
+----
+$ podman info --format {{.Host.NetworkBackend}}
+----
+
diff --git a/cli/podman.adoc b/cli/podman.adoc
index 5bd51ef..9f9fe16 100644
--- a/cli/podman.adoc
+++ b/cli/podman.adoc
@@ -68,32 +68,13 @@ See link:{cli-link} for information about using the Skupper CLI to create Podman
 * `netavark` is configured as the podman network backend.
 +
 --
-By default, Podman v4 uses Netavark which works with Skupper.
-
-If you are using CNI, for example, if you upgrade from Podman v3, you must also install the `podman-plugins` package.
-For example, `dnf install podman-plugins` for RPM based distributions.
-
-NOTE: CNI will be deprecated in the future in preference of Netavark.
-
 To check if `netavark` is configured as the podman network backend:
 
 ----
-$ podman info | grep networkBackend
-----
-
-To install `netavark` on rpm based Linux, eg RHEL8:
-
-----
-$ sudo dnf install netavark
-----
-
-Configure podman to use `netavark` by making sure the following lines exist in the `/etc/containers/containers.conf` file:
-
-----
-[network]
-network_backend = "netavark"
+$ podman info --format {{.Host.NetworkBackend}}
 ----
 
+If the output is something other than `netavark`, see link:networkBackend.adoc[Configuring Podman networkBackend for {skupper-name}].
 
 --