diff --git a/config/config.py b/config/config.py
index 4610720c..09d6eae7 100644
--- a/config/config.py
+++ b/config/config.py
@@ -10,3 +10,6 @@ def path_nav(page):
 
 latest_release_version = _latest_release["version"]
 latest_release_date = format_date(parse_timestamp(_latest_release["date"]))
+ID = "{{.ID}}"
+Image="{{.Image}}"
+Labels="{{.Labels}}"
diff --git a/convert-all.sh b/convert-all.sh
index b80abff6..e7a9e80c 100755
--- a/convert-all.sh
+++ b/convert-all.sh
@@ -21,3 +21,8 @@ cp -r subrepos/skupper-docs/images/ input/docs/
 # To process nested numbered lists
 python python/nested-numbers.py input/docs/operator/
 
+# To workaround https://github.com/ssorj/plano/issues/3
+
+sed -i 's/.ID/ID/g' input/docs/cli/podman.md
+sed -i 's/.Image/Image/g' input/docs/cli/podman.md
+sed -i 's/.Labels/Labels/g' input/docs/cli/podman.md
diff --git a/docs/community/index.html b/docs/community/index.html
index 53149905..335efe79 100644
--- a/docs/community/index.html
+++ b/docs/community/index.html
@@ -146,7 +146,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/cli/index.html b/docs/docs/cli/index.html
index 2bd0a2b2..84f4b642 100644
--- a/docs/docs/cli/index.html
+++ b/docs/docs/cli/index.html
@@ -91,7 +91,8 @@ <h2 id="checking-the-skupper-cli">Checking the Skupper CLI</h2>
 </ol>
 <h2 id="creating-a-site-using-the-cli">Creating a site using the CLI</h2>
 <p>A service network consists of Skupper sites.
-This section describes how to create a site using the default settings.</p>
+This section describes how to create a site in a Kubernetes cluster using the default settings.
+See <a href="../cli/podman.html">Using Skupper Podman</a> for information about using the Skupper CLI to create Podman sites.</p>
 <ul>
 <li>The <code>skupper</code> CLI is installed.</li>
 <li>You are logged into the cluster.</li>
@@ -365,6 +366,13 @@ <h3 id="exposing-services-from-a-different-namespace-to-the-service-network">Exp
 <h2 id="exposing-services-on-the-service-network-from-a-local-machine">Exposing services on the service network from a local machine</h2>
 <p>After creating a service network, you can expose services from a local machine on the service network.</p>
 <p>For example, if you run a database on a server in your data center, you can deploy a front end in a cluster that can access the data as if the database was running in the cluster.</p>
+<dl><dt><strong>📌 NOTE</strong></dt><dd>
+
+<p>This documentation describes creating a gateway from a local host to a cluster site.
+An alternative approach is to create a site on the local host and link to the cluster site.
+See <a href="../cli/podman.html">Using Skupper Podman</a> for information about using the Skupper CLI to create Podman sites.</p>
+</dd></dl>
+
 <h3 id="exposing-simple-local-services-to-the-service-network">Exposing simple local services to the service network</h3>
 <p>This section shows how to expose a single service running locally on a service network.</p>
 <ul>
@@ -618,7 +626,7 @@ <h3 id="gateway-yaml-reference">Gateway YAML reference</h3>
 <li><strong>qdr-listeners.port</strong><br />
 Port for skupper router, typically <code>5672</code>.</li>
 </ul>
-<h3 id="exploring-a-service-network">Exploring a service network</h3>
+<h2 id="exploring-a-service-network">Exploring a service network</h2>
 <p>Skupper includes a command to allow you report all the sites and the services available on a service network.</p>
 <ul>
 <li>A service network with more than one site</li>
@@ -668,11 +676,11 @@ <h3 id="exploring-a-service-network">Exploring a service network</h3>
 </ol>
 </li>
 </ol>
-<h4 id="securing-a-service-network">Securing a service network</h4>
+<h2 id="securing-a-service-network">Securing a service network</h2>
 <p>Skupper provides default, built-in security that scales across clusters and clouds.
 This section describes additional security you can configure.</p>
 <p>See <a href="../policy/index.html">Securing a service network using policies</a> for information about creating granular policies for each cluster.</p>
-<h5 id="restricting-access-to-services-using-a-kubernetes-network-policy">Restricting access to services using a Kubernetes network policy</h5>
+<h3 id="restricting-access-to-services-using-a-kubernetes-network-policy">Restricting access to services using a Kubernetes network policy</h3>
 <p>By default, if you expose a service on the service network, that service is also accessible from other namespaces in the cluster.
 You can avoid this situation when creating a site using the <code>--create-network-policy</code> option.</p>
 <ol>
@@ -689,7 +697,7 @@ <h5 id="restricting-access-to-services-using-a-kubernetes-network-policy">Restri
 </li>
 </ol>
 <p>You can now expose services on the service network and those services are not accessible from other namespaces in the cluster.</p>
-<h5 id="applying-tls-to-tcp-or-http2-traffic-on-the-service-network">Applying TLS to TCP or HTTP2 traffic on the service network</h5>
+<h3 id="applying-tls-to-tcp-or-http2-traffic-on-the-service-network">Applying TLS to TCP or HTTP2 traffic on the service network</h3>
 <p>By default, the traffic between sites is encrypted, however the traffic between the service pod and the router pod is not encrypted.
 For services exposed as TCP or HTTP2, the traffic between the pod and the router pod can be encrypted using TLS.</p>
 <ul>
@@ -750,7 +758,7 @@ <h5 id="applying-tls-to-tcp-or-http2-traffic-on-the-service-network">Applying TL
 <li><p>Test calling the service from a TLS enabled frontend.</p>
 </li>
 </ol>
-<h5 id="supported-standards-and-protocols">Supported standards and protocols</h5>
+<h2 id="supported-standards-and-protocols">Supported standards and protocols</h2>
 <p>Skupper supports the following protocols for your service network:</p>
 <ul>
 <li>TCP - default</li>
@@ -776,7 +784,7 @@ <h5 id="supported-standards-and-protocols">Supported standards and protocols</h5
 <p>TCP is implemented as a single streamed message, whereas HTTP1 and HTTP2 are implemented as request/response message routing.</p>
 </li>
 </ul>
-<h6 id="cli-options">CLI options</h6>
+<h2 id="cli-options">CLI options</h2>
 <p>For a full list of options, see the <a href="../kubernetes-reference/index.html">Skupper Kubernetes CLI reference</a> and <a href="../podman-reference/index.html">Skupper Podman CLI reference</a> documentation.</p>
 <dl><dt><strong>⚠️ WARNING</strong></dt><dd>
 
@@ -823,7 +831,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/cli/native-security-options.html b/docs/docs/cli/native-security-options.html
index aab6fb53..2b72556c 100644
--- a/docs/docs/cli/native-security-options.html
+++ b/docs/docs/cli/native-security-options.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Skupper - Securing a service network</title>
+    <title>Skupper - #Securing a service network</title>
     <meta name="description" content="Multicluster communication for Kubernetes.  Skupper is a layer 7 service interconnect.  It enables secure communication across Kubernetes clusters with no VPNs or special firewall rules."/>
     <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
     <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic|Roboto+Mono:400,400italic|Alegreya+Sans:300,300italic,400,400italic,500,500italic,700,700italic;display=optional"/>
@@ -58,7 +58,7 @@
       </div>
     </div>
   </nav>
-  <nav id="-path-nav"><div><a href="/docs/index.html">Documentation</a> <span class="path-separator">&#8250;</span> <a href="/docs/cli/index.html">Using the Skupper CLI</a> <span class="path-separator">&#8250;</span> <a href="/docs/cli/native-security-options.html">Securing a service network</a></div></nav>
+  <nav id="-path-nav"><div><a href="/docs/index.html">Documentation</a> <span class="path-separator">&#8250;</span> <a href="/docs/cli/index.html">Using the Skupper CLI</a> <span class="path-separator">&#8250;</span> <a href="/docs/cli/native-security-options.html">#Securing a service network</a></div></nav>
   <nav id="-site-menu-layer" style="display: none;">
     <div>
       <a href="/index.html">Home</a>
@@ -75,11 +75,11 @@
   <div>
     <main>
 
-<h1 id="securing-a-service-network">Securing a service network</h1>
+<h2 id="securing-a-service-network">Securing a service network</h2>
 <p>Skupper provides default, built-in security that scales across clusters and clouds.
 This section describes additional security you can configure.</p>
 <p>See <a href="../policy/index.html">Securing a service network using policies</a> for information about creating granular policies for each cluster.</p>
-<h2 id="restricting-access-to-services-using-a-kubernetes-network-policy">Restricting access to services using a Kubernetes network policy</h2>
+<h3 id="restricting-access-to-services-using-a-kubernetes-network-policy">Restricting access to services using a Kubernetes network policy</h3>
 <p>By default, if you expose a service on the service network, that service is also accessible from other namespaces in the cluster.
 You can avoid this situation when creating a site using the <code>--create-network-policy</code> option.</p>
 <ol>
@@ -96,7 +96,7 @@ <h2 id="restricting-access-to-services-using-a-kubernetes-network-policy">Restri
 </li>
 </ol>
 <p>You can now expose services on the service network and those services are not accessible from other namespaces in the cluster.</p>
-<h2 id="applying-tls-to-tcp-or-http2-traffic-on-the-service-network">Applying TLS to TCP or HTTP2 traffic on the service network</h2>
+<h3 id="applying-tls-to-tcp-or-http2-traffic-on-the-service-network">Applying TLS to TCP or HTTP2 traffic on the service network</h3>
 <p>By default, the traffic between sites is encrypted, however the traffic between the service pod and the router pod is not encrypted.
 For services exposed as TCP or HTTP2, the traffic between the pod and the router pod can be encrypted using TLS.</p>
 <ul>
@@ -180,7 +180,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/cli/podman.html b/docs/docs/cli/podman.html
index 60fd9b9e..b0159013 100644
--- a/docs/docs/cli/podman.html
+++ b/docs/docs/cli/podman.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
-    <title>Skupper - Using Skupper podman</title>
+    <title>Skupper - Using Skupper Podman</title>
     <meta name="description" content="Multicluster communication for Kubernetes.  Skupper is a layer 7 service interconnect.  It enables secure communication across Kubernetes clusters with no VPNs or special firewall rules."/>
     <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
     <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic|Roboto+Mono:400,400italic|Alegreya+Sans:300,300italic,400,400italic,500,500italic,700,700italic;display=optional"/>
@@ -58,7 +58,7 @@
       </div>
     </div>
   </nav>
-  <nav id="-path-nav"><div><a href="/docs/index.html">Documentation</a> <span class="path-separator">&#8250;</span> <a href="/docs/cli/index.html">Using the Skupper CLI</a> <span class="path-separator">&#8250;</span> <a href="/docs/cli/podman.html">Using Skupper podman</a></div></nav>
+  <nav id="-path-nav"><div><a href="/docs/index.html">Documentation</a> <span class="path-separator">&#8250;</span> <a href="/docs/cli/index.html">Using the Skupper CLI</a> <span class="path-separator">&#8250;</span> <a href="/docs/cli/podman.html">Using Skupper Podman</a></div></nav>
   <nav id="-site-menu-layer" style="display: none;">
     <div>
       <a href="/index.html">Home</a>
@@ -75,22 +75,23 @@
   <div>
     <main>
 
-<h1 id="using-skupper-podman">Using Skupper podman</h1>
-<p>Skupper podman allows you to create a site using containers, without requiring Kubernetes.
-Typically, you create a site on a Linux host, allowing you to link to and from other sites, regardless of whether those sites are running in podman or Kubernetes.</p>
-<h2 id="about-skupper-podman">About Skupper podman</h2>
-<p>Skupper podman is available with the following precedence:</p>
+<h1 id="using-skupper-podman">Using Skupper Podman</h1>
+<p>Using the <code>skupper</code> command-line interface (CLI) allows you to create and manage Skupper sites from the context of the current Linux user.
+Skupper Podman allows you to create a site using containers, without requiring Kubernetes.</p>
+<p>A typical workflow is to create a site, link sites together, and expose services to the service network.</p>
+<h2 id="about-skupper-podman">About Skupper Podman</h2>
+<p>Skupper Podman is available with the following precedence:</p>
 <ul>
 <li><p><strong><code>skupper --platform podman &lt;command&gt;</code></strong><br />
-Use this option to avoid changing mode, for example, if you are working on Kubernetes and podman simultaneously.</p>
+Use this option to avoid changing mode, for example, if you are working on Kubernetes and Podman simultaneously.</p>
 </li>
 <li><p><strong><code>export SKUPPER_PLATFORM=podman</code></strong><br />
-Use this command to use Skupper podman for the current session, for example, if you have two terminals set to different contexts. To set the environment to target Kubernetes sites:</p>
+Use this command to use Skupper Podman for the current session, for example, if you have two terminals set to different contexts. To set the environment to target Kubernetes sites:</p>
 <pre><code class="language-bash">$ export SKUPPER_PLATFORM=kubernetes
 </code></pre>
 </li>
 <li><p><strong><code>skupper switch podman</code></strong><br />
-If you enter this command, all subsequent command target podman rather than Kubernetes for all terminal sessions.</p>
+If you enter this command, all subsequent command target Podman rather than Kubernetes for all terminal sessions.</p>
 </li>
 </ul>
 <p>To determine which mode is currently active:</p>
@@ -99,7 +100,19 @@ <h2 id="about-skupper-podman">About Skupper podman</h2>
 podman
 </code></pre>
 <p>To switch back to target Kubernetes sites: <code>skupper switch kubernetes</code></p>
+<dl><dt><strong>📌 NOTE</strong></dt><dd>
+
+<p>Services exposed on remote sites are not automatically available to Podman sites.
+This is the equivalent to Kubernetes sites created using <code>skupper init --enable-service-sync false</code>.</p>
+<p>To consume an exposed service on a Podman site, check that it exists using <code>skupper service status</code> on the original site and use that information to create the service on the Podman site:</p>
+<pre><code class="language-bash">$ skupper service create &lt;name&gt; &lt;port&gt;
+</code></pre>
+</dd></dl>
+
 <h2 id="creating-a-site-using-skupper-podman">Creating a site using Skupper podman</h2>
+<p>A service network consists of Skupper sites.
+This section describes how to create a site in on a Linux host using the default settings.
+See <a href="../cli/index.html">Using the Skupper CLI</a> for information about using the Skupper CLI to create Podman sites.</p>
 <ul>
 <li><p>The latest <code>skupper</code> CLI is installed.</p>
 </li>
