Upgrade BIG-IP Next for Kubernetes (BNK) from 2.4.1 to 2.4.2 using F5 Lifecycle Operator

This document describes how to upgrade the F5 Lifecycle Operator (FLO) and upgrade the CNE Instance.

Upgrade F5 Lifecycle Operator

  1. Create or update the override values file for F5 Lifecycle Operator (for example, f5-lifecycle-operator-override-values.yaml).

  2. Upgrade F5 Lifecycle Operator.

    helm upgrade f5-lifecycle-operator \

oci://repo.f5.com/charts/f5-lifecycle-operator
–version v2.30.0-0.11.4 \ # Need to change FLO to the correct version –namespace f5-cne-core
–values f5-lifecycle-operator-override-values.yaml
–wait ```

  1. Verify the upgrade:

    $ helm list

Upgrade the CNE-instance workloads

  1. In a terminal window on your computer, make sure you’re in the directory that contains your manifest for the CNE-instance workloads (for example, cne-instance-f5-bnk-instance.yaml).

  2. Trigger F5 Lifecycle Operator to upgrade the CNE-instance workloads.

    Example

    kubectl apply -f cne-instance-f5-bnk-instance.yaml \
  --namespace f5-bnk-instance

Verify the upgrade

  1. Wait until the status of each CNE-core pod is Running:

    watch kubectl get pods \
  --namespace f5-cne-core -o wide

  2. Wait until the status of each CNE-instance pod is Running.

    Example

    watch kubectl get pods \
  --namespace f5-bnk-instance -o wide