Operator taking 10-30 minutes to create new cluster/existing cluster change

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.12.2
• **Where do you run it - cloud or metal? Kubernetes
• Are you running Postgres Operator in production? yes
• Type of issue? question

Hi All,

we are using postgres operator(12.2). Number of cluster has been increased to 500 and we are facing delay in the new cluster creation or any change w.r.t CR. It is taking 10-30 minutes.

We also see below log messages in the operator.

I1105 06:03:54.604950 1 request.go:697] Waited for 1.58998395s due to client-side throttling, not priority and fairness, request: POST:https://192.168.128.1:443/api/v1/namespaces/pg-cluster/secrets

Current config :

requests:
cpu: 1
memory: 2Gi
limits:
cpu: 2
memory: 4Gi

workers: 8
resync_period: 30m
repair_period: 5m
CPU Max usage - 3%
MEM Max usage - 26%

could you please suggest whether we need to change any above config?

No files, tests, or entry points are named. Start by reviewing the operator's Kubernetes API client-throttling log alongside the reported worker, resync, repair, and resource settings; done means identifying the cause of the 10–30 minute delay and documenting a supported configuration change or next diagnostic step.