@@ -115,7 +128,7 @@ <h2 id="creating-a-site-using-skupper-podman">Creating a site using Skupper podm
 <p>Use <code>systemctl --user enable --now podman.socket</code> to start the  Podman API Socket.</p>
 <p>See <a href="https://github.com/containers/podman/blob/main/docs/tutorials/socket_activation.md">Podman socket activation</a> for information about enabling this endpoint.</p>
 <ol>
-<li><p>Set your session to use Skupper podman:</p>
+<li><p>Set your session to use Skupper Podman:</p>
 <pre><code class="language-bash">$ export SKUPPER_PLATFORM=podman
 </code></pre>
 <p>To verify the <code>skupper</code> mode:</p>
@@ -126,18 +139,19 @@ <h2 id="creating-a-site-using-skupper-podman">Creating a site using Skupper podm
 </li>
 <li><p>Create a Skupper site:</p>
 <p>The simplest Skupper site allows you to link to other sites, but does not support linking <em>to</em> the current site.</p>
-<pre><code class="language-bash">$ skupper init --ingress none
+<pre><code class="language-bash">$ skupper init
 
 It is recommended to enable lingering for &lt;username&gt;, otherwise Skupper may not start on boot.
 Skupper is now installed for user '&lt;username&gt;'.  Use 'skupper status' to get more information.
 </code></pre>
-<p>If you require that other sites can link to the site you are creating:</p>
-<pre><code class="language-bash">$ skupper init --ingress-host &lt;machine-address&gt;
-
-It is recommended to enable lingering for &lt;username&gt;, otherwise Skupper may not start on boot.
-Skupper is now installed for user '&lt;username&gt;'.  Use 'skupper status' to get more information.
+<p>If you do not require that other sites can link to the site you are creating:</p>
+<pre><code class="language-bash">$ skupper init --ingress none
 </code></pre>
-<p>For more information, see the <a href="../podman-reference/index.html">Skupper Podman CLI reference</a> documentation.</p>
+<p>In this guide we assume you have enabled ingress using the first command.
+This allows you create tokens that allow links from every network interface on the host.</p>
+<p><strong>📌 NOTE</strong><br />
+When creating a token you can specify the ingress host.</p>
+<p>You can also restrict ingress to an IP address or hostname when initializing as described in the <a href="../podman-reference/index.html">Skupper Podman CLI reference</a> documentation.</p>
 </li>
 <li><p>Check the status of your site:</p>
 <pre><code class="language-bash">$ skupper status
@@ -149,12 +163,23 @@ <h2 id="creating-a-site-using-skupper-podman">Creating a site using Skupper podm
 </ol>
 </li>
 </ul>
-<h2 id="linking-sites-using-skupper-podman">Linking sites using Skupper podman</h2>
-<p>The general flow for linking podman sites is the same as for Kubernetes sites:</p>
+<h2 id="linking-sites-using-skupper-podman">Linking sites using Skupper Podman</h2>
+<p>A service network consists of Skupper sites.
+This section describes how to link sites to form a service network.</p>
+<p>Linking two sites requires a single initial directional connection. However:</p>
+<ul>
+<li>Communication between the two sites is bidirectional, only the initial linking is directional.</li>
+<li>The choice of direction for linking is typically determined by accessibility. For example, if you are linking a virtual machine running in the cloud with a Linux host running behind a firewall, you must link from the Linux host to the cloud virtual machine because that route is accessible.</li>
+</ul>
 <ol>
 <li><p>Generate a token on one site:</p>
 <pre><code class="language-bash">$ skupper token create &lt;filename&gt;
 </code></pre>
+<p>The <code>metadata</code> section of the resulting YAML file shows which interface is available for linking.</p>
+<p>To specify the interface, use <code>ifconfig</code> to determine the IP address of the interface you want to use.
+You can then specify that IP address when creating the token:</p>
+<pre><code class="language-bash">$ skupper token create &lt;filename&gt; --ingress-host &lt;IP Address&gt;
+</code></pre>
 </li>
 <li><p>Create a link from the other site:</p>
 <pre><code class="language-bash">$ skupper link create &lt;filename&gt;
@@ -164,76 +189,183 @@ <h2 id="linking-sites-using-skupper-podman">Linking sites using Skupper podman</
 <p>After you have linked to a network, you can check the link status:</p>
 <pre><code class="language-bash">$ skupper link status
 </code></pre>
-<h2 id="working-with-services-using-skupper-podman">Working with services using Skupper podman</h2>
-<p>The general flow for working with services is the same for Kubernetes and Podman sites.</p>
+<h2 id="specifying-link-cost">Specifying link cost</h2>
+<p>When linking sites, you can assign a cost to each link to influence the traffic flow.
+By default, link cost is set to <code>1</code> for a new link.
+In a service network, the routing algorithm attempts to use the path with the lowest total cost from client to target server.</p>
+<ul>
+<li><p>If you have services distributed across different sites, you might want a client to favor a particular target or link.
+In this case, you can specify a cost of greater than <code>1</code> on the alternative links to reduce the usage of those links.</p>
 <p><strong>📌 NOTE</strong><br />
-Services exposed on Kubernetes are not automatically available to Podman sites.
-This is the equivalent to Kubernetes sites created using <code>skupper init --enable-service-sync false</code>.</p>
-<p>In this variation of the <a href="https://github.com/skupperproject/skupper-example-hello-world">hello world</a> example, the <code>backend</code> service is exposed on Kubernetes site and a Podman site is linked.
-You deploy the <code>frontend</code> as a container and that container can access the <code>backend</code> service.</p>
-<ol>
-<li><p>Create a Podman site and link it to a Kubernetes site.</p>
+The distribution of open connections is statistical, that is, not a round robin system.</p>
 </li>
-<li><p>Check the service from the Podman site:</p>
-<pre><code class="language-bash">$ skupper service status
-
-No services defined
+<li><p>If a connection only traverses one link, then the path cost is equal to the link cost.
+If the connection traverses more than one link, the path cost is the sum of all the links involved in the path.</p>
+</li>
+<li><p>Cost acts as a threshold for using a path from client to server in the network.
+When there is only one path, traffic flows on that path regardless of cost.</p>
+<p><strong>📌 NOTE</strong><br />
+If you start with two targets for a service, and one of the targets is no longer available, traffic flows on the remaining path regardless of cost.</p>
+</li>
+<li><p>When there are a number of paths from a client to server instances or a service, traffic flows on the lowest cost path until the number of connections exceeds the cost of an alternative path.
+After this threshold of open connections is reached, new connections are spread across the alternative path and the lowest cost path.</p>
+</li>
+<li><p>You have set your Kubernetes context to a site that you want to link <em>from</em>.</p>
+</li>
+<li><p>A token for the site that you want to link <em>to</em>.</p>
+</li>
+</ul>
+<ol>
+<li><p>Create a link to the service network:</p>
+<pre><code class="language-bash">$ skupper link create &lt;filename&gt; --cost &lt;integer-cost&gt;
+</code></pre>
+<p>where <code>&lt;integer-cost&gt;</code> is an integer greater than 1 and traffic favors lower cost links.</p>
+<p><strong>📌 NOTE</strong><br />
+If a service can be called without traversing a link, that service is considered local, with an implicit cost of <code>0</code>.</p>
+<p>For example, create a link with cost set to <code>2</code> using a token file named <code>token.yaml</code>:</p>
+<pre><code class="language-bash">$ skupper link create token.yaml --cost 2
 </code></pre>
-<p>This result is expected because services exposed on Kubernetes are not automatically available to Podman sites.</p>
 </li>
-<li><p>Create a service on the Podman site matching the service exposed on the Kubernetes site:</p>
-<pre><code class="language-bash">$ skupper service create backend 8080
+<li><p>Check the link cost:</p>
+<pre><code class="language-bash">$ skupper link status link1 --verbose
+</code></pre>
+<p>The output is similar to the following:</p>
+<pre><code class="language-bash"> Cost:          2
+ Created:       2022-11-17 15:02:01 +0000 GMT
+ Name:          link1
+ Namespace:     default
+ Site:          default-0d99d031-cee2-4cc6-a761-697fe0f76275
+ Status:        Connected
 </code></pre>
 </li>
-<li><p>Validate the service from the Podman site by checking the backend API health URL:</p>
-<pre><code class="language-bash">$ podman run -it --rm --network=skupper --name=myubi ubi8/ubi curl backend:8080/api/health
-
-OK
+<li><p>Observe traffic using the console.</p>
+<p>If you have a console on a site, log in and navigate to the processes for each server.
+You can view the traffic levels corresponding to each client.</p>
+<p><strong>📌 NOTE</strong><br />
+If there are multiple clients on different sites, filter the view to each client to determine the effect of cost on traffic.
+For example, in a two site network linked with a high cost with servers and clients on both sites, you can see that a client is served by the local servers while a local server is available.</p>
+</li>
+</ol>
+<h2 id="exposing-services-on-the-service-network-from-a-linux-host">Exposing services on the service network from a Linux host</h2>
+<p>After creating a service network, exposed services can communicate across that network.</p>
+<p>The general flow for working with services is the same for Kubernetes and Podman sites.</p>
+<p>The <code>skupper</code> CLI has two options for exposing services that already exist on a host:</p>
+<ul>
+<li><code>expose</code> supports simple use cases, for example, a host with a single service.
+See <a href="#exposing-simple-services-on-the-service-network">Exposing simple services on the service network</a> for instructions.</li>
+<li><code>service create</code> and <code>service bind</code> is a more flexible method of exposing services, for example, if you have multiple services for a host.
+See <a href="#exposing-complex-services-on-the-service-network">Exposing complex services on the service network</a> for instructions.</li>
+</ul>
+<h3 id="exposing-simple-services-on-the-service-network">Exposing simple services on the service network</h3>
+<p>This section describes how services can be enabled for a service network for simple use cases.</p>
+<ul>
+<li>A Skupper Podman site</li>
+</ul>
+<ol>
+<li><p>Run a server, for example:</p>
+<pre><code class="language-bash">$ podman run --name backend-target --network skupper --detach --rm -p 8080:8080 quay.io/skupper/hello-world-backend
 </code></pre>
-<p>This command runs a container using the <code>skupper</code> network and returns the results from <code>http://backend:8080/api/health</code></p>
+<p>This step is not Skupper-specific, that is, this process is unchanged from standard processes for your host.</p>
 </li>
-<li><p>Run the frontend as a container:</p>
-<pre><code class="language-bash">$ podman run -dp 8080:8080 --name hello-world-frontend --network skupper quay.io/skupper/hello-world-frontend
+<li><p>Create a service that can communicate on the service network:</p>
+<pre><code class="language-bash">$ skupper expose [host &lt;hostname|ip&gt;]
+</code></pre>
+<p>where</p>
+<ul>
+<li><code>&lt;host&gt;</code> is the name of the host where the server is running.
+For example, the name of the container if you run the server as a container.</li>
+<li><code>&lt;ip&gt;</code> is the IP address where the server is running</li>
+</ul>
+<p>For the example deployment in step 1, you create a service using the following command:</p>
+<pre><code>$ skupper expose host backend-target --address backend --port 8080
 </code></pre>
+<p>Options for this command include:</p>
+<ul>
+<li><code>--port &lt;port-number&gt;</code>:: Specify the port number that this service is available on the service network.
+NOTE: You can specify more than one port by repeating this option.</li>
+<li><code>--target-port &lt;port-number&gt;</code>:: Specify the port number of pods that you want to expose.</li>
+<li><code>--protocol &lt;protocol&gt;</code> allows you specify the protocol you want to use, <code>tcp</code>, <code>http</code> or <code>http2</code></li>
+</ul>
 </li>
-<li><p>Check your service network is working as expected by navigating to http://localhost:8080 and click <strong>Say hello</strong>.</p>
-<p>Each of the backend replicas respond, for example <code>Hi, Perfect Parrot. I am Kind Hearted Component (backend-7c84887f9f-wxhxp).</code></p>
-<dl><dt><strong>📌 NOTE</strong></dt><dd>
-
-<p>In this scenario, running the <code>skupper service status</code> command on the Podman site does not provide much detail about the service:</p>
-<pre><code class="language-bash">$ skupper service status
-Services exposed through Skupper:
-╰─ backend (tcp port 8080)
+<li><p>Create the service on another site in the service network:</p>
+<pre><code class="language-bash">$ skupper service create backend 8080
 </code></pre>
-</dd></dl>
-
 </li>
 </ol>
-<p>In this variation of the <a href="https://github.com/skupperproject/skupper-example-hello-world">hello world</a> example, the <code>backend</code> service is exposed on Podman site and consumed from a <code>frontend</code> on a Kubernetes site.</p>
+<h3 id="exposing-complex-services-on-the-service-network">Exposing complex services on the service network</h3>
+<p>This section describes how services can be enabled for a service network for more complex use cases.</p>
+<ul>
+<li>A Skupper Podman site</li>
+</ul>
 <ol>
-<li><p>Create a Podman site and link it to a Kubernetes site.</p>
+<li><p>Run a server, for example:</p>
+<pre><code class="language-bash">$ podman run --name backend-target --network skupper --detach --rm -p 8080:8080 quay.io/skupper/hello-world-backend
+</code></pre>
+<p>This step is not Skupper-specific, that is, this process is unchanged from standard processes for your host.</p>
 </li>
-<li><p>Create and expose a frontend deployment on the Kubernetes site:</p>
-<pre><code class="language-bash">$ kubectl create deployment frontend --image quay.io/skupper/hello-world-frontend
-$ kubectl expose deployment/frontend --port 8080 --type LoadBalancer
+<li><p>Create a service that can communicate on the service network:</p>
+<pre><code class="language-bash">$ skupper service create &lt;name&gt; &lt;port&gt;
+</code></pre>
+<p>where</p>
+<ul>
+<li><code>&lt;name&gt;</code> is the name of the service you want to create</li>
+<li><code>&lt;port&gt;</code> is the port the service uses</li>
+</ul>
+<p>For the example deployment in step 1, you create a service using the following command:</p>
+<pre><code class="language-bash">$ skupper service create hello-world-backend 8080
 </code></pre>
 </li>
-<li><p>Run the backend as a container:</p>
-<pre><code class="language-bash">$ podman run -d --name hello-world-backend --network skupper quay.io/skupper/hello-world-backend
+<li><p>Bind the service to a cluster service:</p>
+<pre><code class="language-bash">$ skupper service bind &lt;service-name&gt; &lt;target-type&gt; &lt;target-name&gt;
 </code></pre>
