Bug ID 1982921: Delete FLO CRDs when FLO is uninstalled from one namespace and before installing in another namespace

Last Modified: Jul 15, 2026

Affected Product(s):
BIG_IP_NEXT(BNK) BNK(all modules)

Fixed In:
2.1.0

Opened: Jul 14, 2025

Severity: 3-Major

Symptoms

When FLO is uninstalled from one namespace and try to install in another namespace, you will see the error as shown below: Error: INSTALLATION FAILED: Unable to continue with install: CustomResourceDefinition "afms.k8s.f5.com" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "f5-utils": current value is "alpha".

Impact

FLO installation is blocked.

Conditions

This issue occurs when FLO is uninstalled from one namespace and tried to install in another namespace.

Workaround

Delete the FLO related CRDs and install the FLO in desired namespace using the below command: kubectl get crds -o name | grep 'k8s.f5.com' | xargs kubectl delete

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips