Chapter 5. Upgrading sites

Procedure

1. Note whether the site was installed using the operator or YAML. You will need to use the same method to upgrade the site.

   Use the following command to determine whether the site was installed using the operator or YAML:

   kubectl get deployment skupper-controller -n <namespace> -o jsonpath='{.metadata.labels}'

   This command returns a list of labels for the Skupper controller deployment. If the output includes ClusterServiceVersion, the site was installed using the operator. If there is no output, the site was installed using YAML.

   The namespace is the namespace where the Skupper controller is installed, for example skupper or openshift-operators.

2. Note whether Skupper is installed in a namespace or cluster-wide. You will need to use the same method to upgrade the site.

   Use the following command to determine whether Skupper is installed in a namespace or cluster-wide:

   kubectl get deployment skupper-controller -n <namespace> -o jsonpath='{.spec.template.spec.containers[0].env}'

   This command returns a list of environment variables for the Skupper controller deployment. If the output includes WATCH_NAMESPACE, the site is installed in a namespace. If there is no output, the site is installed cluster-wide. The namespace is the namespace where the Skupper controller is installed, for example skupper or openshift-operators.

3. If the site was installed using YAML, apply the latest YAML for either a namespace or cluster-wide installation. See Installing the CRDs and controller using YAML for instructions on how to install Red Hat Service Interconnect using YAML.
4. If the site was installed using the operator, upgrade the operator to the latest version for either a namespace or cluster-wide installation. See Installing the operators for instructions on how to install Red Hat Service Interconnect using the operator.

Procedure

1. Check if the Skupper controller is running, for example:

   podman ps | grep skupper-controller
   docker ps | grep skupper-controller

2. If the Skupper controller is not running, you can upgrade the site by running the reload command:

   skupper system reload

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

3. If the Skupper controller is running, you must upgrade the controller manually.

   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.

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

      Podman

      podman rm -f <user>-skupper-controller

      Docker

      docker 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.