Rollback from 2.2.3 to 2.2.2

F5 recommends you rollback to a previous version when a newly deployed SPK pod in your cluster results in issues such as application downtime due to errors while upgrading or the deployment process does not complete successfully.

Important: Before you perform a rollback, ensure that you identify the cause of the failure and confirm whether a rollback will resolve the issue.

To successfully rollback to SPK 2.2.2 from 2.2.3, follow the instructions provided in the following sections:

  1. Rollback the F5Ingress

  2. Rollback the OTeL

  3. Rollback the Toda-fluentd

  4. Rollback the dSSM

  5. Rollback the Coremond

  6. Rollback the CRD Conversion

  7. Rollback the CWC Pod

  8. Rollback the Cert Manager

Rollback the F5Ingress

The Helm Rollback F5Ingress is not supported. Therefore, the recommended method to downgrade F5Ingress to a previous version is to use helm upgrade <previous helm version> by providing service account values as described below.

  1. Create patch_values.yaml with below service account values.

    global:
  serviceAccount:
    name: f5ingress-f5ingress

  2. Downgrade the F5Ingress to previous version using the f5ingress helm chart version specified in the desired SPK version tarball and providing the previously created patch_values.yaml file in the command.

    helm upgrade f5ingress Builds/Build1/tar/f5ingress-v15.82.0-0.9.1.tgz
     --namespace dav23-alpha  
     --set image.repository=repo.f5.com/images 
     --values overrides_2.2.2.yaml

    Sample Output:

    Release "f5ingress" has been upgraded. Happy Helming!
NAME: f5ingress
LAST DEPLOYED: Fri Dec 12 15:06:43 2026
NAMESPACE: spk-ingress
STATUS: deployed     
REVISION: 4
TEST SUITE: None
NOTES:
The F5Ingress Controller has been installed.
TMM debug sidecar is deployed. To access: kubectl exec -it deployment/f5-tmm -c debug -n spk-ingress -- bash

Rollback the OTeL

  1. Rollback OTeL to the previous version.

    In the example below, 1 is the REVISION number for downgrading the pod. To find the most recent previous version’s revision number, use the helm history <release-name> command.

    helm rollback otel 1 -n spk-utilities

    Sample Output:

    Rollback was a success! Happy Helming!

  2. View the historical revisions (versions) of a deployed Toda-fluentD release.

    helm history otel -n spk-utilities

    Sample Output:

    REVISION        UPDATED                         STATUS          CHART                APP VERSION     DESCRIPTION
1               Wed April 24 11:14:14 2025      superseded      otel-3.0.32          3.0.32          Install complete
2               Wed April 24 11:09:30 2025      superseded      otel-2.3.2-0.0.2     2.3.2-0.0.2     Upgrade complete
3               Mon April 29 13:12:48 2025      deployed        otel-3.0.32          3.0.32          Rollback to 1

Rollback the Toda-fluentD

  1. Rollback Toda-fluentD to the previous version.

    In the example below, 1 is the REVISION number for downgrading the pod. To find the most recent previous version’s revision number, use the helm history <release-name> command.

    helm rollback f5-toda-fluentd 1 -n spk-utilities

    Sample Output:

    Rollback was a success! Happy Helming!

  2. View the historical revisions (versions) of a deployed Toda-fluentD release.

    helm history f5-toda-fluentd -n spk-utilities

    Sample Output:

    REVISION        UPDATED                         STATUS          CHART                           APP VERSION     DESCRIPTION
1               Wed Dec 24 11:14:14 2025        superseded      f5-toda-fluentd-3.0.32          3.0.32          Install complete
2               Wed Dec 24 11:09:30 2025        superseded      f5-toda-fluentd-2.3.2-0.0.2     2.3.2-0.0.2     Upgrade complete
3               Mon Dec 29 13:12:48 2025        deployed        f5-toda-fluentd-3.0.32          3.0.32          Rollback to 1

Rollback the dSSM

To successfully rollback dSSM, follow the instructions in Rollback.

Rollback the Coremond

  1. Rollback OTeL to the previous version.

    In the example below, 1 is the REVISION number for downgrading the pod. To find the most recent previous version’s revision number, use the helm history <release-name> command.

    helm rollback f5-coremond 1 -n spk-utilities

    Sample Output:

    Rollback was a success! Happy Helming!

  2. View the historical revisions (versions) of a deployed Toda-fluentD release.

    helm history f5-coremond -n spk-utilities

    Sample Output:

    REVISION        UPDATED                         STATUS          CHART                       APP VERSION     DESCRIPTION
1               Wed April 24 11:14:14 2025      superseded      f5-coremond-3.0.32          3.0.32          Install complete
2               Wed April 24 11:09:30 2025      superseded      f5-coremond-2.3.2-0.0.2     2.3.2-0.0.2     Upgrade complete
3               Mon April 29 13:12:48 2025      deployed        f5-coremond-3.0.32          3.0.32          Rollback to 1

Rollback the CRD Conversion

  1. Rollback OTeL to the previous version.

    In the example below, 1 is the REVISION number for downgrading the pod. To find the most recent previous version’s revision number, use the helm history <release-name> command.

    helm rollback f5-crd-conversion 1 -n spk-utilities

    Sample Output:

    Rollback was a success! Happy Helming!

  2. View the historical revisions (versions) of a deployed Toda-fluentD release.

    helm history f5-crd-conversion -n spk-utilities

    Sample Output:

    REVISION        UPDATED                         STATUS          CHART                               APP VERSION     DESCRIPTION
