Flow for updating local site

[pwright]

follow up on skupperproject/skupper#2332

@fgiorgetti am I getting this right?

You can't run skupper system uninstall when there's a running site, so workaround is:

• remove containers manually (just router?)
• pull latest images / change config
• restart site

[fgiorgetti]

Actually this is not for updating local sites.
To update an existing site today, you need to have the desired version of the CLI, then just run skupper system reload.

The issue with system uninstall is that it is meant to uninstall the system-controller, but it only happens if there is no active site running. To workaround that, and allow the system-controller container to be updated, an alternative we have until it is properly addressed by the CLI, would be to stop and remove the system-controller container, which is named as: <user>-skupper-controller (as we have just one instance per user).

Once the container is removed, we can then run skupper system install once again, and the container will be recreated with the appropriate version (according to CLI's version).

[pwright]

@fgiorgetti How about:

Upgrading Podman sites

There are two distinct procedures for updating your Skupper installation: updating the site configuration and manually updating the controller.

Standard Site Update

To update an existing site to the latest images or configuration matching your current CLI version:

Procedure

1. Ensure you have the latest version of the Skupper CLI installed.
2. Run the reload command:

   skupper system reload

   This command refreshes the site definition and pulls the latest images associated with the CLI version.

Updating the controller

Currently, skupper system uninstall protects active sites by refusing to run if a site is detected. However, if you need to force an update to the controller itself (to pick up a new controller version) without deleting your sites, follow this manual workaround:

Prerequisites

• Ensure your CLI is updated to the target version.

Procedure

1. Stop and remove the controller container. The container is named <user>-skupper-controller.

   podman rm -f <user>-skupper-controller
   

   Note: Replace <user> with the specific username under which Skupper is running.

2. Re-install the controller.
   Run the install command to recreate the controller using the new CLI version.

   skupper system install
   

3. Verify the controller is recreated with the updated version.