No matches for kind "PerconaServerMongoDB" in version ""

I have the Percona Server for MongoDB operator installed in our cluster (version 1.12.0) and I am now trying to install Percona Server for MongoDB and getting this error:

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: unable to recognize “”: no matches for kind “PerconaServerMongoDB” in version “

I have uninstalled and re-installed the operator and I am installing percona server for mongodb with default helm chart options - I’m not even customizing anything.

If I do a kubectl get PerconaServerMongoDB I don’t see anything. What creates that? The operator? If so why would the operator install successfully but not install the custom resource?

1 Like

I got logs on the operator and see this:

{“level”:“error”,“ts”:1653068179.3692636,“logger”:“controller-runtime.source”,“msg”:“if kind is a CRD, it should be installed before calling Start”,“kind”:“”,“error”:"no matches for kind “PerconaServerMongoDB” in version “"”,“stacktrace”:“*Kind).Start.func1.1\n\t/go/src/\\n\t/go/src/\\n\t/go/src/\\n\t/go/src/\*Kind).Start.func1\n\t/go/src/”}

1 Like

I ended up using:


kubectl delete -f crd.yml
kubectl create -f crd.yml

Then installing the operator, then installing the percona mongo db helm chart. That seemed to work. :crazy_face:

1 Like

Hello @Brad_Baker1 ,

I’m not sure what was happening here. Seems that you were using a CRD of older version, but trying to apply the CR of the newer one.

Just get the CRD and CR from the same branch:

git clone -b v1.12.0
1 Like