Crossplane Claim Deletion Hangs Indefinitely

In this tutorial, you'll learn about Crossplane Claim Deletion Hangs Indefinitely. We cover key concepts, practical examples, and best practices.

When you delete a Crossplane Claim, the underlying managed resources remain or the deletion hangs.

Wrong ❌

apiVersion: example.org/v1alpha1
kind: MyDatabase
metadata:
  name: my-db-claim
  # No deletionPolicy set, defaults to Orphan
spec:
  compositionRef:
    name: db-composition
  parameters:
    region: us-east-1
    size: small

Wrong Output

kubectl delete mydatabase my-db-claim
# hangs indefinitely
kubectl get mydatabase my-db-claim
NAME           SYNCED   READY   AGE
my-db-claim   True     True    30m   # Still exists with deletionTimestamp

Right ✅

apiVersion: example.org/v1alpha1
kind: MyDatabase
metadata:
  name: my-db-claim
spec:
  compositionRef:
    name: db-composition
  writeConnectionSecretToRef:
    name: db-connection
  resourceRefs:
    - apiVersion: aws.upbound.io/v1beta1
      kind: DBInstance
      name: my-db-claim-db
  claimRef:
    apiVersion: example.org/v1alpha1
    kind: MyDatabase
    name: my-db-claim
  deletionPolicy: Delete

Right Output

kubectl delete mydatabase my-db-claim
mydatabase.example.org "my-db-claim" deleted
# All composed managed resources are also deleted

Prevention

• Set deletionPolicy: Delete on the CompositeResource to cascade delete composed resources.
• Remove finalizers manually only as a last resort: kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge.
• Ensure the Crossplane provider has permissions to delete the managed resources.
• Check for pending managed resources that might block deletion: kubectl get managed.
• Use writeConnectionSecretToRef only when you need the connection secret to be exported.

DodaTech applies similar defensive patterns across Doda Browser, DodaZIP, and Durga Antivirus Pro infrastructure for production reliability.

Common Mistakes with claim delete

1. Forgetting deriving (Show, Eq) on custom data types needed for debugging
2. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
3. Using head and tail instead of pattern matching, causing runtime errors on empty lists

These mistakes appear frequently in real-world CROSSPLANE code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

This quick fix is part of the DodaTech infrastructure engineering series. Learn more at DodaTech tutorials.