Uninstalling#

This page explains how to remove Dex Config Operator and its associated resources from your cluster.

Step 1 — Remove custom resources#

Delete all DCO custom resources before removing the operator. This ensures finalizers run and any managed resources are cleaned up properly.

kubectl delete clients --all -A
kubectl delete connectors --all -A
kubectl delete dexconfigs --all -A

Verify that no resources remain:

kubectl get clients -A
kubectl get connectors -A
kubectl get dexconfigs -A

Use the method that matches your original installation.

helm uninstall dex-config-operator

make undeploy

kubectl delete -f dist/install.yaml

Warning

Deleting CRDs removes all instances of those resources across the cluster. Make sure Step 1 is complete before proceeding.

make uninstall

Alternatively, delete the CRDs directly:

kubectl delete crd dexconfigs.auth.stakater.com
kubectl delete crd connectors.auth.stakater.com
kubectl delete crd clients.auth.stakater.com

If the operator namespace is no longer needed:

kubectl delete namespace dex-config-operator-system

Confirm that no operator pods, CRDs, or namespaces remain:

kubectl get crds | grep stakater
kubectl get namespace dex-config-operator-system

Both commands should return no results.