Stuck Kubernetes Resource

Percona News Awards & Recognition
1

I was testing the Percona MongoDB operator and have some stuck resources. I created a namespace percona-mongodb which I can’t delete now due to the remaining resources.

If I run

kubectl api-resources --verbs=list --namespaced -o name \
  | xargs -n 1 kubectl get --show-kind --ignore-not-found -n percona-mongodb

I get this result
perconaservermongodb.psmdb.percona.com/mongodb-psmdb-db stopping 7d2h

If I try to force delete or patch (no finalizers) perconaservermongodb.psmdb.percona.com/mongodb-psmdb-db it says the resource wasn’t found.

Anyone know how I can delete this thing?

2

I was able to delete it after using --type=merge with the patch request.

kubectl patch perconaservermongodb.psmdb.percona.com/mongodb-psmdb-db -n percona-mongodb -p '{"metadata":{"finalizers":[]}}' --type=merge

3

@sloan58 some of our finalizers are quite strict to ensure that database consistency is intact. For example:

- percona.com/delete-psmdb-pods-in-order

I guess that was exactly the prob.
If you can provide more details, we might dig deeper. Or improve the experience here.