Upgrade SPK from v1.7.15 to v1.7.16

To successfully move from SPK v1.7.15 to v1.7.16, please follow the steps below.

Important: The Helm Upgrade is not supported. Therefore, the recommended method to upgrade SPK v1.7.15 to v1.7.16 is to uninstall and install the necessary releases.
  1. Upgrade Cert Manager
  2. Upgrade RabbitMQ
  3. Upgrade CWC
  4. Upgrade Toda-fluentd
  5. Upgrade dSSM
  6. Upgrade F5Ingress

Prereqisites:

Upgrade Cert Manager

  1. Uninstall the Cert Manager helm chart.

    In this example, the f5-certificate-manager helm chart is installed in the spk-utilities Project.

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

    Sample Output:

    release "f5-certificate-manager" uninstalled

  2. Reinstall the f5-certificate-manager using the new Cert Manager helm chart version mentioned in the SPK v1.7.16 tarball.

    In this example, the new version of Cert Manager helm chart is 0.5.12-0.0.15.

    helm install f5-certificate-manager tar/f5-cert-manager-0.5.12-0.0.15.tgz --namespace spk-utilities --values cm_overrides.yaml

    Sample Output:

    Helm installation output: NAME: f5-certificate-manager
LAST DEPLOYED: Sun Oct 19 20:34:10 2025
NAMESPACE: spk-utilities
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
# Modified from and/or generated from (possibly modified), cert-manager source
# f5-cert-manager

  3. See the installed releases in spk-utilities namespace.

    In this example, the below command shows the installed releases in spk-utilities Project.

    helm list -n spk-utilities

    Sample Output:

    | NAME            | NAMESPACE     | REVISION | UPDATED                                 | STATUS   | CHART                         | APP VERSION   |
|-----------------|---------------|----------|-----------------------------------------|----------|-------------------------------|-------------|
| f5-cert-manager | spk-utilities | 1        | 2025-10-19 20:34:10.040511141 +0000 UTC | deployed | f5-cert-manager-0.5.12-0.0.10 | v20.5.12-0.0.10 |

Upgrade RabbitMQ

  1. Uninstall the RabbitMQ helm chart.

    In this example, the rabbitmq helm chart is installed in the spk-utilities Project.

    helm uninstall rabbitmq -n spk-utilities

    Sample Output:

    release "rabbitmq" uninstalled

  2. Reinstall the rabbitmq using the new RabbitMQ helm chart version mentioned in the SPK v1.7.16 tarball.

    In this example, the new version of RabbitMQ helm chart is 2.0.10.

    helm install rabbitmq tar/rabbitmq-2.0.14.tgz --namespace spk-utilities --values rmq_overrides.yaml --set cert-orchestrator.enabled=true

    Sample Output:

    Helm installation output: NAME: rabbitmq
LAST DEPLOYED: Sun Oct 19 20:34:53 2025
NAMESPACE: spk-utilities
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
The RabbitMQ has been installed.

  3. See the installed releases in spk-utilities namespace.

    In this example, the below command shows the installed releases in spk-utilities Project.

    helm list -n spk-utilities

    Sample Output:

    | NAME     | NAMESPACE     | REVISION | UPDATED                                 | STATUS   | CHART           | APP VERSION |
|----------|---------------|----------|-----------------------------------------|----------|-----------------|-------------|
| rabbitmq | spk-utilities | 1        | 2025-10-19 20:34:53.040511141 +0000 UTC | deployed | rabbitmq-2.0.10 | v2.0.10     |

Upgrade CWC

  1. Uninstall the CWC helm chart.

    In this example, the cwc helm chart is installed in the spk-utilities Project.

    helm uninstall cwc -n spk-utilities

    Sample Output:

    release "cwc" uninstalled

  2. Reinstall the cwc using the new CWC helm chart version mentioned in the SPK v1.7.16 tarball.

    In this example, the new version of CWC helm chart is 2.0.23.

    helm install cwc tar/cwc-2.0.29.tgz -n spk-utilities --set rabbitmqNamespace=spk-utilities -f cwc_overrides.yaml

    Sample Output:

    NAME: cwc
LAST DEPLOYED: Sun Oct 19 20:35:26 2025
NAMESPACE: spk-utilities
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
The Cluster Wide Controller has been installed.

  3. See the installed releases in spk-utilities namespace.

    In this example, the below command shows the installed releases in spk-utilities Project.

    helm list -n spk-utilities

    Sample Output:

    | NAME  | NAMESPACE     | REVISION | UPDATED                                 | STATUS   | CHART      | APP VERSION |
|-------|---------------|----------|-----------------------------------------|----------|------------|-------------|
| cwc   | spk-utilities | 1        | 2025-10-19 20:35:26.040511141 +0000 UTC | deployed | cwc-2.0.23 | v2.0.23     |

