Uninstall the JFrog Crossplane Providers

Remove the JFrog Crossplane providers from your cluster. Follow the steps in the order shown.

If you remove the providers first, managed resources stay stuck in Terminating state. This happens because no active controller remains to remove their finalizers.

Prerequisites

• The providers are installed. For more information, see Install the JFrog Crossplane Providers.

Uninstall the Providers

1. (Optional) To keep objects in JFrog after uninstallation, remove Delete from managementPolicies. For legacy resources, set deletionPolicy: Orphan.

2. Delete managed resources in dependent order:

   1. Watches before policies
   2. Environments, roles, and assignments before projects
   3. Virtual repositories before local and remote repositories

3. Wait until kubectl get managed -A returns no resources.

4. Delete provider configurations:

   • For each provider, run kubectl delete clusterproviderconfigs.<provider>.m.crossplane.io --all.

     Replace <provider> with each provider's API group name: artifactory, xray, project, or platform.

   • Also delete namespaced and legacy provider configurations.

5. Delete the Providers. Wait until kubectl get providerrevisions returns no resources. Then remove leftover CRDs:

   Shell

   kubectl get crds -o name | grep -E '\.(artifactory|xray|project|platform)(\.m)?\.crossplane\.io$' | xargs kubectl delete

6. Delete the DeploymentRuntimeConfig and the jfrog-registry and jfrog-creds Secrets.

7. (Optional) Run helm uninstall crossplane -n crossplane-system.

   Helm keeps CRDs when you uninstall. Manually delete the remaining *.crossplane.io CRDs and the leftover Crossplane webhook configurations.

   If lock.pkg.crossplane.io/lock stops responding, clear its finalizers with:

   Shell

   kubectl patch lock.pkg.crossplane.io lock --type merge -p '{"metadata":{"finalizers":[]}}'

Next Steps

• To install the providers again, see Install the JFrog Crossplane Providers.