SUSE Multi-Linux Manager Proxy Upgrade

1. Refresh software repositories with zypper:

   zypper ref

2. Depending on the host operating system, proceed with these steps:

   For a transactional system such as SL Micro:

   1. Apply available updates with transactional-update:

      transactional-update

   2. If updates were applied, reboot.

   For SUSE Linux Enterprise Server:

   Update installed software with zypper:

   zypper up

3. The SUSE Multi-Linux Manager Proxy containers running on podman can be updated using the following command:

   mgrpxy upgrade podman

   Or, those running on a Kubernetes cluster can update using:

   mgrpxy upgrade kubernetes

4. On 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.

   In some upgrades, multiple *.rpmnew and *.rpmsave files may be generated. The presence or number of these files does not indicate that manual action is required. In SUSE Multi-Linux Manager container environments, required configuration changes are applied automatically during the upgrade process. These files are created as a result of differences between packaged defaults and existing configuration files, and may also include internal or informational changes that are not intended to be merged. If manual action is required for a configuration change, it will be explicitly documented in the release notes or upgrade documentation. Do not treat these files as a post-upgrade checklist or merge them in bulk. Only review a file if you are actively troubleshooting a specific issue and understand the impact of the configuration it contains. If a change is required, it should be applied intentionally based on a known requirement, not by copying differences from these files. If you are unsure, leave the file unchanged.