Fix the upgrade command to correct one (#3039)

* adjust the navigation and add page for proxy upgrade
* Info about upgrading to specific version and air-gapped installations

modules/installation-and-upgrade/nav-installation-and-upgrade-guide.adoc

@@ -69,8 +69,10 @@ endif::[]
 ifeval::[{suma-content} == true]
 ** Upgrade and Migration
 *** Server
+**** xref:container-management/updating-server-containers.adoc[Server Upgrade]
 **** xref:container-deployment/suma/server-migration.adoc[Server Migration]
 *** Proxy
+**** xref:container-management/updating-proxy-containers.adoc[Proxy Upgrade]
 **** xref:container-deployment/suma/proxy-migration.adoc[Proxy Migration]
 *** Clients
 **** xref:client-intro.adoc[Upgrading Clients]
@@ -93,7 +95,6 @@ endif::[]
 ** Basic Server Management
 *** xref:container-management/mgradm-yaml-custom-configuration.adoc[Custom YAML configuration with mgradm]
 *** xref:container-management/start-and-stop-containers.adoc[Start and stop the container]
-*** xref:container-management/updating-containers.adoc[Update the container]
 *** xref:container-management/persistent-container-volumes.adoc[Persistent container volumes]
 
 ifdef::backend-pdf[]

modules/installation-and-upgrade/pages/container-management/updating-containers.adoc → modules/installation-and-upgrade/pages/container-management/_updating-containers.adoc

@@ -3,7 +3,7 @@
 The {productname} {productnumber} Server container can be updated using the following command:
 
 ----
-mgradm update
+mgradm upgrade podman
 ----
 
-This command will bring the status of the container up-to-date and restart the server.
+This command will bring the status of the container up-to-date and restart the server.

modules/installation-and-upgrade/pages/container-management/updating-proxy-containers.adoc

@@ -0,0 +1,26 @@
+= Update containers
+
+The {productname} {productnumber} Proxy containers running on [literal]``podman`` can be updated using the following command:
+----
+mgrpxy upgrade podman
+----
+
+Those running on a Kubernetes cluster can update using:
+
+----
+mgrpxy upgrade kubernetes
+----
+
+.Upgrading to specific version
+[NOTE]
+====
+If you do not specify the tag parameter, it will default to upgrading to the most recent version. To upgrade to a specific version, provide the tag parameter with the desired image tag.
+====
+
+[IMPORTANT]
+====
+While there is an option to upgrade a specific container using its specific tag, this feature is intended for applying PTFs only.
+We highly recommend using the same tag for all proxy containers to ensure consistency under normal circumstances.
+====
+
+For air-gapped installations, first upgrade the container RPM packages, then run the [literal]``mgradm`` command.

modules/installation-and-upgrade/pages/container-management/updating-server-containers.adoc

@@ -0,0 +1,23 @@
+= Update containers
+
+The {productname} {productnumber} Server container can be updated using the following command:
+
+----
+mgradm upgrade podman
+----
+
+This command will bring the status of the container up-to-date and restart the server.
+
+.Upgrading to specific version
+[NOTE]
+====
+If you do not specify the tag parameter , it will default to upgrading to the most recent version. To upgrade to a specific version, provide the tag parameter with the desired image tag.
+====
+
+For more information on the upgrade command and its parameters, use the following command:
+----
+mgradm upgrade podman -h
+----
+
+
+For air-gapped installations, first upgrade the container RPM packages, then run the [literal]``mgradm`` command.