Network backend for podman (#256)

* networkBackend

README.adoc

@@ -22,8 +22,7 @@ If you want to preview changes for more complex contributions, follow this proce
 . Start the build:
 +
 ----
-$ python scripts/convert-all.py ./scripts/convert
--adoc.sh .github/workflows/asciidoc-convert-check.yml
+$ python scripts/convert-all.py ./scripts/convert-adoc.sh  published-adoc.txt
 ----
 
 * `convert-adoc.sh` converts each adoc to HTML

cli/index.adoc

@@ -454,8 +454,6 @@ include::./single-logical-service.adoc[leveloffset=0]
 
 include::./protocols.adoc[leveloffset=0]
 
-include::../kubernetes/ingress.adoc[leveloffset=1]
-
 // Type: reference
 [id="cli-global-options"] 
 == CLI options

cli/networkBackend.adoc

@@ -0,0 +1,38 @@
+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}}
+----
+
+.Additional information
+
+See link:{podman-link}[Using Skupper Podman].

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-link}.
 
 --
 

partials/attributes.adoc

@@ -7,6 +7,7 @@
 :console-link: ../console/index.html[Using the Skupper console]
 :cli-link: ../cli/index.html[Using the Skupper CLI]
 :podman-link: ../cli/podman.html[Using Skupper Podman]
+:networkbackend-link: ../cli/networkBackend.html[Configuring Podman networkBackend for {skupper-name}]
 :tokens-link: ../cli/tokens.html[Using Skupper tokens]
 :overview-link: ../overview/index.html[Overview]
 :security-link: ../overview/security.html[Security]

published-adoc.txt

@@ -1,6 +1,7 @@
 cli/index.adoc
 cli/tokens.adoc
 cli/podman.adoc
+cli/networkBackend.adoc
 cli/native-security-options.adoc
 yaml/index.adoc
 operator/index.adoc