Rollback SPK v2.0.0 to v1.7.14¶
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 v1.7.14 from v2.0.0, follow the instructions provided in the following sections:
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.
Create patch_values.yaml with below service account values.
global: serviceAccount: name: f5ingress-f5ingress
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 spk-installer/Builds/Build1/tar/f5ingress-v0.761.1-0.0.216.tgz -n spk-ingress -f spk-installer/ocp/tmp/spk-ingress_overrides_1.7.14.yaml -f patch_values.yaml
Sample Output:
Release "f5ingress" has been upgraded. Happy Helming! NAME: f5ingress LAST DEPLOYED: Fri Apr 11 15:06:43 2025 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 Toda-fluentD¶
Rollback Toda-fluentD to the previous version.
In the example below,
1is the REVISION number for downgrading the pod. To find the most recent previous version’s revision number, use thehelm history <release-name>command.helm rollback f5-toda-fluentd 1 -n spk-utilities
Sample Output:
Rollback was a success! Happy Helming!
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 Sun Apr 6 00:18:32 2025 superseded f5-toda-fluentd-3.0.28 3.0.28 Install complete 2 Mon Apr 7 16:16:46 2025 superseded f5-toda-fluentd-1.31.12-10.0.12 1.31.12-10.0.12 Upgrade complete 3 Fri Apr 11 15:55:28 2025 deployed f5-toda-fluentd-3.0.28 3.0.28 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.0.0 to an earlier SPK version (SPK versions < 2.0), you must include the
--forceflag 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.
Rollback CWC pod to the previous version.
In the example below,
1is the REVISION number for downgrading the pod. To find the most recent previous version’s revision number, use thehelm history <release-name>command.helm rollback cwc 1 -n spk-utilities --force
Sample Output:
Rollback was a success! Happy Helming!
View the installed releases in
spk-utilitiesnamespace.helm list -n spk-utilities
Sample Output:
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION cwc spk-utilities 3 2025-04-11 16:01:38.825916077 +0000 UTC deployed cwc-2.0.21 2.0.21 f5-certificate-manager spk-utilities 2 2025-04-09 13:52:48.330358417 +0000 UTC deployed f5-cert-manager-0.23.28-0.0.8 v2.2.3 f5-crd-conversion spk-utilities 1 2025-04-09 13:51:19.215929374 +0000 UTC deployed f5-crdconversion-0.16.15-0.0.10 v1.62.8-0.0.2 rabbitmq spk-utilities 2 2025-04-11 12:06:32.198922307 +0000 UTC deployed rabbitmq-0.5.10-10.0.12 0.5.10-10.0.12
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 Apr 11 11:42:30 2025 superseded cwc-2.0.21 2.0.21 Install complete 2 Fri Apr 11 12:11:52 2025 superseded cwc-0.41.34-10.0.18 0.41.34-10.0.18 Upgrade complete 3 Fri Apr 11 16:01:38 2025 deployed cwc-2.0.21 2.0.21 Rollback to 1
Rollback the RabbitMQ Pod¶
Important:
This note applies only to the RabbitMQ pod. When using Helm rollback or downgrading via Helm upgrade from SPK v2.0.0 to an earlier SPK version (SPK versions < 2.0), you must include the
--forceflag to successfully perform the rollback.If you use the helm upgrade command to rollback to an earlier version (SPK versions < 2.0), use the RabbitMQ Helm chart version specified in the desired SPK version tarball.
Rollback RabbitMQ to the previous version.
In the example below,
1is the REVISION number for downgrading the pod. To find the most recent previous version’s revision number, use thehelm history <release-name>command.helm rollback rabbitmq 1 -n spk-utilities --force
Sample Output:
Rollback was a success! Happy Helming!
View the installed releases in
spk-utilitiesnamespace.helm list -n spk-utilities
Sample Output:
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION cwc spk-utilities 4 2025-04-11 16:01:38.825916077 +0000 UTC deployed cwc-2.0.21 2.0.21 f5-certificate-manager spk-utilities 2 2025-04-09 13:52:48.330358417 +0000 UTC deployed f5-cert-manager-0.23.28-0.0.11 v2.3.0 f5-crd-conversion spk-utilities 1 2025-04-09 13:51:19.215929374 +0000 UTC deployed f5-crdconversion-0.16.15-0.0.12 v1.62.8-0.0.2 rabbitmq spk-utilities 4 2025-04-11 16:15:09.362891269 +0000 UTC deployed rabbitmq-0.5.10-10.0.14 0.5.10-10.0.14
View the historical revisions (versions) of a deployed RabbitMQ release.
helm history cwc -n spk-utilities
Sample Output:
REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION 1 Mon Apr 21 13:02:57 2025 superseded rabbitmq-2.0.8 2.0.8 Install complete 2 Mon Apr 21 08:26:57 2025 superseded rabbitmq-0.5.10-10.0.14 0.5.10-10.0.14 Upgrade complete 3 Mon Apr 21 08:29:22 2025 deployed rabbitmq-2.0.8 2.0.8 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.0.0 to an earlier SPK version (SPK versions < 2.0), you must include the
--forceflag 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.
Downgrade Cert Manager to the previous version.
In the example below,
1is the REVISION number for downgrading the pod. To find the most recent previous version’s REVISION number, use thehelm history <release-name>command.helm rollback f5-certificate-manager 1 -n spk-utilities
Sample Output:
Rollback was a success! Happy Helming!
View the installed releases in
spk-utilitiesnamespace.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
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 Tue Apr 8 16:59:12 2025 superseded f5-cert-manager-0.5.12-0.0.5 v1.3.2 Install complete 2 Wed Apr 9 13:52:48 2025 superseded f5-cert-manager-0.23.28-0.0.11 0.7.27-10.0.11 Upgrade complete 3 Sat Apr 12 12:46:29 2025 deployed f5-cert-manager-0.5.12-0.0.5 v1.3.2 Rollback to 1