rabbitmq operator watch configmaps when configmaps too many and large it will failed

[jisongxi]

version 1.14.0

when I create the rabbitcluster , but no pod and sts created, i see the log from the operator pod as this:

how to fix the problem

[mkuratczyk]

This seems to be an issue with your Kubernetes cluster, not a RabbitMQ / cluster operator issue.
Kubernetes API responds with a "internal error".

As additional evidence, a completely different project had a virtually identical issue reported and reached a similar conclusion:
fluxcd/source-controller#1137

[jisongxi]

My k8s cluster has a lot of configmaps. Can rabbitmq operator only monitor the required configmaps? Is it because there are too many configmaps, causing rabbtimq to pull the configmap reading of the entire cluster and time out?

[mkuratczyk]

If that's what causes the problem, it's likely fixed on the main branch already: #1549

We need to ship a new version with this change though