How to use a Fleet hotfix image

This document (000021273) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Rancher 2.9.x

Situation

SUSE Rancher support and engineering might propose a hotfix image, which contains a potential fix for a specific issue, for troubleshooting purposes.
Hotfix images usually follow the naming convention: "v<X.Y.Z>-hotfix-<IDENTIFIER>"
The Rancher version should be respected (for Rancher v2.9.3, the debug image should be v2.9.3-hotfix-XYZ).

SUSE Support will give information about the content of a hotfix.

Disclaimers:
Please, use a hotfix build only when instructed by SUSE Support/Engineering personnel. Hotfix builds are meant to help troubleshoot specific problems and they are not supported for general use.
From an Engineering standpoint we are confident that hotfix builds will not introduce regressions, as changes target a small code region, pass reviews and a selection of automated tests as well. Nevertheless, hotfix builds do not go through full Rancher QA processes, so please be ready to revert to the original version in case unexpected behavior is noticed (instructions are provided below).

Important Upgrade Notice: This hotfix includes changes that may not be present in all subsequent Rancher releases. Therefore, to ensure a smooth upgrade process after applying this hotfix, please contact SUSE Support for guidance before upgrading to any later Rancher version. SUSE Support will indicate which versions are safe to upgrade to.

Resolution

Installation instructions

from a machine with access to the upstream cluster, edit the fleet deployment (to change the fleet image to the hotfix version):

Edit the fleet-controller ConfigMap (to change the fleet-agent image to the test version):

$ export TAG=v0.10.3-hotfix-ch-2-1e8d071a
$ kubectl get configmap -n cattle-fleet-system fleet-controller -o yaml | sed -E "s#rancher/fleet-agent:v[0-9A-Za-z\.\-]+#rancher/fleet-agent:$TAG#g" | kubectl apply -f -

Edit the fleet-controller deployment (to change the fleet-controller image to the test version):
```
$ export TAG=v0.10.3-hotfix-ch-2-1e8d071a
$ kubectl set image -n cattle-fleet-system deployment/fleet-controller "*=registry.suse.com/rancher/fleet:$TAG"
```
Note: for air-gap setups or environments not allowing images to be pulled from SUSE Registry, one should transfer or whitelist the fleet-controller and fleet-agent images appropriately for the procedure to work.

Uninstallation instructions (restoring the original Fleet version)

$ export TAG=v0.10.3
$ kubectl get configmap -n cattle-fleet-system fleet-controller -o yaml | sed -E "s#rancher/fleet-agent:v[0-9A-Za-z\.\-]+#rancher/fleet-agent:$TAG#g" | kubectl apply -f -
$ kubectl set image -n cattle-fleet-system deployment/fleet-controller "*=registry.suse.com/rancher/fleet:$TAG"

Follow-up instructions

Please report if changes help with symptoms.
Please contact SUSE again before upgrading to a newer Rancher version.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.