Upgrade Toda-fluentd

  1. Uninstall the f5-toda-fluentd helm chart.

    In this example, the f5-toda-fluentd helm chart is installed in the spk-utilities Project.

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

    Sample Output:

    release “f5-toda-fluentd” uninstalled

  2. Reinstall the f5-toda-fluentd using the new Toda-fluentd helm chart version mentioned in the SPK v1.7.16 tarball.

    In this example, the new version of Toda-fluentd helm chart is 3.0.32.

    helm install f5-toda-fluentd tar/f5-toda-fluentd-3.0.41.tgz --namespace spk-utilities --values f5-toda-fluentd.yaml

    Sample Output:

    Helm installation output: NAME: f5-toda-fluentd
LAST DEPLOYED: Sun Oct 19 20:37:19 2025
NAMESPACE: spk-utilities
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Log aggregator - FluentD is deployed, which get logs from fluentbit sidecars.
FluentD outputs:
  'stdout' is "true"
  'persistent volume' is "true"
Persistent volume claim created with:
  accessModes: "ReadWriteOnce"
  storage: "3Gi"

FluentD hostname: f5-toda-fluentd.spk-utilities.svc.cluster.local.
FluentD port: "54321"
Use this info to connect to it:  
  --set f5-toda-logging.fluentd.host="f5-toda-fluentd.spk-utilities.svc.cluster.local."
  --set f5-toda-logging.fluentd.port=54321

FluentD service IP family:       
  serviceIpFamily: .Values.serviceIpFamily

  3. See the installed releases in spk-utilities namespace.

    In this example, the below command shows the installed releases in spk-utilities Project.

    helm list -n spk-utilities

    Sample Output:

    | NAME            | NAMESPACE     | REVISION | UPDATED                                 | STATUS   | CHART                  | APP VERSION |
|-----------------|---------------|----------|-----------------------------------------|----------|------------------------|-------------|
| f5-toda-fluentd | spk-utilities | 1        | 2025-10-19 20:37:19.040511141 +0000 UTC | deployed | f5-toda-fluentd-3.0.32 | v3.0.32     |

Upgrade dSSM

  1. Uninstall the dSSM helm chart.

    In this example, the dSSM helm chart is installed in the spk-utilities Project.

    helm uninstall f5-dssm -n spk-utilities

    Sample Output:

    release “f5-dssm” uninstalled

  2. Reinstall the dSSM using the new dSSM helm chart version mentioned in the SPK v1.7.16 tarball.

    In this example, the new version of dSSM helm chart is 3.0.54.

    helm install f5-dssm tar/f5-dssm-3.0.54.tgz --namespace spk-utilities -f f5-dssm_overrides.yaml

    Sample Output:

    Helm installation output: NAME: f5-dssm
LAST DEPLOYED: Sun Oct 19 20:38:05 2025
NAMESPACE: spk-utilities
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
1. Check the status of all pods/service by running
kubectl --namespace spk-utilities get all

  3. See the installed releases in spk-utilities namespace.

    In this example, the below command shows the installed releases in spk-utilities Project.

    helm list -n spk-utilities

    Sample Output:

    | NAME        | NAMESPACE     | REVISION | UPDATED                                 | STATUS   | CHART             | APP VERSION |
|-------------|---------------|----------|-----------------------------------------|----------|-------------------|-------------|
| f5-dssm     | spk-utilities | 1        | 2025-10-19 20:38:05.040511141 +0000 UTC | deployed | f5-dssm-3.0.45    | v3.0.45     |

Upgrade F5Ingress

  1. Uninstall the f5ingress helm chart.

    In this example, the f5ingress helm chart is installed in the spk-utils Project.

    helm uninstall f5ingress -n spk-ingress

    Sample Output:

    release "f5ingress" uninstalled

  2. Reinstall the f5ingress using the new f5ingress helm chart version mentioned in the SPK v1.7.16 tarball.

    In this example, the new version of f5ingress helm chart is 10.0.202.

    helm install f5ingress tar/f5ingress-10.0.202.tgz --namespace spk-ingress --set
image.repository=repo.f5.com/images --values ingress_overrides.yaml

    Sample Output:

    Helm installation output: NAME: f5ingress
LAST DEPLOYED: Sun Oct 19 20:37:58 2025
NAMESPACE: spk-ingress
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
The F5Ingress Controller has been installed.

  3. See the installed releases in spk-utils namespace.

    In this example, the below command shows the installed releases in spk-ingress Project.

    helm list -n spk-ingress

    Sample Output:

    | NAME        | NAMESPACE   | REVISION | UPDATED                                 | STATUS   | CHART             | APP VERSION |
|-------------|-------------|----------|-----------------------------------------|----------|-------------------|-------------|
| f5ingress   | spk-ingress | 1        | 2025-10-19 20:37:58.040511141 +0000 UTC | deployed | f5ingress-10.0.180| v10.0.180   |