Upgrade from v2.0 or v2.1¶
Important
You cannot upgrade directly from BNK v2.0 or v2.1 to v2.2. You must uninstall your current version and install v2.2 as a new deployment.
Pre-Upgrade Configuration Backup¶
Before starting the upgrade, create a complete configuration backup. This backup allows you to restore your settings after the new installation.
For detailed commands, see the Configuration Backup and Export section.
Export configurations.
mkdir -p bnk-backup-$(date +%Y%m%d) cd bnk-backup-$(date +%Y%m%d) # Export F5 CRs for crd in $(kubectl get crds | grep f5 | awk '{print $1}'); do resource=$(echo $crd | cut -d. -f1) kubectl get $resource -A -o yaml > ${resource}.yaml done # Export Gateway API CRs kubectl get gatewayclasses,gateways,httproutes,grpcroutes -A -o yaml > gateway_api.yaml # Export Helm values helm get values flo -n f5-cne-core > flo_values.yaml # Export secrets kubectl get secrets -n f5-cne-core -o yaml > secrets-f5-cne-core.yaml kubectl get secrets -n <cneInstanceNamespace> -o yaml > secrets-<cneInstanceNamespace>.yaml # Export ZebOS configmaps kubectl get configmap zebos-config -n <cneInstanceNamespace> -o yaml > zebos-config.yaml
Generate a QKView snapshot.
Collect a QKView snapshot to help compare system state before and after the upgrade.
Document node labels, taints, and annotations.
kubectl get nodes -o yaml > node_state.yaml
Upgrade Procedure¶
Delete Gateway API CRs.
kubectl delete -f cneinstancecr.yaml -n <cneInstanceNamespace>
Uninstall FLO.
helm uninstall flo -n f5-cne-core
Confirm all BNK pods are removed.
kubectl get pods -n <cneInstanceNamespace> # Should return empty
Install v2.2.
Perform a full installation of v2.2. See Infrastructure Preparation and BNK Installation.
Restore configuration.
kubectl apply -f backup_f5spkvlans.yaml kubectl apply -f backup_gateway_api.yaml # Apply remaining CRs as needed
Verify all components are running.
See Verify Installation.