+<p>where</p>
+<ul>
+<li><code>&lt;service-name&gt;</code> is the name of the service on the service network</li>
+<li><code>&lt;target-type&gt;</code> is the object you want to expose, <code>host</code> is the only current valid value.</li>
+<li><code>&lt;target-name&gt;</code> is the name of the cluster service</li>
+</ul>
+<p>For the example deployment in step 1, you bind the service using the following command:</p>
+<pre><code class="language-bash">$ skupper service bind hello-world-backend host hello-world-backend
+</code></pre>
+</li>
+</ol>
+<h3 id="consuming-simple-services-from-the-service-network">Consuming simple services from the service network</h3>
+<p>Services exposed on Podman sites are not automatically available to other sites.
+This is the equivalent to Kubernetes sites created using <code>skupper init --enable-service-sync false</code>.</p>
+<ul>
+<li>A remote site where a service is exposed on the service network</li>
+<li>A Podman site</li>
+</ul>
+<ol>
+<li><p>Log into the host as the user associated with the Skupper site.</p>
 </li>
-<li><p>Expose the <code>backend</code> from the Podman site.</p>
-<pre><code class="language-bash">$ skupper expose host hello-world-backend --address backend --port 8080
+<li><p>Create the local service:</p>
+<pre><code class="language-bash">$ skupper service create &lt;service-name&gt; &lt;port number&gt;
 </code></pre>
 </li>
-<li><p>From the Kubernetes site, create the <code>backend</code> service:</p>
-<pre><code class="language-bash">$ skupper service create backend 8080
+</ol>
+<h2 id="deleting-a-podman-site">Deleting a Podman site</h2>
+<p>When you no longer want the Linux host to be part of the service network, you can delete the site.</p>
+<dl><dt><strong>📌 NOTE</strong></dt><dd>
+
+<p>This procedure removes all containers, volumes and networks labeled <code>application=skupper</code>.</p>
+<p>To check the labels associated with running containers:</p>
+<pre><code class="language-bash">$ podman ps -a --format &quot;{{.ID}}  {{.Image}}  {{.Labels}}&quot;
+</code></pre>
+</dd></dl>
+
+<ol>
+<li><p>Make sure you are logged in as the user that created the site:</p>
+<pre><code class="language-bash">$ skupper status
+Skupper is enabled for &quot;&lt;username&gt;&quot; with site name &quot;&lt;machine-name&gt;-&lt;username&gt;&quot;.
 </code></pre>
 </li>
-<li><p>Check your service network is working as expected by navigating to your cluster URL, port 8080, and clicking <strong>Say hello</strong>.</p>
+<li><p>Delete the site and all podman resources (containers, volumes and networks) labeled with &quot;application=skupper&quot;:</p>
+<pre><code class="language-bash">$ skupper delete
+Skupper is now removed for user &quot;&lt;username&gt;&quot;.
+</code></pre>
 </li>
 </ol>
-<p>For more information, see the <a href="../podman-reference/index.html">Skupper Podman CLI reference</a> documentation.</p>
 
 
     </main>
@@ -257,7 +389,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/cli/tokens.html b/docs/docs/cli/tokens.html
index 700518e6..7b1633c9 100644
--- a/docs/docs/cli/tokens.html
+++ b/docs/docs/cli/tokens.html
@@ -209,7 +209,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/console/index.html b/docs/docs/console/index.html
index 8124c3fe..2084068d 100644
--- a/docs/docs/console/index.html
+++ b/docs/docs/console/index.html
@@ -186,7 +186,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/index.html b/docs/docs/index.html
index 7d23feac..267633b0 100644
--- a/docs/docs/index.html
+++ b/docs/docs/index.html
@@ -192,7 +192,7 @@ <h2>Blog posts, articles, and videos</h2>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/index.html b/docs/docs/kubernetes-reference/index.html
index d9d55789..c3b4eef8 100644
--- a/docs/docs/kubernetes-reference/index.html
+++ b/docs/docs/kubernetes-reference/index.html
@@ -127,7 +127,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_completion.html b/docs/docs/kubernetes-reference/skupper_completion.html
index ecaee4c7..cd7e02ad 100644
--- a/docs/docs/kubernetes-reference/skupper_completion.html
+++ b/docs/docs/kubernetes-reference/skupper_completion.html
@@ -122,7 +122,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_debug.html b/docs/docs/kubernetes-reference/skupper_debug.html
index 177a685e..b7dee58e 100644
--- a/docs/docs/kubernetes-reference/skupper_debug.html
+++ b/docs/docs/kubernetes-reference/skupper_debug.html
@@ -121,7 +121,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_debug_dump.html b/docs/docs/kubernetes-reference/skupper_debug_dump.html
index 547874de..4203e9da 100644
--- a/docs/docs/kubernetes-reference/skupper_debug_dump.html
+++ b/docs/docs/kubernetes-reference/skupper_debug_dump.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_debug_events.html b/docs/docs/kubernetes-reference/skupper_debug_events.html
index 846305fb..1f8713f6 100644
--- a/docs/docs/kubernetes-reference/skupper_debug_events.html
+++ b/docs/docs/kubernetes-reference/skupper_debug_events.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_debug_policies.html b/docs/docs/kubernetes-reference/skupper_debug_policies.html
index d4913b09..ac43e243 100644
--- a/docs/docs/kubernetes-reference/skupper_debug_policies.html
+++ b/docs/docs/kubernetes-reference/skupper_debug_policies.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_debug_service.html b/docs/docs/kubernetes-reference/skupper_debug_service.html
index 2eacdff2..8d615579 100644
--- a/docs/docs/kubernetes-reference/skupper_debug_service.html
+++ b/docs/docs/kubernetes-reference/skupper_debug_service.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_delete.html b/docs/docs/kubernetes-reference/skupper_delete.html
index e2124295..daee59c0 100644
--- a/docs/docs/kubernetes-reference/skupper_delete.html
+++ b/docs/docs/kubernetes-reference/skupper_delete.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_expose.html b/docs/docs/kubernetes-reference/skupper_expose.html
index 51ef70e2..4827e3d9 100644
--- a/docs/docs/kubernetes-reference/skupper_expose.html
+++ b/docs/docs/kubernetes-reference/skupper_expose.html
@@ -140,7 +140,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway.html b/docs/docs/kubernetes-reference/skupper_gateway.html
index 4b16fb03..18448679 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway.html
@@ -128,7 +128,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_bind.html b/docs/docs/kubernetes-reference/skupper_gateway_bind.html
index 675307fd..0f491f10 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_bind.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_bind.html
@@ -121,7 +121,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_delete.html b/docs/docs/kubernetes-reference/skupper_gateway_delete.html
index e0d9f26a..ac2329c8 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_delete.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_delete.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_export-config.html b/docs/docs/kubernetes-reference/skupper_gateway_export-config.html
index 60ee133c..6e9eea54 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_export-config.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_export-config.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_expose.html b/docs/docs/kubernetes-reference/skupper_gateway_expose.html
index e843d990..ff025d2d 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_expose.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_expose.html
@@ -123,7 +123,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_forward.html b/docs/docs/kubernetes-reference/skupper_gateway_forward.html
index bce00835..f565091e 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_forward.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_forward.html
@@ -122,7 +122,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_generate-bundle.html b/docs/docs/kubernetes-reference/skupper_gateway_generate-bundle.html
index 67d8d435..5a2a16b0 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_generate-bundle.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_generate-bundle.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_init.html b/docs/docs/kubernetes-reference/skupper_gateway_init.html
index a1ed5a71..196b6115 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_init.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_init.html
@@ -121,7 +121,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_status.html b/docs/docs/kubernetes-reference/skupper_gateway_status.html
index 2c652206..155ded9d 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_status.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_status.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_unbind.html b/docs/docs/kubernetes-reference/skupper_gateway_unbind.html
index 462488ca..03087387 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_unbind.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_unbind.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_unexpose.html b/docs/docs/kubernetes-reference/skupper_gateway_unexpose.html
index b76d2a43..4f249376 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_unexpose.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_unexpose.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_gateway_unforward.html b/docs/docs/kubernetes-reference/skupper_gateway_unforward.html
index fb46da53..20404cb8 100644
--- a/docs/docs/kubernetes-reference/skupper_gateway_unforward.html
+++ b/docs/docs/kubernetes-reference/skupper_gateway_unforward.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_init.html b/docs/docs/kubernetes-reference/skupper_init.html
index 9606e4ac..f04c2b35 100644
--- a/docs/docs/kubernetes-reference/skupper_init.html
+++ b/docs/docs/kubernetes-reference/skupper_init.html
@@ -179,7 +179,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_link.html b/docs/docs/kubernetes-reference/skupper_link.html
index 91c1066e..4e44ab33 100644
--- a/docs/docs/kubernetes-reference/skupper_link.html
+++ b/docs/docs/kubernetes-reference/skupper_link.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_link_create.html b/docs/docs/kubernetes-reference/skupper_link_create.html
index b923cc1a..d16c0181 100644
--- a/docs/docs/kubernetes-reference/skupper_link_create.html
+++ b/docs/docs/kubernetes-reference/skupper_link_create.html
@@ -121,7 +121,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_link_delete.html b/docs/docs/kubernetes-reference/skupper_link_delete.html
index 666b88ec..888cac23 100644
--- a/docs/docs/kubernetes-reference/skupper_link_delete.html
+++ b/docs/docs/kubernetes-reference/skupper_link_delete.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_link_status.html b/docs/docs/kubernetes-reference/skupper_link_status.html
index 4028b756..a122de5e 100644
--- a/docs/docs/kubernetes-reference/skupper_link_status.html
+++ b/docs/docs/kubernetes-reference/skupper_link_status.html
@@ -121,7 +121,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_network.html b/docs/docs/kubernetes-reference/skupper_network.html
index ff872546..7b8ecc61 100644
--- a/docs/docs/kubernetes-reference/skupper_network.html
+++ b/docs/docs/kubernetes-reference/skupper_network.html
@@ -118,7 +118,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_network_status.html b/docs/docs/kubernetes-reference/skupper_network_status.html
index bc9053fe..f4317d3b 100644
--- a/docs/docs/kubernetes-reference/skupper_network_status.html
+++ b/docs/docs/kubernetes-reference/skupper_network_status.html
@@ -121,7 +121,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_revoke-access.html b/docs/docs/kubernetes-reference/skupper_revoke-access.html
index 5bd5a8d8..074e4116 100644
--- a/docs/docs/kubernetes-reference/skupper_revoke-access.html
+++ b/docs/docs/kubernetes-reference/skupper_revoke-access.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_service.html b/docs/docs/kubernetes-reference/skupper_service.html
index abed3785..6ef1edc2 100644
--- a/docs/docs/kubernetes-reference/skupper_service.html
+++ b/docs/docs/kubernetes-reference/skupper_service.html
@@ -123,7 +123,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_service_bind.html b/docs/docs/kubernetes-reference/skupper_service_bind.html
index 8cc07672..c02f0468 100644
--- a/docs/docs/kubernetes-reference/skupper_service_bind.html
+++ b/docs/docs/kubernetes-reference/skupper_service_bind.html
@@ -131,7 +131,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_service_create.html b/docs/docs/kubernetes-reference/skupper_service_create.html
index 6c7013d6..1506a307 100644
--- a/docs/docs/kubernetes-reference/skupper_service_create.html
+++ b/docs/docs/kubernetes-reference/skupper_service_create.html
@@ -126,7 +126,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_service_delete.html b/docs/docs/kubernetes-reference/skupper_service_delete.html
index 0059607f..2f57c51e 100644
--- a/docs/docs/kubernetes-reference/skupper_service_delete.html
+++ b/docs/docs/kubernetes-reference/skupper_service_delete.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_service_label.html b/docs/docs/kubernetes-reference/skupper_service_label.html
index 0b772cec..77061c06 100644
--- a/docs/docs/kubernetes-reference/skupper_service_label.html
+++ b/docs/docs/kubernetes-reference/skupper_service_label.html
@@ -130,7 +130,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_service_status.html b/docs/docs/kubernetes-reference/skupper_service_status.html
index 10375d24..8217f985 100644
--- a/docs/docs/kubernetes-reference/skupper_service_status.html
+++ b/docs/docs/kubernetes-reference/skupper_service_status.html
@@ -121,7 +121,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_service_unbind.html b/docs/docs/kubernetes-reference/skupper_service_unbind.html
index d098ab62..c9d06bd4 100644
--- a/docs/docs/kubernetes-reference/skupper_service_unbind.html
+++ b/docs/docs/kubernetes-reference/skupper_service_unbind.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_status.html b/docs/docs/kubernetes-reference/skupper_status.html
index a3e20233..ce195c73 100644
--- a/docs/docs/kubernetes-reference/skupper_status.html
+++ b/docs/docs/kubernetes-reference/skupper_status.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_token.html b/docs/docs/kubernetes-reference/skupper_token.html
index 86c8f265..149ea22c 100644
--- a/docs/docs/kubernetes-reference/skupper_token.html
+++ b/docs/docs/kubernetes-reference/skupper_token.html
@@ -118,7 +118,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_token_create.html b/docs/docs/kubernetes-reference/skupper_token_create.html
index 8e6c358e..6ac8a9f9 100644
--- a/docs/docs/kubernetes-reference/skupper_token_create.html
+++ b/docs/docs/kubernetes-reference/skupper_token_create.html
@@ -124,7 +124,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_unexpose.html b/docs/docs/kubernetes-reference/skupper_unexpose.html
index 2758d4ac..4ab59d19 100644
--- a/docs/docs/kubernetes-reference/skupper_unexpose.html
+++ b/docs/docs/kubernetes-reference/skupper_unexpose.html
@@ -121,7 +121,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_update.html b/docs/docs/kubernetes-reference/skupper_update.html
index abcea12f..20ec95ab 100644
--- a/docs/docs/kubernetes-reference/skupper_update.html
+++ b/docs/docs/kubernetes-reference/skupper_update.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_version.html b/docs/docs/kubernetes-reference/skupper_version.html
index ecd810a9..fd96d9e2 100644
--- a/docs/docs/kubernetes-reference/skupper_version.html
+++ b/docs/docs/kubernetes-reference/skupper_version.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes-reference/skupper_version_manifest.html b/docs/docs/kubernetes-reference/skupper_version_manifest.html
index d54ac677..4f0e17db 100644
--- a/docs/docs/kubernetes-reference/skupper_version_manifest.html
+++ b/docs/docs/kubernetes-reference/skupper_version_manifest.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/kubernetes/deployment-concerns.html b/docs/docs/kubernetes/deployment-concerns.html
index c391f3c6..731051d7 100644
--- a/docs/docs/kubernetes/deployment-concerns.html
+++ b/docs/docs/kubernetes/deployment-concerns.html
@@ -91,9 +91,8 @@ <h2 id="scaling-for-increased-traffic">Scaling for increased traffic</h2>
 <li><p>Determine the router CPU allocation you require.</p>
 <p>By default, the router CPU allocation is <code>BestEffort</code> as described in <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#besteffort">Pod Quality of Service Classes</a>.</p>
 <p>Consider the following CPU allocation options:</p>
