Rollback BIG-IP Next for Kubernetes (Host) components using Helm (2.4.0 to 2.3.x)

This document describes how to rollback deployed components to a previous Helm revision (version) using helm rollback.

When to use rollback

Use a rollback when:

  • A component upgrade fails.

  • A newly deployed version causes functional or performance issues.

  • You need to restore a previously working version.

General Rollback Syntax

$ helm rollback <release-name> <revision> -n <namespace>

Parameters

  • <release-name> – Helm release name

  • <revision> – Target Helm revision number (for example, 1)

  • <namespace> – Namespace where the release is installed

Note

Always verify the revision number using the following command before rolling back:

$ helm history <release-name> -n <namespace>

Rollback the namespace‑scoped components

The following components were rolled back to revision 1.

OpenTelemetry Collector

$ helm rollback otel 1 -n spk-ingress

TODA Observer

$ helm rollback f5-toda-observer 1 -n spk-ingress

F5 Ingress

$ helm rollback f5ingress 1 -n spk-ingress

Rollback cluster‑wide components

TODA Fluentd

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

Core Monitoring Daemon

$ helm rollback f5-coremond 1 -n spk-utilities

CRD Conversion Service

$ helm rollback f5-crdconversion 1 -n spk-utilities

RabbitMQ

$ helm rollback rabbitmq 1 -n spk-utilities

CWC

$ helm rollback cwc 1 -n spk-utilities

Note

Helm rollback does not work for CWC if you are using Helm 4.0 or later versions. Recommend you to use Helm 3.x or earlier versions.

Certificate Manager

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

Note

  • You may get the Warning: tls: failed to find any PEM data in certificate input error while rolling back the Certificate Manager. This is a known issue and can be ignored. The rollback will still complete successfully.

  • Helm rollback does not work for dSSM. If you attempt this rollback, the DSSM pods may restart continuously and do not reach the Ready state. If you need to roll back dSSM, please contact F5 support.

Rollback CRDs

CRDs are rolled back without specifying a namespace.

Service Proxy CRDs

$ helm rollback f5-spk-crds-service-proxy 1

Common CRDs

$ helm rollback f5-spk-crds-common 1

Post‑Rollback Verification

After each rollback, perform the following checks:

  1. Verify Helm release status:

    helm list -n <namespace>

  2. Verify pod status:

    kubectl get pods -n <namespace>

  3. Ensure all pods are running and restarted where required.