Uninstall a CNE instance using Helm¶
Introduction¶
The following instructions describe how to uninstall a CNE instance using Helm. If you want to uninstall more than one CNE instance, repeat these instructions for each instance.
Note
Uninstall using Helm only if you installed using Helm.
These instructions assume that you’ll delete the CNE instance namespace as part of the uninstallation.
Uninstall the CNE instance¶
Set the
CNE_INSTANCE_NAMESPACEenvironment variable to the name of the CNE instance’s namespace.Example
$ export CNE_INSTANCE_NAMESPACE=bnk-app1
Uninstall F5 TODA Observer:
$ helm uninstall f5-toda-observer \ --namespace $CNE_INSTANCE_NAMESPACE \ --wait
Uninstall the f5ingress release:
$ helm uninstall f5ingress \ --namespace $CNE_INSTANCE_NAMESPACE \ --wait
Delete the TLS-offloading secret:
$ kubectl delete secret tls-keys-certs-secret \ --namespace $CNE_INSTANCE_NAMESPACE
Delete the certificates for the Prometheus-scraping endpoint:
$ kubectl delete certificates \ external-f5ingotelsvr \ external-otelsvr \ --namespace $CNE_INSTANCE_NAMESPACE
Delete the MULTUS network-attachment definitions you created.
Did you store Helm charts and Docker container images in a private artifact registry?
Yes:
If your private artifact registry requires authentication, delete the image pull secret for your private artifact registry (for example,
private-registry-pull-secret):
$ kubectl delete secret \ <privateRegistryPullSecretManifestFilename> \ --namespace $CNE_INSTANCE_NAMESPACE
No:
Delete the image pull secret for F5 Artifact Registry:
$ kubectl delete secret far-pull-secret \ --namespace $CNE_INSTANCE_NAMESPACE
Delete the namespace:
$ kubectl delete namespace $CNE_INSTANCE_NAMESPACE
What’s next¶
If you have other CNE instances you want to uninstall, repeat these instructions.
If you’ve uninstalled all CNE instances and want to uninstall F5 BIG-IP Cloud-Native Edition completely, go to Uninstall the F5 CRDs and the CNE core using Helm.