-<p>|     |     |
+<p>| Router CPU | Description |
 | --- | --- |
-| Router CPU | Description |
 | 1 | Helps avoid issues with <code>BestEffort</code> on low resource clusters |
 | 2 | Suitable for production environments |
 | 5 | Maximum performance |</p>
@@ -159,7 +158,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/operator/index.html b/docs/docs/operator/index.html
index 70d04388..8c1ebe30 100644
--- a/docs/docs/operator/index.html
+++ b/docs/docs/operator/index.html
@@ -196,7 +196,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/overview/connectivity.html b/docs/docs/overview/connectivity.html
index 4ef6bd6e..0b3f4a3f 100644
--- a/docs/docs/overview/connectivity.html
+++ b/docs/docs/overview/connectivity.html
@@ -129,7 +129,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/overview/glossary.html b/docs/docs/overview/glossary.html
index f799a95a..f382c9d4 100644
--- a/docs/docs/overview/glossary.html
+++ b/docs/docs/overview/glossary.html
@@ -114,7 +114,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/overview/index.html b/docs/docs/overview/index.html
index 25a5d041..2f65e0eb 100644
--- a/docs/docs/overview/index.html
+++ b/docs/docs/overview/index.html
@@ -110,9 +110,9 @@ <h2 id="skupper">Skupper</h2>
 <p>Once a Skupper network is formed across Kubernetes namespaces, any of the services in those namespaces can be exposed (through annotation) to the Skupper network.
 When a service is exposed, Skupper creates proxy endpoints to make that service available on each namespace in the Skupper network.</p>
 <ul>
-<li>link:{security-link}</li>
-<li>link:{routing-link}</li>
-<li>link:{connectivity-link}</li>
+<li><a href="../overview/security.html">Security</a></li>
+<li><a href="../overview/routing.html">Routing</a></li>
+<li><a href="../overview/connectivity.html">Connectivity</a></li>
 </ul>
 
 
@@ -137,7 +137,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/overview/resources.html b/docs/docs/overview/resources.html
index a05ac357..464b9b3f 100644
--- a/docs/docs/overview/resources.html
+++ b/docs/docs/overview/resources.html
@@ -175,7 +175,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/overview/routing.html b/docs/docs/overview/routing.html
index ac1eba74..2b597342 100644
--- a/docs/docs/overview/routing.html
+++ b/docs/docs/overview/routing.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/overview/security.html b/docs/docs/overview/security.html
index bd246913..1fe87ffd 100644
--- a/docs/docs/overview/security.html
+++ b/docs/docs/overview/security.html
@@ -117,7 +117,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/index.html b/docs/docs/podman-reference/index.html
index d3603b5a..4da2357f 100644
--- a/docs/docs/podman-reference/index.html
+++ b/docs/docs/podman-reference/index.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_delete.html b/docs/docs/podman-reference/skupper_delete.html
index 71823396..baf8f19f 100644
--- a/docs/docs/podman-reference/skupper_delete.html
+++ b/docs/docs/podman-reference/skupper_delete.html
@@ -116,7 +116,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_expose.html b/docs/docs/podman-reference/skupper_expose.html
index 6fc88a62..287fa65e 100644
--- a/docs/docs/podman-reference/skupper_expose.html
+++ b/docs/docs/podman-reference/skupper_expose.html
@@ -139,7 +139,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_init.html b/docs/docs/podman-reference/skupper_init.html
index eb0a5832..199d9cbe 100644
--- a/docs/docs/podman-reference/skupper_init.html
+++ b/docs/docs/podman-reference/skupper_init.html
@@ -139,7 +139,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_link.html b/docs/docs/podman-reference/skupper_link.html
index 28d2a47e..c2950a83 100644
--- a/docs/docs/podman-reference/skupper_link.html
+++ b/docs/docs/podman-reference/skupper_link.html
@@ -117,7 +117,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_link_create.html b/docs/docs/podman-reference/skupper_link_create.html
index 8d6b488b..29dd80b1 100644
--- a/docs/docs/podman-reference/skupper_link_create.html
+++ b/docs/docs/podman-reference/skupper_link_create.html
@@ -118,7 +118,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_link_delete.html b/docs/docs/podman-reference/skupper_link_delete.html
index ecb5cafb..eae9bd50 100644
--- a/docs/docs/podman-reference/skupper_link_delete.html
+++ b/docs/docs/podman-reference/skupper_link_delete.html
@@ -116,7 +116,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_link_status.html b/docs/docs/podman-reference/skupper_link_status.html
index 09686a87..77ff9b64 100644
--- a/docs/docs/podman-reference/skupper_link_status.html
+++ b/docs/docs/podman-reference/skupper_link_status.html
@@ -118,7 +118,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_revoke-access.html b/docs/docs/podman-reference/skupper_revoke-access.html
index 03f6f1bd..fb3722de 100644
--- a/docs/docs/podman-reference/skupper_revoke-access.html
+++ b/docs/docs/podman-reference/skupper_revoke-access.html
@@ -117,7 +117,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_service.html b/docs/docs/podman-reference/skupper_service.html
index bae93f72..6b83d17d 100644
--- a/docs/docs/podman-reference/skupper_service.html
+++ b/docs/docs/podman-reference/skupper_service.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_service_bind.html b/docs/docs/podman-reference/skupper_service_bind.html
index 795da22f..0a638cf2 100644
--- a/docs/docs/podman-reference/skupper_service_bind.html
+++ b/docs/docs/podman-reference/skupper_service_bind.html
@@ -118,7 +118,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_service_create.html b/docs/docs/podman-reference/skupper_service_create.html
index e6e9d858..24e6d786 100644
--- a/docs/docs/podman-reference/skupper_service_create.html
+++ b/docs/docs/podman-reference/skupper_service_create.html
@@ -127,7 +127,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_service_delete.html b/docs/docs/podman-reference/skupper_service_delete.html
index 32a270a7..c6528561 100644
--- a/docs/docs/podman-reference/skupper_service_delete.html
+++ b/docs/docs/podman-reference/skupper_service_delete.html
@@ -116,7 +116,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_service_status.html b/docs/docs/podman-reference/skupper_service_status.html
index a5f498ec..d6510dd6 100644
--- a/docs/docs/podman-reference/skupper_service_status.html
+++ b/docs/docs/podman-reference/skupper_service_status.html
@@ -117,7 +117,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_service_unbind.html b/docs/docs/podman-reference/skupper_service_unbind.html
index e6d86544..4de94b18 100644
--- a/docs/docs/podman-reference/skupper_service_unbind.html
+++ b/docs/docs/podman-reference/skupper_service_unbind.html
@@ -116,7 +116,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_status.html b/docs/docs/podman-reference/skupper_status.html
index e1bfc9e3..179ce061 100644
--- a/docs/docs/podman-reference/skupper_status.html
+++ b/docs/docs/podman-reference/skupper_status.html
@@ -117,7 +117,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_token.html b/docs/docs/podman-reference/skupper_token.html
index fcb8578d..836f3d21 100644
--- a/docs/docs/podman-reference/skupper_token.html
+++ b/docs/docs/podman-reference/skupper_token.html
@@ -115,7 +115,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_token_create.html b/docs/docs/podman-reference/skupper_token_create.html
index 48c23cc2..98b568c7 100644
--- a/docs/docs/podman-reference/skupper_token_create.html
+++ b/docs/docs/podman-reference/skupper_token_create.html
@@ -118,7 +118,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_unexpose.html b/docs/docs/podman-reference/skupper_unexpose.html
index 62fd62b3..2cabcc2f 100644
--- a/docs/docs/podman-reference/skupper_unexpose.html
+++ b/docs/docs/podman-reference/skupper_unexpose.html
@@ -128,7 +128,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_update.html b/docs/docs/podman-reference/skupper_update.html
index 9bd27ff6..f7bd627b 100644
--- a/docs/docs/podman-reference/skupper_update.html
+++ b/docs/docs/podman-reference/skupper_update.html
@@ -119,7 +119,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_version.html b/docs/docs/podman-reference/skupper_version.html
index fca316fd..387f5e02 100644
--- a/docs/docs/podman-reference/skupper_version.html
+++ b/docs/docs/podman-reference/skupper_version.html
@@ -117,7 +117,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/podman-reference/skupper_version_manifest.html b/docs/docs/podman-reference/skupper_version_manifest.html
index f1816a33..13bba608 100644
--- a/docs/docs/podman-reference/skupper_version_manifest.html
+++ b/docs/docs/podman-reference/skupper_version_manifest.html
@@ -116,7 +116,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/policy/index.html b/docs/docs/policy/index.html
index 84b33f55..c888bed6 100644
--- a/docs/docs/policy/index.html
+++ b/docs/docs/policy/index.html
@@ -333,7 +333,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/troubleshooting/index.html b/docs/docs/troubleshooting/index.html
index fe5cbbba..05c3a422 100644
--- a/docs/docs/troubleshooting/index.html
+++ b/docs/docs/troubleshooting/index.html
@@ -183,12 +183,12 @@ <h2 id="checking-sites">Checking sites</h2>
 However, this output is most useful when reporting an issue and is included in the Skupper debug tar file.</p>
 </li>
 <li><p>List the Kubernetes events for a site:</p>
-<pre><code class="language-bash">kubectl get events | grep &quot;service/skupper&quot;
-10m         Normal    ServiceSyncEvent               service/skupper                                   Service sync receiver connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
-10m         Normal    ServiceSyncEvent               service/skupper                                   Service sync sender connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
-10m         Normal    ServiceControllerCreateEvent   service/skupper                                   Creating service productcatalogservice
-7m59s       Normal    TokenHandler                   service/skupper                                   Connecting using token link1
-7m54s       Normal    TokenHandler                   service/skupper                                   Connecting using token link2
+<pre><code class="language-bash">kubectl get events | grep &quot;deployment/skupper-service-controller&quot;
+10m         Normal    ServiceSyncEvent               deployment/skupper-service-controller   Service sync receiver connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
+10m         Normal    ServiceSyncEvent               deployment/skupper-service-controller   Service sync sender connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
+10m         Normal    ServiceControllerCreateEvent   deployment/skupper-service-controller   Creating service productcatalogservice
+7m59s       Normal    TokenHandler                   deployment/skupper-service-controller   Connecting using token link1
+7m54s       Normal    TokenHandler                   deployment/skupper-service-controller   Connecting using token link2
 </code></pre>
 <p>The output shows events relating to Kubernetes resources.</p>
 </li>
@@ -466,7 +466,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/docs/yaml/index.html b/docs/docs/yaml/index.html
index 22662f03..9b0bee9e 100644
--- a/docs/docs/yaml/index.html
+++ b/docs/docs/yaml/index.html
@@ -638,7 +638,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/examples/index.html b/docs/examples/index.html
index 8beaa76d..fd5346e9 100644
--- a/docs/examples/index.html
+++ b/docs/examples/index.html
@@ -424,7 +424,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/index.html b/docs/index.html
index eb3a20ae..07c1ed33 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -431,7 +431,7 @@ <h2>A multi-cluster microservices app</h2>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/install/index.html b/docs/install/index.html
index 5d90d4ac..2f243985 100644
--- a/docs/install/index.html
+++ b/docs/install/index.html
@@ -163,7 +163,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/install/troubleshooting.html b/docs/install/troubleshooting.html
index 6343ff2b..52063882 100644
--- a/docs/install/troubleshooting.html
+++ b/docs/install/troubleshooting.html
@@ -130,7 +130,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/releases/index.html b/docs/releases/index.html
index 7943752f..43566a7b 100644
--- a/docs/releases/index.html
+++ b/docs/releases/index.html
@@ -161,7 +161,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/site.html b/docs/site.html
index 531729c2..8f584233 100644
--- a/docs/site.html
+++ b/docs/site.html
@@ -127,7 +127,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/start/aks.html b/docs/start/aks.html
index 43985d85..df3d5487 100644
--- a/docs/start/aks.html
+++ b/docs/start/aks.html
@@ -120,7 +120,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/start/eks.html b/docs/start/eks.html
index 4ffa40e9..de4d86a0 100644
--- a/docs/start/eks.html
+++ b/docs/start/eks.html
@@ -112,7 +112,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/start/gke.html b/docs/start/gke.html
index 075f9514..770e446e 100644
--- a/docs/start/gke.html
+++ b/docs/start/gke.html
@@ -129,7 +129,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/start/ibmks.html b/docs/start/ibmks.html
index c2c6951d..e701ba34 100644
--- a/docs/start/ibmks.html
+++ b/docs/start/ibmks.html
@@ -143,7 +143,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/start/index.html b/docs/start/index.html
index f39635bd..5368ab2e 100644
--- a/docs/start/index.html
+++ b/docs/start/index.html
@@ -402,7 +402,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/start/kubernetes.html b/docs/start/kubernetes.html
index 60844c88..780de07f 100644
--- a/docs/start/kubernetes.html
+++ b/docs/start/kubernetes.html
@@ -113,7 +113,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/start/minikube.html b/docs/start/minikube.html
index a95ba84c..17f2ae25 100644
--- a/docs/start/minikube.html
+++ b/docs/start/minikube.html
@@ -143,7 +143,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/docs/start/openshift.html b/docs/start/openshift.html
index a00a8860..1bd176c1 100644
--- a/docs/start/openshift.html
+++ b/docs/start/openshift.html
@@ -136,7 +136,7 @@ <h4>Contents</h4>
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/includes/footer.html b/includes/footer.html
index 4bc4df25..f01d50ee 100644
--- a/includes/footer.html
+++ b/includes/footer.html
@@ -11,7 +11,7 @@
       <h4>Skupper - Multicloud communication for Kubernetes</h4>
       <p>Skupper enables secure communication across Kubernetes
         clusters with no VPNs or special firewall rules</p>
-      <p>Copyright &#169; 2023 the Skupper authors</p>
+      <p>Copyright &#169; 2024 the Skupper authors</p>
     </div>
     <div>
       <p>All code and documentation is licensed under
diff --git a/input/docs/cli/index.md b/input/docs/cli/index.md
index e266918a..d26e706d 100644
--- a/input/docs/cli/index.md
+++ b/input/docs/cli/index.md
@@ -22,7 +22,8 @@ Installing the `skupper` command-line interface (CLI) provides a simple method t
 ## Creating a site using the CLI
 
 A service network consists of Skupper sites.
-This section describes how to create a site using the default settings.
+This section describes how to create a site in a Kubernetes cluster using the default settings.
+See [Using Skupper Podman](../cli/podman.html) for information about using the Skupper CLI to create Podman sites.
 
 * The `skupper` CLI is installed.
 * You are logged into the cluster.
