Proxy Upgrade
Before running the upgrade command, it is required to upgrade the mgrpxy tool first.
Refresh software repositories with
zypper:zypper refApply available updates:
For SLE Micro:
transactional-updateIf updates were applied,
reboot.For SUSE Linux Enterprise Server:
zypper upThe SUSE Manager 5.0 Proxy containers running on
podmancan be updated using the following command:mgrpxy upgrade podmanOr, those running on a Kubernetes cluster can update using:
mgrpxy upgrade kubernetesOn podman, clean up the unused container images to free disk space:
podman image prune -a
On Kubernetes the image cleanup is handled automatically, or it depends on the Kubernetes distribution.
|
If you do not specify the tag parameter when upgrading to specific version, 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. |
|
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 mgrpxy upgrade podman command.