agent version match warning

agent only network driver overlay

docs/v2.0-be/deploy/beinstalldocker.md

@@ -11,6 +11,10 @@ By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose
 
 To see the requirements, please, visit the page of [requirements](/v2.0-be/deploy/requirements/).
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
+
 ## :fontawesome-solid-paper-plane: Portainer Deployment
 
 Use the following Docker commands to deploy the Portainer Server; note the agent is not needed on standalone hosts, however it does provide additional functionality if used (see Portainer and agent scenario below):

docs/v2.0-be/deploy/beinstallk8s.md

@@ -11,6 +11,10 @@ By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose
 
 To see the requirements, please, visit the page of [requirements](/v2.0-be/deploy/requirements/).
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
+
 ## :fontawesome-solid-paper-plane: Portainer Deployment
 ---
 ### :material-list-status: Pre-Req Note:

docs/v2.0-be/deploy/beinstallswarm.md

@@ -11,6 +11,10 @@ By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose
 
 To see the requirements, please, visit the page of [requirements](/v2.0-be/deploy/requirements/).
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
+
 ## :fontawesome-solid-paper-plane: Portainer Deployment
 
 Use the following Docker commands to deploy the Portainer Server; note the agent is not needed on standalone hosts, however it does provide additional functionality if used (see Portainer and agent scenario below):
@@ -35,7 +39,7 @@ Use the following Docker commands to deploy the Portainer Server; note the agent
         First create the network:
 
         ```shell
-        docker network create portainer_agent_network
+        docker network create --driver overlay --attachable portainer_agent_network
         ```
 
         The following step to deploy the Agent:
@@ -83,6 +87,12 @@ Use the following Docker commands to deploy the Portainer Server; note the agent
         ```
 
         ### Portainer Agent Only Deployment
+        First create the network:
+
+        ```shell
+        docker network create --driver overlay --attachable portainer_agent_network
+        ```
+        
         Deploy Portainer Agent on a Swarm Cluster as a Swarm Service, run this command in a manager node in the cluster.
 
         ```shell

docs/v2.0-be/upgrade/upddocker.md

@@ -1,5 +1,8 @@
 # :fontawesome-brands-docker: Upgrade a Standalone Docker Deployment
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
 ### Docker Standalone
 
 Assuming you've used our recommended deployment scripts: when upgrading to the latest version of Portainer, use the following commands:

docs/v2.0-be/upgrade/updk8s.md

@@ -1,5 +1,9 @@
 # :material-kubernetes: Upgrade Kubernetes Deployment
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
+
 Steps to upgrade Portainer and or Portainer agent deployed into Kubernetes. Upgrade method depends on the original install method used.
 
 ## Using Helm

docs/v2.0-be/upgrade/updswarm.md

@@ -1,4 +1,8 @@
 # :fontawesome-brands-docker: Upgrade a Docker Swarm Deployment
+
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
 ### Docker Swarm
 Steps to upgrade Portainer and or Portainer agent deployed into Docker Swarm as a service.
 

docs/v2.0/deploy/ceinstalldocker.md

@@ -12,6 +12,10 @@ By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose
 
 To see the requirements, please, visit the page of [requirements](/v2.0/deploy/requirements).
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
+
 ## :fontawesome-solid-paper-plane: Portainer Deployment
 
 Use the following Docker commands to deploy the Portainer Server; note the agent is not needed on standalone hosts, however it does provide additional functionality if used (see Portainer and agent scenario below):

docs/v2.0/deploy/ceinstallk8s.md

@@ -14,6 +14,10 @@ By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose
 
 To see the requirements, please, visit the page of [requirements](/v2.0/deploy/requirements).
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
+
 ## :fontawesome-solid-paper-plane: Portainer Deployment
 ---
 ### :material-list-status: Pre-Req Note:

docs/v2.0/deploy/ceinstallswarm.md

@@ -13,6 +13,10 @@ By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose
 
 To see the requirements, please, visit the page of [requirements](/v2.0/deploy/requirements).
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
+
 ## :fontawesome-solid-paper-plane: Portainer Deployment
 
 Use the following Docker commands to deploy the Portainer Server; note the agent is not needed on standalone hosts, however it does provide additional functionality if used (see Portainer and agent scenario below):
@@ -37,7 +41,7 @@ Use the following Docker commands to deploy the Portainer Server; note the agent
         First create the network:
 
         ```shell
-        docker network create portainer_agent_network
+        docker network create --driver overlay --attachable portainer_agent_network
         ```
 
         The following step is deploy the Agent:
@@ -84,7 +88,13 @@ Use the following Docker commands to deploy the Portainer Server; note the agent
         docker stack deploy -c portainer-agent-stack.yml portainer
         ```
 
-        ### :fontawesome-solid-laptop: Portainer Agent Only Deployment
+        ### :fontawesome-solid-laptop: Portainer Agent Only Deployment       
+        First create the network:
+
+        ```shell
+        docker network create --driver overlay --attachable portainer_agent_network
+        ```
+        
         Deploy Portainer Agent on a Swarm Cluster as a Swarm Service, run this command in a manager node in the cluster.
 
         ```shell

docs/v2.0/upgrade/upddocker.md

@@ -1,5 +1,8 @@
 # :fontawesome-brands-docker: Upgrade a Standalone Docker Deployment
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
 ### Docker Standalone
 
 Assuming you've used our recommended deployment scripts: when upgrading to the latest version of Portainer, use the following commands:

docs/v2.0/upgrade/updk8s.md

@@ -1,5 +1,9 @@
 # :material-kubernetes: Upgrade Kubernetes Deployment
 
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
+
 Steps to upgrade Portainer and or Portainer agent deployed into Kubernetes. Upgrade method depends on the original install method used.
 
 ## Using Helm

docs/v2.0/upgrade/updswarm.md

@@ -1,4 +1,8 @@
 # :fontawesome-brands-docker: Upgrade a Docker Swarm Deployment
+
+!!! Warning "Agent Versions"
+    Always match the agent version to Portainer Server version. i.e., while installing or upgrading to Portainer 2.6 make sure all the agents are also version 2.6. 
+
 ### Docker Swarm
 Steps to upgrade Portainer and or Portainer agent deployed into Docker Swarm as a service.