@@ -358,6 +359,13 @@ After creating a service network, you can expose services from a local machine o
 
 For example, if you run a database on a server in your data center, you can deploy a front end in a cluster that can access the data as if the database was running in the cluster.
 
+<dl><dt><strong>📌 NOTE</strong></dt><dd>
+
+This documentation describes creating a gateway from a local host to a cluster site.
+An alternative approach is to create a site on the local host and link to the cluster site.
+See [Using Skupper Podman](../cli/podman.html) for information about using the Skupper CLI to create Podman sites.
+</dd></dl>
+
 ### Exposing simple local services to the service network
 
 This section shows how to expose a single service running locally on a service network.
@@ -644,7 +652,7 @@ Hostname for skupper router, typically `localhost`.
 * **qdr-listeners.port**\
 Port for skupper router, typically `5672`.
 
-### Exploring a service network
+## Exploring a service network
 
 Skupper includes a command to allow you report all the sites and the services available on a service network.
 
@@ -696,14 +704,14 @@ Skupper includes a command to allow you report all the sites and the services av
    5. The sites that the remote site is linked to.
    6. The unique identifier of a remote podman site. Podman sites do not have an associated context.
 
-#### Securing a service network
+## Securing a service network
 
 Skupper provides default, built-in security that scales across clusters and clouds.
 This section describes additional security you can configure.
 
 See [Securing a service network using policies](../policy/index.html) for information about creating granular policies for each cluster.
 
-##### Restricting access to services using a Kubernetes network policy
+### Restricting access to services using a Kubernetes network policy
 
 By default, if you expose a service on the service network, that service is also accessible from other namespaces in the cluster.
 You can avoid this situation when creating a site using the `--create-network-policy` option.
@@ -725,7 +733,7 @@ You can avoid this situation when creating a site using the `--create-network-po
 
 You can now expose services on the service network and those services are not accessible from other namespaces in the cluster.
 
-##### Applying TLS to TCP or HTTP2 traffic on the service network
+### Applying TLS to TCP or HTTP2 traffic on the service network
 
 By default, the traffic between sites is encrypted, however the traffic between the service pod and the router pod is not encrypted.
 For services exposed as TCP or HTTP2, the traffic between the pod and the router pod can be encrypted using TLS.
@@ -790,7 +798,7 @@ For services exposed as TCP or HTTP2, the traffic between the pod and the router
    ```
 5. Test calling the service from a TLS enabled frontend.
 
-##### Supported standards and protocols
+## Supported standards and protocols
 
 Skupper supports the following protocols for your service network:
 
@@ -818,7 +826,7 @@ When choosing which protocol to specify, note the following:
 
   TCP is implemented as a single streamed message, whereas HTTP1 and HTTP2 are implemented as request/response message routing.
 
-###### CLI options
+## CLI options
 
 For a full list of options, see the [Skupper Kubernetes CLI reference](../kubernetes-reference/index.html) and [Skupper Podman CLI reference](../podman-reference/index.html) documentation.
 
diff --git a/input/docs/cli/native-security-options.md b/input/docs/cli/native-security-options.md
index b3ab4ff0..d9ad1f4c 100644
--- a/input/docs/cli/native-security-options.md
+++ b/input/docs/cli/native-security-options.md
@@ -1,14 +1,14 @@
 ---
-title: Securing a service network
+title: #Securing a service network
 ---
-# Securing a service network
+## Securing a service network
 
 Skupper provides default, built-in security that scales across clusters and clouds.
 This section describes additional security you can configure.
 
 See [Securing a service network using policies](../policy/index.html) for information about creating granular policies for each cluster.
 
-## Restricting access to services using a Kubernetes network policy
+### Restricting access to services using a Kubernetes network policy
 
 By default, if you expose a service on the service network, that service is also accessible from other namespaces in the cluster.
 You can avoid this situation when creating a site using the `--create-network-policy` option.
@@ -30,7 +30,7 @@ You can avoid this situation when creating a site using the `--create-network-po
 
 You can now expose services on the service network and those services are not accessible from other namespaces in the cluster.
 
-## Applying TLS to TCP or HTTP2 traffic on the service network
+### Applying TLS to TCP or HTTP2 traffic on the service network
 
 By default, the traffic between sites is encrypted, however the traffic between the service pod and the router pod is not encrypted.
 For services exposed as TCP or HTTP2, the traffic between the pod and the router pod can be encrypted using TLS.
diff --git a/input/docs/cli/podman.md b/input/docs/cli/podman.md
index 7ff29d70..9f200fda 100644
--- a/input/docs/cli/podman.md
+++ b/input/docs/cli/podman.md
@@ -1,25 +1,27 @@
 ---
-title: Using Skupper podman
+title: Using Skupper Podman
 ---
-# Using Skupper podman
+# Using Skupper Podman
 
-Skupper podman allows you to create a site using containers, without requiring Kubernetes.
-Typically, you create a site on a Linux host, allowing you to link to and from other sites, regardless of whether those sites are running in podman or Kubernetes.
+Using the `skupper` command-line interface (CLI) allows you to create and manage Skupper sites from the context of the current Linux user.
+Skupper Podman allows you to create a site using containers, without requiring Kubernetes.
 
-## About Skupper podman
+A typical workflow is to create a site, link sites together, and expose services to the service network.
 
-Skupper podman is available with the following precedence:
+## About Skupper Podman
+
+Skupper Podman is available with the following precedence:
 
 * **`skupper --platform podman <command>`**\
-Use this option to avoid changing mode, for example, if you are working on Kubernetes and podman simultaneously.
+Use this option to avoid changing mode, for example, if you are working on Kubernetes and Podman simultaneously.
 * **`export SKUPPER_PLATFORM=podman`**\
-Use this command to use Skupper podman for the current session, for example, if you have two terminals set to different contexts. To set the environment to target Kubernetes sites:
+Use this command to use Skupper Podman for the current session, for example, if you have two terminals set to different contexts. To set the environment to target Kubernetes sites:
 
   ```bash
   $ export SKUPPER_PLATFORM=kubernetes
   ```
 * **`skupper switch podman`**\
-If you enter this command, all subsequent command target podman rather than Kubernetes for all terminal sessions.
+If you enter this command, all subsequent command target Podman rather than Kubernetes for all terminal sessions.
 
 To determine which mode is currently active:
 ```bash
@@ -30,8 +32,23 @@ podman
 
 To switch back to target Kubernetes sites: `skupper switch kubernetes`
 
+<dl><dt><strong>📌 NOTE</strong></dt><dd>
+
+Services exposed on remote sites are not automatically available to Podman sites.
+This is the equivalent to Kubernetes sites created using `skupper init --enable-service-sync false`.
+
+To consume an exposed service on a Podman site, check that it exists using `skupper service status` on the original site and use that information to create the service on the Podman site:
+```bash
+$ skupper service create <name> <port>
+```
+</dd></dl>
+
 ## Creating a site using Skupper podman
 
+A service network consists of Skupper sites.
+This section describes how to create a site in on a Linux host using the default settings.
+See [Using the Skupper CLI](../cli/index.html) for information about using the Skupper CLI to create Podman sites.
+
 * The latest `skupper` CLI is installed.
 * Podman is installed, see https://podman.io/
 
