SUSE Multi-Linux Manager 프록시 업그레이드

1. Refresh software repositories with zypper:

   zypper ref

2. 호스트 운영 체제에 따라 다음 단계를 진행합니다.

   SL Micro 같은 트랜잭션 시스템의 경우:

   1. Apply available updates with transactional-update:

      transactional-update

   2. If updates were applied, reboot.

   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

   또는 Kubernetes 클러스터에서 실행 중인 경우 다음을 사용하여 업데이트할 수 있습니다.

   mgrpxy upgrade kubernetes

4. podman에서, 사용하지 않는 컨테이너 이미지를 정리하여 디스크 공간을 확보합니다.

   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.