1               Wed April 24 11:14:14 2025      superseded      f5-crd-conversion-3.0.32            3.0.32          Install complete
2               Wed April 24 11:09:30 2025      superseded      f5-crd-conversion-2.3.2-0.0.2       2.3.2-0.0.2     Upgrade complete
3               Mon April 29 13:12:48 2025      deployed        f5-crd-conversion-3.0.32            3.0.32          Rollback to 1

Rollback the CWC Pod

Important:

  • This note applies only to the CWC pod. When using Helm rollback or downgrading via Helm upgrade from SPK v2.2.2 to an earlier SPK version (SPK versions < 2.0), you must include the --force flag to successfully perform the rollback.

  • If you use the helm upgrade command to rollback to an earlier version (SPK versions < 2.0), use the CWC Helm chart version specified in the desired SPK version tarball.

  1. Rollback CWC pod to the previous version.

    In the example below, 1 is the REVISION number for downgrading the pod. To find the most recent previous version’s revision number, use the helm history <release-name> command.

    helm rollback cwc 1 -n spk-utilities --force

    Sample Output:

    Rollback was a success! Happy Helming!

  2. View the installed releases in spk-utilities namespace.

    helm list -n spk-utilities

    Sample Output:

    NAME                    NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                           APP VERSION
cwc                     spk-utilities       3               2025-12-26 15:19:11.076261541 +0000 UTC deployed        cwc-2.0.23                      2.0.23
f5-certificate-manager  spk-utilities       2               2025-12-24 08:20:18.796884978 +0000 UTC deployed        f5-cert-manager-0.23.48-0.1.0   v2.5.1
f5-coremond             spk-utilities       1               2025-12-24 11:06:26.378713173 +0000 UTC deployed        coremond-0.10.0-0.0.2           0.10.0-0.0.2
f5-crd-conversion       spk-utilities       1               2025-12-24 07:27:47.076888086 +0000 UTC deployed        f5-crdconversion-0.61.4-0.0.17  v1.212.9-0.0.65
f5-dssm         spk-utilities    3               2025-12-26 12:01:20.877642389 +0000 UTC deployed        f5-dssm-1.46.0-0.10.0           v1.46.0-0.10.0
f5-toda-fluentd         spk-utilities       2               2025-12-24 11:09:30.075569043 +0000 UTC deployed        f5-toda-fluentd-2.3.2-0.0.2     2.3.2-0.0.2
rabbitmq                spk-utilities       2               2025-12-24 08:37:33.393337517 +0000 UTC deployed        rabbitmq-0.8.9                  0.8.9

  3. View the historical revisions (versions) of a deployed CWC release.

    helm history cwc -n spk-utilities

    Sample Output:

    REVISION        UPDATED                         STATUS          CHART                   APP VERSION     DESCRIPTION
1               Fri Dec 26 13:10:52 2025        superseded      cwc-2.0.23              2.0.23          Install complete
2               Fri Dec 26 15:15:45 2025        superseded      cwc-0.49.7-0.0.12       0.49.7-0.0.12   Upgrade complete
3               Fri Dec 26 15:19:11 2025        deployed        cwc-2.0.23              2.0.23          Rollback to 1

Rollback the Cert Manager

Important:

  • This note applies only to the Cert Manager. When using Helm rollback or downgrading via Helm upgrade from SPK v2.2.2 to an earlier SPK version (SPK versions < 2.0), you must include the --force flag to successfully perform the rollback.

  • If you use the helm upgrade command to rollback to an earlier version (SPK versions < 2.0), use the Cert Manager Helm chart version specified in the desired SPK version tarball.

  1. Downgrade Cert Manager to the previous version.

    In the example below, 1 is the REVISION number for downgrading the pod. To find the most recent previous version’s REVISION number, use the helm history <release-name> command.

    helm rollback f5-certificate-manager 1 -n spk-utilities

    Sample Output:

    Rollback was a success! Happy Helming!

  2. View the installed releases in spk-utilities namespace.

    helm list -n spk-utilities

    Sample Output:

    NAME                    NAMESPACE               REVISION        UPDATED                                         STATUS          CHART
cwc                     spk-utilities           3               2025-04-21 08:26:01.521728191 +0000 UTC         deployed        cwc-0.41.34-10.0.18
f5-certificate-manager  spk-utilities           3               2025-04-21 08:30:10.545300867 +0000 UTC         deployed        f5-cert-manager-0.23.28-0.0.11
f5-crd-conversion       spk-utilities           1               2025-04-21 07:12:32.627675464 +0000 UTC         deployed        f5-crdconversion-0.16.15-0.0.12
rabbitmq                spk-utilities           3               2025-04-21 08:29:22.275226813 +0000 UTC         deployed        rabbitmq-0.5.10-10.0.14

  3. View the historical revisions (versions) of a deployed Cert Manager release.

    helm history f5-certificate-manager -n spk-utilities

    Sample Output:

    REVISION        UPDATED                         STATUS          CHART                           APP VERSION     DESCRIPTION
1               Wed Dec 24 11:09:30 2025        superseded      f5-cert-manager-0.5.12-0.0.10   v2.4.1          Install complete
2               Wed Dec 24 08:20:18 2025        superseded      f5-cert-manager-0.23.48-0.1.0   v2.5.1          Upgrade complete
3               Mon Dec 29 13:14:13 2025        deployed        f5-cert-manager-0.5.12-0.0.10   v2.4.1          Rollback to 1