@@ -48,7 +65,7 @@ To switch back to target Kubernetes sites: `skupper switch kubernetes`
   Use `systemctl --user enable --now podman.socket` to start the  Podman API Socket.
 
   See [Podman socket activation](https://github.com/containers/podman/blob/main/docs/tutorials/socket_activation.md) for information about enabling this endpoint.
-  1. Set your session to use Skupper podman:
+  1. Set your session to use Skupper Podman:
 
      ```bash
      $ export SKUPPER_PLATFORM=podman
@@ -66,22 +83,25 @@ To switch back to target Kubernetes sites: `skupper switch kubernetes`
      The simplest Skupper site allows you to link to other sites, but does not support linking _to_ the current site.
 
      ```bash
-     $ skupper init --ingress none
+     $ skupper init
 
      It is recommended to enable lingering for <username>, otherwise Skupper may not start on boot.
      Skupper is now installed for user '<username>'.  Use 'skupper status' to get more information.
      ```
 
-     If you require that other sites can link to the site you are creating:
+     If you do not require that other sites can link to the site you are creating:
 
      ```bash
-     $ skupper init --ingress-host <machine-address>
-
-     It is recommended to enable lingering for <username>, otherwise Skupper may not start on boot.
-     Skupper is now installed for user '<username>'.  Use 'skupper status' to get more information.
+     $ skupper init --ingress none
      ```
 
-     For more information, see the [Skupper Podman CLI reference](../podman-reference/index.html) documentation.
+     In this guide we assume you have enabled ingress using the first command.
+     This allows you create tokens that allow links from every network interface on the host.
+
+     **📌 NOTE**\
+     When creating a token you can specify the ingress host.
+
+     You can also restrict ingress to an IP address or hostname when initializing as described in the [Skupper Podman CLI reference](../podman-reference/index.html) documentation.
   3. Check the status of your site:
 
      ```bash
@@ -92,15 +112,30 @@ To switch back to target Kubernetes sites: `skupper switch kubernetes`
      **📌 NOTE**\
      You can only create one site per user. If you require a host to support many sites, create a user for each site.
 
-## Linking sites using Skupper podman
+## Linking sites using Skupper Podman
+
+A service network consists of Skupper sites.
+This section describes how to link sites to form a service network.
 
-The general flow for linking podman sites is the same as for Kubernetes sites:
+Linking two sites requires a single initial directional connection. However:
+
+* Communication between the two sites is bidirectional, only the initial linking is directional.
+* The choice of direction for linking is typically determined by accessibility. For example, if you are linking a virtual machine running in the cloud with a Linux host running behind a firewall, you must link from the Linux host to the cloud virtual machine because that route is accessible.
 
 1. Generate a token on one site:
 
    ```bash
    $ skupper token create <filename>
    ```
+
+   The `metadata` section of the resulting YAML file shows which interface is available for linking.
+
+   To specify the interface, use `ifconfig` to determine the IP address of the interface you want to use.
+   You can then specify that IP address when creating the token:
+
+   ```bash
+   $ skupper token create <filename> --ingress-host <IP Address>
+   ```
 2. Create a link from the other site:
 
    ```bash
@@ -112,86 +147,209 @@ After you have linked to a network, you can check the link status:
 $ skupper link status
 ```
 
-## Working with services using Skupper podman
+## Specifying link cost
 
-The general flow for working with services is the same for Kubernetes and Podman sites.
+When linking sites, you can assign a cost to each link to influence the traffic flow.
+By default, link cost is set to `1` for a new link.
+In a service network, the routing algorithm attempts to use the path with the lowest total cost from client to target server.
 
-**📌 NOTE**\
-Services exposed on Kubernetes are not automatically available to Podman sites.
-This is the equivalent to Kubernetes sites created using `skupper init --enable-service-sync false`.
+* If you have services distributed across different sites, you might want a client to favor a particular target or link.
+In this case, you can specify a cost of greater than `1` on the alternative links to reduce the usage of those links.
 
-In this variation of the [hello world](https://github.com/skupperproject/skupper-example-hello-world) example, the `backend` service is exposed on Kubernetes site and a Podman site is linked.
-You deploy the `frontend` as a container and that container can access the `backend` service.
+  **📌 NOTE**\
+  The distribution of open connections is statistical, that is, not a round robin system.
+* If a connection only traverses one link, then the path cost is equal to the link cost.
+If the connection traverses more than one link, the path cost is the sum of all the links involved in the path.
+* Cost acts as a threshold for using a path from client to server in the network.
+When there is only one path, traffic flows on that path regardless of cost.
+
+  **📌 NOTE**\
+  If you start with two targets for a service, and one of the targets is no longer available, traffic flows on the remaining path regardless of cost.
+* When there are a number of paths from a client to server instances or a service, traffic flows on the lowest cost path until the number of connections exceeds the cost of an alternative path.
+After this threshold of open connections is reached, new connections are spread across the alternative path and the lowest cost path.
 
-1. Create a Podman site and link it to a Kubernetes site.
-2. Check the service from the Podman site:
+* You have set your Kubernetes context to a site that you want to link _from_.
+* A token for the site that you want to link _to_.
+
+1. Create a link to the service network:
 
    ```bash
-   $ skupper service status
+   $ skupper link create <filename> --cost <integer-cost>
+   ```
+
+   where `<integer-cost>` is an integer greater than 1 and traffic favors lower cost links.
+
+   **📌 NOTE**\
+   If a service can be called without traversing a link, that service is considered local, with an implicit cost of `0`.
+
+   For example, create a link with cost set to `2` using a token file named `token.yaml`:
 
-   No services defined
+   ```bash
+   $ skupper link create token.yaml --cost 2
    ```
+2. Check the link cost:
 
-   This result is expected because services exposed on Kubernetes are not automatically available to Podman sites.
-3. Create a service on the Podman site matching the service exposed on the Kubernetes site:
+   ```bash
+   $ skupper link status link1 --verbose
+   ```
+
+   The output is similar to the following:
 
    ```bash
-   $ skupper service create backend 8080
+    Cost:          2
+    Created:       2022-11-17 15:02:01 +0000 GMT
+    Name:          link1
+    Namespace:     default
+    Site:          default-0d99d031-cee2-4cc6-a761-697fe0f76275
+    Status:        Connected
    ```
-4. Validate the service from the Podman site by checking the backend API health URL:
+3. Observe traffic using the console.
+
+   If you have a console on a site, log in and navigate to the processes for each server.
+   You can view the traffic levels corresponding to each client.
+
+   **📌 NOTE**\
+   If there are multiple clients on different sites, filter the view to each client to determine the effect of cost on traffic.
+   For example, in a two site network linked with a high cost with servers and clients on both sites, you can see that a client is served by the local servers while a local server is available.
+
+## Exposing services on the service network from a Linux host
+
+After creating a service network, exposed services can communicate across that network.
+
+The general flow for working with services is the same for Kubernetes and Podman sites.
+
+The `skupper` CLI has two options for exposing services that already exist on a host:
+
+* `expose` supports simple use cases, for example, a host with a single service.
+See [Exposing simple services on the service network](#exposing-simple-services-on-the-service-network) for instructions.
+* `service create` and `service bind` is a more flexible method of exposing services, for example, if you have multiple services for a host.
+See [Exposing complex services on the service network](#exposing-complex-services-on-the-service-network) for instructions.
+
+### Exposing simple services on the service network
+This section describes how services can be enabled for a service network for simple use cases.
+
+* A Skupper Podman site
+
+1. Run a server, for example:
 
    ```bash
-   $ podman run -it --rm --network=skupper --name=myubi ubi8/ubi curl backend:8080/api/health
+   $ podman run --name backend-target --network skupper --detach --rm -p 8080:8080 quay.io/skupper/hello-world-backend
+   ```
+
+   This step is not Skupper-specific, that is, this process is unchanged from standard processes for your host.
+2. Create a service that can communicate on the service network:
 
-   OK
+   ```bash
+   $ skupper expose [host <hostname|ip>]
    ```
 
-   This command runs a container using the `skupper` network and returns the results from `http://backend:8080/api/health`
-5. Run the frontend as a container:
+   where
+
+   * `<host>` is the name of the host where the server is running.
+   For example, the name of the container if you run the server as a container.
+   * `<ip>` is the IP address where the server is running
+
+   For the example deployment in step 1, you create a service using the following command:
+   ```
+   $ skupper expose host backend-target --address backend --port 8080
+   ```
+
+   Options for this command include:
+
+   * `--port <port-number>`:: Specify the port number that this service is available on the service network.
+   NOTE: You can specify more than one port by repeating this option.
+   * `--target-port <port-number>`:: Specify the port number of pods that you want to expose.
+   * `--protocol <protocol>` allows you specify the protocol you want to use, `tcp`, `http` or `http2`
+3. Create the service on another site in the service network:
 
    ```bash
-   $ podman run -dp 8080:8080 --name hello-world-frontend --network skupper quay.io/skupper/hello-world-frontend
+   $ skupper service create backend 8080
    ```
-6. Check your service network is working as expected by navigating to http://localhost:8080 and click **Say hello**.
 
-   Each of the backend replicas respond, for example `Hi, Perfect Parrot. I am Kind Hearted Component (backend-7c84887f9f-wxhxp).`
+### Exposing complex services on the service network
 
-   <dl><dt><strong>📌 NOTE</strong></dt><dd>
+This section describes how services can be enabled for a service network for more complex use cases.
+
+* A Skupper Podman site
+
+1. Run a server, for example:
+
+   ```bash
+   $ podman run --name backend-target --network skupper --detach --rm -p 8080:8080 quay.io/skupper/hello-world-backend
+   ```
 
-   In this scenario, running the `skupper service status` command on the Podman site does not provide much detail about the service:
+   This step is not Skupper-specific, that is, this process is unchanged from standard processes for your host.
+2. Create a service that can communicate on the service network:
 
    ```bash
-   $ skupper service status
-   Services exposed through Skupper:
-   ╰─ backend (tcp port 8080)
+   $ skupper service create <name> <port>
    ```
 
-   </dd></dl>
+   where
 
-In this variation of the [hello world](https://github.com/skupperproject/skupper-example-hello-world) example, the `backend` service is exposed on Podman site and consumed from a `frontend` on a Kubernetes site.
+   * `<name>` is the name of the service you want to create
+   * `<port>` is the port the service uses
 
-1. Create a Podman site and link it to a Kubernetes site.
-2. Create and expose a frontend deployment on the Kubernetes site:
+   For the example deployment in step 1, you create a service using the following command:
+   ```bash
+   $ skupper service create hello-world-backend 8080
+   ```
+3. Bind the service to a cluster service:
 
    ```bash
-   $ kubectl create deployment frontend --image quay.io/skupper/hello-world-frontend
-   $ kubectl expose deployment/frontend --port 8080 --type LoadBalancer
+   $ skupper service bind <service-name> <target-type> <target-name>
    ```
-3. Run the backend as a container:
 
+   where
+
+   * `<service-name>` is the name of the service on the service network
+   * `<target-type>` is the object you want to expose, `host` is the only current valid value.
+   * `<target-name>` is the name of the cluster service
+
+   For the example deployment in step 1, you bind the service using the following command:
    ```bash
-   $ podman run -d --name hello-world-backend --network skupper quay.io/skupper/hello-world-backend
+   $ skupper service bind hello-world-backend host hello-world-backend
    ```
-4. Expose the `backend` from the Podman site.
+
+### Consuming simple services from the service network
+
+Services exposed on Podman sites are not automatically available to other sites.
+This is the equivalent to Kubernetes sites created using `skupper init --enable-service-sync false`.
+
+* A remote site where a service is exposed on the service network
+* A Podman site
+
+1. Log into the host as the user associated with the Skupper site.
+2. Create the local service:
 
    ```bash
-   $ skupper expose host hello-world-backend --address backend --port 8080
+   $ skupper service create <service-name> <port number>
    ```
-5. From the Kubernetes site, create the `backend` service:
+
+## Deleting a Podman site
+
+When you no longer want the Linux host to be part of the service network, you can delete the site.
+
+<dl><dt><strong>📌 NOTE</strong></dt><dd>
+
+This procedure removes all containers, volumes and networks labeled `application=skupper`.
+
+To check the labels associated with running containers:
+
+```bash
+$ podman ps -a --format "{{ID}}  {{Image}}  {{Labels}}"
+```
+</dd></dl>
+
+1. Make sure you are logged in as the user that created the site:
 
    ```bash
-   $ skupper service create backend 8080
+   $ skupper status
+   Skupper is enabled for "<username>" with site name "<machine-name>-<username>".
    ```
-6. Check your service network is working as expected by navigating to your cluster URL, port 8080, and clicking **Say hello**.
+2. Delete the site and all podman resources (containers, volumes and networks) labeled with "application=skupper":
 
-For more information, see the [Skupper Podman CLI reference](../podman-reference/index.html) documentation.
+   ```bash
+   $ skupper delete
+   Skupper is now removed for user "<username>".
+   ```
diff --git a/input/docs/kubernetes/deployment-concerns.md b/input/docs/kubernetes/deployment-concerns.md
index 4c9c0caf..a27d24d3 100644
--- a/input/docs/kubernetes/deployment-concerns.md
+++ b/input/docs/kubernetes/deployment-concerns.md
@@ -23,9 +23,8 @@ Increasing the number of routers does not improve network performance.  An incom
 
    Consider the following CPU allocation options:
 
-   |     |     |
-   | --- | --- |
    | Router CPU | Description |
+   | --- | --- |
    | 1 | Helps avoid issues with `BestEffort` on low resource clusters |
    | 2 | Suitable for production environments |
    | 5 | Maximum performance |
diff --git a/input/docs/overview/index.md b/input/docs/overview/index.md
index 95a3eddb..6ffbac65 100644
--- a/input/docs/overview/index.md
+++ b/input/docs/overview/index.md
@@ -58,6 +58,6 @@ This means that each Skupper instance is always aware of every service that has
 Once a Skupper network is formed across Kubernetes namespaces, any of the services in those namespaces can be exposed (through annotation) to the Skupper network.
 When a service is exposed, Skupper creates proxy endpoints to make that service available on each namespace in the Skupper network.
 
-* link:{security-link}
-* link:{routing-link}
-* link:{connectivity-link}
+* [Security](../overview/security.html)
+* [Routing](../overview/routing.html)
+* [Connectivity](../overview/connectivity.html)
diff --git a/input/docs/troubleshooting/index.md b/input/docs/troubleshooting/index.md
index 0c2e31e6..29a43bb5 100644
--- a/input/docs/troubleshooting/index.md
+++ b/input/docs/troubleshooting/index.md
@@ -123,12 +123,12 @@ Using the `skupper` command-line interface (CLI) provides a simple method to get
 5. List the Kubernetes events for a site:
 
    ```bash
-   kubectl get events | grep "service/skupper"
-   10m         Normal    ServiceSyncEvent               service/skupper                                   Service sync receiver connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
-   10m         Normal    ServiceSyncEvent               service/skupper                                   Service sync sender connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
-   10m         Normal    ServiceControllerCreateEvent   service/skupper                                   Creating service productcatalogservice
-   7m59s       Normal    TokenHandler                   service/skupper                                   Connecting using token link1
-   7m54s       Normal    TokenHandler                   service/skupper                                   Connecting using token link2
+   kubectl get events | grep "deployment/skupper-service-controller"
+   10m         Normal    ServiceSyncEvent               deployment/skupper-service-controller   Service sync receiver connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
+   10m         Normal    ServiceSyncEvent               deployment/skupper-service-controller   Service sync sender connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
+   10m         Normal    ServiceControllerCreateEvent   deployment/skupper-service-controller   Creating service productcatalogservice
+   7m59s       Normal    TokenHandler                   deployment/skupper-service-controller   Connecting using token link1
+   7m54s       Normal    TokenHandler                   deployment/skupper-service-controller   Connecting using token link2
    ```
 
    The output shows events relating to Kubernetes resources.
diff --git a/subrepos/skupper-docs/.gitrepo b/subrepos/skupper-docs/.gitrepo
index 0a73b213..23dee44f 100644
--- a/subrepos/skupper-docs/.gitrepo
+++ b/subrepos/skupper-docs/.gitrepo
@@ -6,7 +6,7 @@
 [subrepo]
 	remote = git@github.com:skupperproject/skupper-docs.git
 	branch = main
-	commit = 4f64d42cd9f344841903a64660f2f4679341b81b
-	parent = 4c5a16b025cf2895862b70e13d6df0bcf86fb93f
+	commit = a5c07eff91bc9f126730519bb005c3286d62a1b6
+	parent = f366b66452a0284140584a7ae13d1fb0a6ec22cb
 	method = merge
 	cmdver = 0.4.6
diff --git a/subrepos/skupper-docs/cli/gateway.adoc b/subrepos/skupper-docs/cli/gateway.adoc
index 4f0c7abd..2a11a6c5 100644
--- a/subrepos/skupper-docs/cli/gateway.adoc
+++ b/subrepos/skupper-docs/cli/gateway.adoc
@@ -1,14 +1,21 @@
 // Type: concept
 [id="exposing-services-local"] 
-= Exposing services on the {service-network} from a local machine
+== Exposing services on the {service-network} from a local machine
 
 After creating a {service-network}, you can expose services from a local machine on the {service-network}.
 
 For example, if you run a database on a server in your data center, you can deploy a front end in a cluster that can access the data as if the database was running in the cluster.
 
+[NOTE]
+====
+This documentation describes creating a gateway from a local host to a cluster site.
+An alternative approach is to create a site on the local host and link to the cluster site.
+See link:{podman-link} for information about using the Skupper CLI to create Podman sites.
+====
+
 // Type: procedure
 [id="exposing-service-gateway"] 
-== Exposing simple local services to the {service-network}
+=== Exposing simple local services to the {service-network}
 
 This section shows how to expose a single service running locally on a {service-network}.
 
@@ -66,7 +73,7 @@ The URL field shows the underlying communication and can be ignored.
 
 // Type: procedure
 [id="exposing-services-gateway"] 
-== Working with complex local services on the {service-network}
+=== Working with complex local services on the {service-network}
 
 
 This section shows more advanced usage of skupper gateway.
@@ -166,7 +173,7 @@ where
 
 // Type: procedure
 [id="exporting-gateway"] 
-== Creating a gateway and applying it on a different machine
+=== Creating a gateway and applying it on a different machine
 
 If you have access to a cluster from one machine but want to create a gateway to the {service-network} from a different machine, you can create the gateway definition bundle on the first machine and later apply that definition bundle on a second machine as described in this procedure.
 For example, if you want to expose a local database service to the {service-network}, but you never want to access the cluster from the database server, you can use this procedure to create the definition bundle and apply it on the database server.
@@ -318,7 +325,7 @@ NOTE: If you need to change the gateway definition, for example to change port,
 
 // Type: procedure
 [id="gateway-reference"] 
-== Gateway YAML reference
+=== Gateway YAML reference
 
 The xref:exporting-gateway[] describes how to create a gateway to apply on a separate machine using a gateway definition YAML file.
 
diff --git a/subrepos/skupper-docs/cli/index.adoc b/subrepos/skupper-docs/cli/index.adoc
index a17fa122..53aa99d9 100644
--- a/subrepos/skupper-docs/cli/index.adoc
+++ b/subrepos/skupper-docs/cli/index.adoc
@@ -35,7 +35,8 @@ client version {skupper-cli-version}
 == Creating a site using the CLI
 
 A {service-network} consists of Skupper sites.
-This section describes how to create a site using the default settings.
+This section describes how to create a site in a Kubernetes cluster using the default settings.
+See link:{podman-link} for information about using the Skupper CLI to create Podman sites.
 
 .Prerequisites
 
@@ -196,91 +197,10 @@ $ skupper link delete <link-name>
 where `<link-name>` is the name of the link specified during creation.
 -- 
 
-// Type: procedure
-[id="link-cost"] 
-== Specifying link cost
-
-When linking sites, you can assign a cost to each link to influence the traffic flow. 
-By default, link cost is set to `1` for a new link.
-In a {service-network}, the routing algorithm attempts to use the path with the lowest total cost from client to target server.
-
-* If you have services distributed across different sites, you might want a client to favor a particular target or link.
-In this case, you can specify a cost of greater than `1` on the alternative links to reduce the usage of those links.
-+
-NOTE: The distribution of open connections is statistical, that is, not a round robin system.
-
-* If a connection only traverses one link, then the path cost is equal to the link cost.  
-If the connection traverses more than one link, the path cost is the sum of all the links involved in the path.  
-
-* Cost acts as a threshold for using a path from client to server in the network.
-When there is only one path, traffic flows on that path regardless of cost.  
-+
-NOTE: If you start with two targets for a service, and one of the targets is no longer available, traffic flows on the remaining path regardless of cost.
-
-* When there are a number of paths from a client to server instances or a service, traffic flows on the lowest cost path until the number of connections exceeds the cost of an alternative path.
-After this threshold of open connections is reached, new connections are spread across the alternative path and the lowest cost path.
-
-
-.Prerequisite
-
-* You have set your Kubernetes context to a site that you want to link _from_.
-* A token for the site that you want to link _to_.
-
-.Procedure
-
-. Create a link to the {service-network}:
-+
---
-[source, bash]
-----
-$ skupper link create <filename> --cost <integer-cost>
-----
-
-where `<integer-cost>` is an integer greater than 1 and traffic favors lower cost links.
-
-NOTE: If a service can be called without traversing a link, that service is considered local, with an implicit cost of `0`.
-
-For example, create a link with cost set to `2` using a token file named `token.yaml`:
-
-[source, bash]
-----
-$ skupper link create token.yaml --cost 2
-----
---
-
-. Check the link cost:
-+
---
-[source, bash]
-----
-$ skupper link status link1 --verbose
-----
-
-The output is similar to the following:
-
-[source, bash]
-----
- Cost:          2
- Created:       2022-11-17 15:02:01 +0000 GMT
- Name:          link1
- Namespace:     default
- Site:          default-0d99d031-cee2-4cc6-a761-697fe0f76275
- Status:        Connected
-----
---
-
-. Observe traffic using the console.
-+
---
-If you have a console on a site, log in and navigate to the processes for each server. 
-You can view the traffic levels corresponding to each client.
-
-NOTE: If there are multiple clients on different sites, filter the view to each client to determine the effect of cost on traffic.
-For example, in a two site network linked with a high cost with servers and clients on both sites, you can see that a client is served by the local servers while a local server is available.
---
+include::link-cost.adoc[leveloffset=0]
 
 // Type: concept
-[id="exposing-services-ns"] 
+[id="kubernetes_exposing-services-ns"] 
 == Exposing services on the {service-network} from a namespace
 
 After creating a {service-network}, exposed services can communicate across that network.
@@ -288,14 +208,14 @@ After creating a {service-network}, exposed services can communicate across that
 The `skupper` CLI has two options for exposing services that already exist in a namespace:
 
 * `expose` supports simple use cases, for example, a deployment with a single service.
-See xref:exposing-simple-services[] for instructions.
+See xref:kubernetes_exposing-simple-services[] for instructions.
 
 * `service create` and `service bind` is a more flexible method of exposing services, for example, if you have multiple services for a deployment.
 See xref:exposing-complex-services[] for instructions.
 
 
 // Type: procedure
-[id="exposing-simple-services"] 
+[id="kubernetes_exposing-simple-services"] 
 === Exposing simple services on the {service-network}
 This section describes how services can be enabled for a {service-network} for simple use cases.
 
@@ -471,13 +391,13 @@ $ skupper expose deployment/backend --port 8080 --target-namespace east-backend
 ----
 --
 
-include::./gateway.adoc[leveloffset=+1]
+include::./gateway.adoc[leveloffset=0]
 
-include::./network-status.adoc[leveloffset=+1]
+include::./network-status.adoc[leveloffset=0]
 
-include::./native-security-options.adoc[leveloffset=+1]
+include::./native-security-options.adoc[leveloffset=0]
 
-include::./protocols.adoc[leveloffset=+1]
+include::./protocols.adoc[leveloffset=0]
 
 // Type: reference
 [id="cli-global-options"] 
diff --git a/subrepos/skupper-docs/cli/link-cost.adoc b/subrepos/skupper-docs/cli/link-cost.adoc
new file mode 100644
index 00000000..c1c95d92
--- /dev/null
+++ b/subrepos/skupper-docs/cli/link-cost.adoc
@@ -0,0 +1,82 @@
+// Type: procedure
+[id="{context}_link-cost"] 
+== Specifying link cost
+
+When linking sites, you can assign a cost to each link to influence the traffic flow. 
+By default, link cost is set to `1` for a new link.
+In a {service-network}, the routing algorithm attempts to use the path with the lowest total cost from client to target server.
+
+* If you have services distributed across different sites, you might want a client to favor a particular target or link.
+In this case, you can specify a cost of greater than `1` on the alternative links to reduce the usage of those links.
++
+NOTE: The distribution of open connections is statistical, that is, not a round robin system.
+
+* If a connection only traverses one link, then the path cost is equal to the link cost.  
+If the connection traverses more than one link, the path cost is the sum of all the links involved in the path.  
+
+* Cost acts as a threshold for using a path from client to server in the network.
+When there is only one path, traffic flows on that path regardless of cost.  
++
+NOTE: If you start with two targets for a service, and one of the targets is no longer available, traffic flows on the remaining path regardless of cost.
+
+* When there are a number of paths from a client to server instances or a service, traffic flows on the lowest cost path until the number of connections exceeds the cost of an alternative path.
+After this threshold of open connections is reached, new connections are spread across the alternative path and the lowest cost path.
+
+
+.Prerequisite
+
+* You have set your Kubernetes context to a site that you want to link _from_.
+* A token for the site that you want to link _to_.
+
+.Procedure
+
+. Create a link to the {service-network}:
++
+--
+[source, bash]
+----
+$ skupper link create <filename> --cost <integer-cost>
+----
+
+where `<integer-cost>` is an integer greater than 1 and traffic favors lower cost links.
+
+NOTE: If a service can be called without traversing a link, that service is considered local, with an implicit cost of `0`.
+
+For example, create a link with cost set to `2` using a token file named `token.yaml`:
+
+[source, bash]
+----
+$ skupper link create token.yaml --cost 2
+----
+--
+
+. Check the link cost:
++
+--
+[source, bash]
+----
+$ skupper link status link1 --verbose
+----
+
+The output is similar to the following:
+
+[source, bash]
+----
+ Cost:          2
+ Created:       2022-11-17 15:02:01 +0000 GMT
+ Name:          link1
+ Namespace:     default
+ Site:          default-0d99d031-cee2-4cc6-a761-697fe0f76275
+ Status:        Connected
+----
+--
+
+. Observe traffic using the console.
++
+--
+If you have a console on a site, log in and navigate to the processes for each server. 
+You can view the traffic levels corresponding to each client.
+
+NOTE: If there are multiple clients on different sites, filter the view to each client to determine the effect of cost on traffic.
+For example, in a two site network linked with a high cost with servers and clients on both sites, you can see that a client is served by the local servers while a local server is available.
+--
\ No newline at end of file
diff --git a/subrepos/skupper-docs/cli/native-security-options.adoc b/subrepos/skupper-docs/cli/native-security-options.adoc
index a91e5916..de68b77a 100644
--- a/subrepos/skupper-docs/cli/native-security-options.adoc
+++ b/subrepos/skupper-docs/cli/native-security-options.adoc
@@ -1,7 +1,7 @@
 include::../partials/attributes.adoc[]
 // Type: assembly
 [id="built-in-security-options"] 
-= Securing a service network
+== Securing a service network
 
 Skupper provides default, built-in security that scales across clusters and clouds.
 This section describes additional security you can configure.
@@ -10,7 +10,7 @@ See link:{policy-link} for information about creating granular policies for each
 
 // Type: procedure
 [id="network-policy"] 
-== Restricting access to services using a Kubernetes network policy
+=== Restricting access to services using a Kubernetes network policy
 
 By default, if you expose a service on the {service-network}, that service is also accessible from other namespaces in the cluster.
 You can avoid this situation when creating a site using the `--create-network-policy` option.
@@ -42,7 +42,7 @@ You can now expose services on the {service-network} and those services are not
 
 // Type: procedure
 [id="tls"] 
-== Applying TLS to TCP or HTTP2 traffic on the {service-network}
+=== Applying TLS to TCP or HTTP2 traffic on the {service-network}
 
 By default, the traffic between sites is encrypted, however the traffic between the service pod and the router pod is not encrypted.
 For services exposed as TCP or HTTP2, the traffic between the pod and the router pod can be encrypted using TLS.
diff --git a/subrepos/skupper-docs/cli/network-status.adoc b/subrepos/skupper-docs/cli/network-status.adoc
index 192601b7..56fc3dce 100644
--- a/subrepos/skupper-docs/cli/network-status.adoc
+++ b/subrepos/skupper-docs/cli/network-status.adoc
@@ -1,6 +1,6 @@
 // Type: procedure
 [id='network-service']
-= Exploring a {service-network}
+== Exploring a {service-network}
 
 Skupper includes a command to allow you report all the sites and the services available on a {service-network}.
 
diff --git a/subrepos/skupper-docs/cli/podman.adoc b/subrepos/skupper-docs/cli/podman.adoc
index ce2b1ba5..a1e899ab 100644
--- a/subrepos/skupper-docs/cli/podman.adoc
+++ b/subrepos/skupper-docs/cli/podman.adoc
@@ -1,45 +1,64 @@
 include::../partials/attributes.adoc[]
-
-:context: skupper-podman
 //Category: skupper-cli
 // Type: assembly
 [id='using-skupper-podman']
-= Using Skupper podman
+= Using Skupper Podman
 
+Using the `skupper` command-line interface (CLI) allows you to create and manage Skupper sites from the context of the current Linux user.
+Skupper Podman allows you to create a site using containers, without requiring Kubernetes.
 
-Skupper podman allows you to create a site using containers, without requiring Kubernetes.
-Typically, you create a site on a Linux host, allowing you to link to and from other sites, regardless of whether those sites are running in podman or Kubernetes.
+A typical workflow is to create a site, link sites together, and expose services to the {service-network}.
 
 [id='about']
-== About Skupper podman
+== About Skupper Podman
 
-Skupper podman is available with the following precedence:
+Skupper Podman is available with the following precedence:
 
-`skupper --platform podman <command>`:: Use this option to avoid changing mode, for example, if you are working on Kubernetes and podman simultaneously.
+`skupper --platform podman <command>`:: Use this option to avoid changing mode, for example, if you are working on Kubernetes and Podman simultaneously.
 
-`export SKUPPER_PLATFORM=podman`:: Use this command to use Skupper podman for the current session, for example, if you have two terminals set to different contexts. To set the environment to target Kubernetes sites:
+`export SKUPPER_PLATFORM=podman`:: Use this command to use Skupper Podman for the current session, for example, if you have two terminals set to different contexts. To set the environment to target Kubernetes sites:
 +
 [source, bash]
 ----
 $ export SKUPPER_PLATFORM=kubernetes
 ----
 
-`skupper switch podman`:: If you enter this command, all subsequent command target podman rather than Kubernetes for all terminal sessions.
+`skupper switch podman`:: If you enter this command, all subsequent command target Podman rather than Kubernetes for all terminal sessions.
 
 
 To determine which mode is currently active:
 [source, bash]
 ----
 $ skupper switch
-
+ 
 podman
 ----
 
 To switch back to target Kubernetes sites: `skupper switch kubernetes`
 
+
+
+[NOTE]
+====
+Services exposed on remote sites are not automatically available to Podman sites.
+This is the equivalent to Kubernetes sites created using `skupper init --enable-service-sync false`.
+
+To consume an exposed service on a Podman site, check that it exists using `skupper service status` on the original site and use that information to create the service on the Podman site:
+[source, bash]
+----
+$ skupper service create <name> <port>
+----
+====
+
+
 [id='creating-a-site']
 == Creating a site using Skupper podman
 
+A {service-network} consists of Skupper sites.
+This section describes how to create a site in on a Linux host using the default settings.
+See link:{cli-link} for information about using the Skupper CLI to create Podman sites.
+
+
 .Prerequisites
 
 * The latest `skupper` CLI is installed.
@@ -63,7 +82,7 @@ See link:https://github.com/containers/podman/blob/main/docs/tutorials/socket_ac
 --
 
 
-. Set your session to use Skupper podman:
+. Set your session to use Skupper Podman:
 +
 --
 [source, bash]
@@ -89,25 +108,25 @@ The simplest Skupper site allows you to link to other sites, but does not suppor
 
 [source, bash]
 ----
-$ skupper init --ingress none
+$ skupper init
 
 It is recommended to enable lingering for <username>, otherwise Skupper may not start on boot.
 Skupper is now installed for user '<username>'.  Use 'skupper status' to get more information.
 ----
 
-If you require that other sites can link to the site you are creating:
+If you do not require that other sites can link to the site you are creating:
 
 [source, bash]
 ----
-$ skupper init --ingress-host <machine-address>
-
-It is recommended to enable lingering for <username>, otherwise Skupper may not start on boot.
-Skupper is now installed for user '<username>'.  Use 'skupper status' to get more information.
+$ skupper init --ingress none
 ----
 
-For more information, see the link:{pod-ref-link} documentation.
+In this guide we assume you have enabled ingress using the first command.
+This allows you create tokens that allow links from every network interface on the host.
 
+NOTE: When creating a token you can specify the ingress host.
 
+You can also restrict ingress to an IP address or hostname when initializing as described in the link:{pod-ref-link} documentation.
 --
 
 . Check the status of your site:
@@ -124,17 +143,39 @@ NOTE: You can only create one site per user. If you require a host to support ma
 --
 
 
-== Linking sites using Skupper podman
+== Linking sites using Skupper Podman
 
-The general flow for linking podman sites is the same as for Kubernetes sites:
+
+A {service-network} consists of Skupper sites.
+This section describes how to link sites to form a {service-network}.
+
+Linking two sites requires a single initial directional connection. However:
+
+* Communication between the two sites is bidirectional, only the initial linking is directional.
+* The choice of direction for linking is typically determined by accessibility. For example, if you are linking a virtual machine running in the cloud with a Linux host running behind a firewall, you must link from the Linux host to the cloud virtual machine because that route is accessible. 
+
+.Procedure
 
 . Generate a token on one site:
 +
+--
 [source, bash]
 ----
 $ skupper token create <filename>
 ----
 
+The `metadata` section of the resulting YAML file shows which interface is available for linking.
+
+To specify the interface, use `ifconfig` to determine the IP address of the interface you want to use.
+You can then specify that IP address when creating the token:
+
+[source, bash]
+----
+$ skupper token create <filename> --ingress-host <IP Address>
+----
+
+--
+
 . Create a link from the other site:
 +
 [source, bash]
@@ -148,117 +189,210 @@ After you have linked to a network, you can check the link status:
 $ skupper link status
 ----
 
+include::link-cost.adoc[leveloffset=0]
 
-== Working with services using Skupper podman
+// Type: concept
+[id="podman_exposing-services-ns"] 
+== Exposing services on the {service-network} from a Linux host
+
+After creating a {service-network}, exposed services can communicate across that network.
 
 The general flow for working with services is the same for Kubernetes and Podman sites.
 
+The `skupper` CLI has two options for exposing services that already exist on a host:
 
-NOTE: Services exposed on Kubernetes are not automatically available to Podman sites.
-This is the equivalent to Kubernetes sites created using `skupper init --enable-service-sync false`.
+* `expose` supports simple use cases, for example, a host with a single service.
+See xref:podman_exposing-simple-services[] for instructions.
+
+* `service create` and `service bind` is a more flexible method of exposing services, for example, if you have multiple services for a host.
+See xref:podman_exposing-complex-services[] for instructions.
 
-.Example 01: Consuming a service from a Podman site
+// Type: procedure
+[id="podman_exposing-simple-services"] 
+=== Exposing simple services on the {service-network}
+This section describes how services can be enabled for a {service-network} for simple use cases.
 
-In this variation of the link:https://github.com/skupperproject/skupper-example-hello-world[hello world] example, the `backend` service is exposed on Kubernetes site and a Podman site is linked.
-You deploy the `frontend` as a container and that container can access the `backend` service.
+.Prerequisites 
 
-. Create a Podman site and link it to a Kubernetes site.
+* A Skupper Podman site
 
-. Check the service from the Podman site:
+.Procedure
+
+. Run a server, for example:
 +
 [source, bash]
 ----
-$ skupper service status
-
-No services defined
+$ podman run --name backend-target --network skupper --detach --rm -p 8080:8080 quay.io/skupper/hello-world-backend
 ----
 +
-This result is expected because services exposed on Kubernetes are not automatically available to Podman sites.
+This step is not Skupper-specific, that is, this process is unchanged from standard processes for your host.
+
+
+. Create a service that can communicate on the {service-network}:
++
+--
+[source, bash]
+----
+$ skupper expose [host <hostname|ip>]
+----
+
+where 
+
+* `<host>` is the name of the host where the server is running. 
+For example, the name of the container if you run the server as a container.
+* `<ip>` is the IP address where the server is running
+
+For the example deployment in step 1, you create a service using the following command:
+----
+$ skupper expose host backend-target --address backend --port 8080
+----
+
+Options for this command include:
+
+* `--port <port-number>`:: Specify the port number that this service is available on the {service-network}.
+NOTE: You can specify more than one port by repeating this option.
 
-. Create a service on the Podman site matching the service exposed on the Kubernetes site:
+* `--target-port <port-number>`:: Specify the port number of pods that you want to expose.
+
+* `--protocol <protocol>` allows you specify the protocol you want to use, `tcp`, `http` or `http2`
+
+--
+
+. Create the service on another site in the {service-network}:
 +
 [source, bash]
 ----
 $ skupper service create backend 8080
 ----
 
-. Validate the service from the Podman site by checking the backend API health URL:
+
+// Type: procedure
+[id="podman_exposing-complex-services"] 
+=== Exposing complex services on the {service-network}
+
+This section describes how services can be enabled for a {service-network} for more complex use cases.
+
+.Prerequisites 
+
+* A Skupper Podman site
+
+.Procedure
+
+. Run a server, for example:
++
+[source, bash]
+----
+$ podman run --name backend-target --network skupper --detach --rm -p 8080:8080 quay.io/skupper/hello-world-backend
+----
++
+This step is not Skupper-specific, that is, this process is unchanged from standard processes for your host.
+
+. Create a service that can communicate on the {service-network}:
 +
 --
 [source, bash]
 ----
-$ podman run -it --rm --network=skupper --name=myubi ubi8/ubi curl backend:8080/api/health
+$ skupper service create <name> <port>
+----
+
+where 
 
-OK
+* `<name>` is the name of the service you want to create
+* `<port>` is the port the service uses
+
+For the example deployment in step 1, you create a service using the following command:
+[source, bash]
+----
+$ skupper service create hello-world-backend 8080
 ----
 
-This command runs a container using the `skupper` network and returns the results from `http://backend:8080/api/health`
+
 --
 
-. Run the frontend as a container:
+. Bind the service to a cluster service:
 +
+--
 [source, bash]
 ----
-$ podman run -dp 8080:8080 --name hello-world-frontend --network skupper quay.io/skupper/hello-world-frontend
+$ skupper service bind <service-name> <target-type> <target-name>
 ----
 
-. Check your {service-network} is working as expected by navigating to http://localhost:8080 and click *Say hello*.
-+
---
-Each of the backend replicas respond, for example `Hi, Perfect Parrot. I am Kind Hearted Component (backend-7c84887f9f-wxhxp).`
+where
 
-[NOTE]
-====
-In this scenario, running the `skupper service status` command on the Podman site does not provide much detail about the service:
+* `<service-name>` is the name of the service on the {service-network}
 
+* `<target-type>` is the object you want to expose, `host` is the only current valid value.
+
+* `<target-name>` is the name of the cluster service
+
+For the example deployment in step 1, you bind the service using the following command:
 [source, bash]
 ----
-$ skupper service status
-Services exposed through Skupper:
-╰─ backend (tcp port 8080)
+$ skupper service bind hello-world-backend host hello-world-backend
 ----
 
-====
 --
 
-.Example 02: Exposing a service from a Podman site
 
-In this variation of the link:https://github.com/skupperproject/skupper-example-hello-world[hello world] example, the `backend` service is exposed on Podman site and consumed from a `frontend` on a Kubernetes site.
+// Type: procedure
+[id="consuming-simple-services"] 
+=== Consuming simple services from the {service-network}
+
+Services exposed on Podman sites are not automatically available to other sites.
+This is the equivalent to Kubernetes sites created using `skupper init --enable-service-sync false`.
+
+.Prerequisites
 
+* A remote site where a service is exposed on the {service-network}
+* A Podman site
 
+.Procedure
 
-. Create a Podman site and link it to a Kubernetes site.
+. Log into the host as the user associated with the Skupper site.
 
-. Create and expose a frontend deployment on the Kubernetes site:
+. Create the local service:
 +
+--
 [source, bash]
 ----
-$ kubectl create deployment frontend --image quay.io/skupper/hello-world-frontend
-$ kubectl expose deployment/frontend --port 8080 --type LoadBalancer
+$ skupper service create <service-name> <port number>
 ----
+--
+
+== Deleting a Podman site
+
+When you no longer want the Linux host to be part of the {service-network}, you can delete the site.
+
+[NOTE]
+====
+This procedure removes all containers, volumes and networks labeled `application=skupper`.
+
+To check the labels associated with running containers:
 
-. Run the backend as a container:
-+
 [source, bash]
 ----
-$ podman run -d --name hello-world-backend --network skupper quay.io/skupper/hello-world-backend
+$ podman ps -a --format "{{.ID}}  {{.Image}}  {{.Labels}}" 
 ----
+====
 
-. Expose the `backend` from the Podman site.
+.Procedure
+
+. Make sure you are logged in as the user that created the site:
 +
+--
 [source, bash]
 ----
-$ skupper expose host hello-world-backend --address backend --port 8080 
+$ skupper status
+Skupper is enabled for "<username>" with site name "<machine-name>-<username>".
 ----
+--
 
-. From the Kubernetes site, create the `backend` service:
+. Delete the site and all podman resources (containers, volumes and networks) labeled with "application=skupper":
 +
+--
 [source, bash]
 ----
-$ skupper service create backend 8080
+$ skupper delete
+Skupper is now removed for user "<username>".
 ----
-
-
-. Check your {service-network} is working as expected by navigating to your cluster URL, port 8080, and clicking *Say hello*.
-
-For more information, see the link:{pod-ref-link} documentation.
+--
\ No newline at end of file
diff --git a/subrepos/skupper-docs/cli/protocols.adoc b/subrepos/skupper-docs/cli/protocols.adoc
index c12c9186..4a314d30 100644
--- a/subrepos/skupper-docs/cli/protocols.adoc
+++ b/subrepos/skupper-docs/cli/protocols.adoc
@@ -1,6 +1,6 @@
 // Type: reference
 [id='protocols']
-= Supported standards and protocols
+== Supported standards and protocols
 
 Skupper supports the following protocols for your {service-network}:
 
diff --git a/subrepos/skupper-docs/console/index.adoc b/subrepos/skupper-docs/console/index.adoc
index 39be7ea0..e082f4b9 100644
--- a/subrepos/skupper-docs/console/index.adoc
+++ b/subrepos/skupper-docs/console/index.adoc
@@ -1,20 +1,16 @@
 include::../partials/attributes.adoc[]
-
 [id="skupper-console"] 
-= Using the Skupper console
-
-
-
-The Skupper console provides data and visualizations of the traffic flow between Skupper sites.
+= Using the {skupper-console-name}
 
+The {skupper-console-name} provides data and visualizations of the traffic flow between Skupper sites.
 
 // Type: procedure
 [id="enabling-console"] 
-== Enabling the Skupper console
+== Enabling the {skupper-console-name}
 
-By default, when you create a Skupper site, a Skupper console is not available.
+By default, when you create a Skupper site, a {skupper-console-name} is not available.
 
-When enabled, the Skupper console URL is displayed whenever you check site status using `skupper status`.
+When enabled, the {skupper-console-name} URL is displayed whenever you check site status using `skupper status`.
 
 .Prerequisites
 
@@ -47,14 +43,14 @@ $ skupper init --enable-console --enable-flow-collector
 
 // Type: procedure
 [id="accessing-console"] 
-== Accessing the Skupper console
+== Accessing the {skupper-console-name}
 
-By default, the Skupper console is protected by credentials available in the `skupper-console-users` secret.
+By default, the {skupper-console-name} is protected by credentials available in the `skupper-console-users` secret.
 
 
 .Procedure
 
-. Determine the Skupper console URL using the `skupper` CLI, for example:
+. Determine the {skupper-console-name} URL using the `skupper` CLI, for example:
 +
 [source, bash]
 ----
@@ -64,7 +60,7 @@ Skupper is enabled for namespace "west" in interior mode. It is not connected to
 The site console url is:  https://skupper-west.apps-crc.testing
 ----
 
-. Browse to the Skupper console URL. 
+. Browse to the {skupper-console-name} URL. 
 The credential prompt depends on how the site was created using `skupper init`:
 +
 * Using the `--console-auth unsecured` option, you are not prompted for credentials.
@@ -82,16 +78,16 @@ JNZWzMHtyg
 
 // Type: procedure
 [id="exploring-console"] 
-== Exploring the Skupper console
+== Exploring the {skupper-console-name}
 
 After exposing a service on the {service-network}, you create an _address_, that is, a service name and port number associated with a site. 
 There might be many replicas associated with an address.
-These replicas are shown in the Skupper console as _processes_. 
+These replicas are shown in the {skupper-console-name} as _processes_. 
 Not all participants on a {service-network} are services.
 For example, a _frontend_ deployment might call an exposed service named _backend_, but that frontend is not part of the {service-network}.
 In the console, both are shown so that you can view the traffic and these are called _components_.
 
-The Skupper console provides an overview of the following:
+The {skupper-console-name} provides an overview of the following:
 
 * Topology 
 * Addresses
@@ -100,7 +96,7 @@ The Skupper console provides an overview of the following:
 * Processes
 
 
-The Skupper console also provides useful networking information about the {service-network}, for example, traffic levels.
+The {skupper-console-name} also provides useful networking information about the {service-network}, for example, traffic levels.
 
 image::../images/skupper-adservice.png[]
 
diff --git a/subrepos/skupper-docs/kubernetes/deployment-concerns.adoc b/subrepos/skupper-docs/kubernetes/deployment-concerns.adoc
index 16f8a809..596db696 100644
--- a/subrepos/skupper-docs/kubernetes/deployment-concerns.adoc
+++ b/subrepos/skupper-docs/kubernetes/deployment-concerns.adoc
@@ -1,3 +1,4 @@
+include::../partials/attributes.adoc[]
 = Deployment options on Kubernetes
 
 When you create a site on Kubernetes, there are many options you can use.  For example, you can set the number of pods and the resources allocated to each pod.
@@ -22,7 +23,7 @@ By default, the router CPU allocation is `BestEffort` as described in link:https
 
 Consider the following CPU allocation options:
 
-[cols="1,5"]
+[%header,cols="1,5"]
 |===
 
 |Router CPU | Description
diff --git a/subrepos/skupper-docs/kubernetes/index.adoc b/subrepos/skupper-docs/kubernetes/index.adoc
index 1b050f73..6b5bb230 100644
--- a/subrepos/skupper-docs/kubernetes/index.adoc
+++ b/subrepos/skupper-docs/kubernetes/index.adoc
@@ -1,3 +1,4 @@
+include::../partials/attributes.adoc[]
 // Type: procedure
 [id="custom-certs"] 
 = Creating sites using a custom certificate authority
diff --git a/subrepos/skupper-docs/kubernetes/service-certs.adoc b/subrepos/skupper-docs/kubernetes/service-certs.adoc
index d2c5f2ff..e4788453 100644
--- a/subrepos/skupper-docs/kubernetes/service-certs.adoc
+++ b/subrepos/skupper-docs/kubernetes/service-certs.adoc
@@ -1,3 +1,4 @@
+include::../partials/attributes.adoc[]
 // Type: assembly
 [id="encrypting-traffic-pod-router"] 
 = Encrypting traffic from a pod to the Skupper router
diff --git a/subrepos/skupper-docs/overview/index.adoc b/subrepos/skupper-docs/overview/index.adoc
index e07e74e8..fcb752c5 100644
--- a/subrepos/skupper-docs/overview/index.adoc
+++ b/subrepos/skupper-docs/overview/index.adoc
@@ -1,7 +1,6 @@
-
+include::../partials/attributes.adoc[]
 //Category: skupper-overview
 // Type: assembly
-
 [id="skupper-overview"] 
 = Skupper overview
 
diff --git a/subrepos/skupper-docs/partials/attributes.adoc b/subrepos/skupper-docs/partials/attributes.adoc
index 6c9331bb..be317319 100644
--- a/subrepos/skupper-docs/partials/attributes.adoc
+++ b/subrepos/skupper-docs/partials/attributes.adoc
@@ -5,6 +5,7 @@
 :policy-link: ../policy/index.html[Securing a service network using policies]
 :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]
 :tokens-link: ../cli/tokens.html[Using Skupper tokens]
 :overview-link: ../overview/index.html[Overview]
 :security-link: ../overview/security.html[Security]
@@ -16,3 +17,4 @@
 
 
 :skupper-operator-name: Skupper operator
+:skupper-console-name: Skupper console
diff --git a/subrepos/skupper-docs/troubleshooting/index.adoc b/subrepos/skupper-docs/troubleshooting/index.adoc
index e1964c22..7b00260a 100644
--- a/subrepos/skupper-docs/troubleshooting/index.adoc
+++ b/subrepos/skupper-docs/troubleshooting/index.adoc
@@ -148,12 +148,12 @@ However, this output is most useful when reporting an issue and is included in t
 --
 [source, bash]
 ----
-kubectl get events | grep "service/skupper"                                                                                                                                                               
-10m         Normal    ServiceSyncEvent               service/skupper                                   Service sync receiver connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
-10m         Normal    ServiceSyncEvent               service/skupper                                   Service sync sender connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
-10m         Normal    ServiceControllerCreateEvent   service/skupper                                   Creating service productcatalogservice
-7m59s       Normal    TokenHandler                   service/skupper                                   Connecting using token link1
-7m54s       Normal    TokenHandler                   service/skupper                                   Connecting using token link2
+kubectl get events | grep "deployment/skupper-service-controller"                                                                                                                                                               
+10m         Normal    ServiceSyncEvent               deployment/skupper-service-controller   Service sync receiver connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
+10m         Normal    ServiceSyncEvent               deployment/skupper-service-controller   Service sync sender connection to amqps://skupper-router-local.private1.svc.cluster.local:5671 established
+10m         Normal    ServiceControllerCreateEvent   deployment/skupper-service-controller   Creating service productcatalogservice
+7m59s       Normal    TokenHandler                   deployment/skupper-service-controller   Connecting using token link1
+7m54s       Normal    TokenHandler                   deployment/skupper-service-controller   Connecting using token link2
 ----
 
 The output shows events relating to Kubernetes resources.