Uninstall the F5 CRDs and the CNE core using Helm¶

Introduction¶

The following instructions describe how to uninstall the F5 custom resource definitions (CRDs) and the CNE core using Helm.

Note

Before you begin, make sure you’ve uninstalled all CNE instances using Helm.
These instructions assume that you’ll delete the f5-cne-core namespace as part of the uninstallation. Make sure you have manifests for any resources in the namespace that you want to keep.

Uninstall F5 CWC:

helm uninstall f5-cwc \
  --namespace f5-cne-core \
  --wait

Uninstall RabbitMQ:

helm uninstall rabbitmq \
  --namespace f5-cne-core \
  --wait

Uninstall F5 dSSM:

helm uninstall f5-dssm \
  --namespace f5-cne-core \
  --wait

(BNK cluster only) Uninstall F5 TODA OpenTelemetry Collector:

helm uninstall f5-stats-collector \
  --namespace f5-cne-core \
  --wait

(BNK cluster only) Uninstall F5 TODA Stats Observer:

helm uninstall f5-toda-observer \
  --namespace f5-cne-core \
  --wait

Uninstall F5 TODA Fluentd:

helm uninstall f5-toda-fluentd \
  --namespace f5-cne-core \
  --wait

Uninstall F5 Core-File Collector:

helm uninstall f5-coremond \
  --namespace f5-cne-core \
  --wait

Uninstall F5 CRD Conversion:

helm uninstall f5-crdconversion \
  --namespace f5-cne-core \
  --wait

Uninstall F5 cert-manager:

helm uninstall f5-cert-manager \
  --namespace f5-cne-core \
  --wait

Was a BIG-IP Next for Kubernetes (BNK) instance installed in this cluster?

Yes:

Uninstall the BNK Legacy common custom resource definitions (CRDs):

helm uninstall f5-spk-crds-common \
  --namespace f5-cne-core \
  --wait

Uninstall the BNK Legacy service-proxy CRDs:

helm uninstall f5-spk-crds-service-proxy \
  --namespace f5-cne-core \
  --wait

No (CNF instances):

Uninstall the CNF CRDs:

helm uninstall f5-cnf-crds-n6lan \
  --namespace f5-cne-core \
  --wait

Delete the f5-cne-core namespace:
```
kubectl delete namespace f5-cne-core
```
F5 BIG-IP Cloud-Native Edition is completely uninstalled.