Bug ID 2277713: Unable to delete the SNATPool Custom Resource (CR) that was not created f5-cne-controller namespace

Last Modified: Aug 28, 2026

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

Known Affected Versions:
2.2.0, 2.2.1, 2.2.2, 2.2.3

Fixed In:
2.3.0

Opened: Apr 15, 2026

Severity: 3-Major

Symptoms

The f5-cne-controller watches and processes SNATPool Custom Resources (CRs) within its own namespace, only. SNATPool CRs created in other namespaces are ignored by the controller, and attempts to delete them will fail due to a validation webhook error.

Impact

SNATPool Custom Resources (CRs) cannot be deleted.

Conditions

F5-cne-controller installed using FLO and SNATPool Custom Resources (CRs) created in a namespace other than f5-cne-controller.

Workaround

1. Create SNATPool Custom Resources (CRs) with same name in the f5-cne-controller namespace. 2. Delete non f5-cne-controller namespace CR. 3. Delete f5-cne-controller namespace CR.

Fix Information

Updated the ValidatingWebhookConfiguration resource to optimize behavior when wholeClusterMode is enabled. In this mode, the validating webhook validates only snatpool CR objects in the controller namespace and no longer intercepts requests for snatpool CRs in other namespaces. As a result, the webhook no longer restricts deleting snatpool CRs in non-controller namespaces.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips