Instead of creating the resource in every sync cycle, first check whether it already exists.

Bug Report

What version of Kubernetes are you using?

EKS v1.30

What version of TiDB Operator are you using?

all version

What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?

What's the status of the TiDB cluster pods?

What did you do?

What did you expect to see?
Instead of creating the resource in every sync cycle, first check whether it already exists.

What did you see instead?
TiDB Operator uses a reconcile mechanism. In each sync cycle, it attempts to create resources. Since the resources already exist and haven't changed, Kubernetes returns a 409 Conflict error. As shown in the picture, you can see many create attempts followed by 409 errors.
By default, TiDB Operator reconciles every 30 seconds. If the TidbCluster (TC) status changes frequently—for example, under a high workload where tc.status.tikv.leaderCount is constantly changing—reconciliation will also be triggered more frequently.

Due to the high frequency of reconciliations, Kubernetes throttling may occur.

I0724 03:28:44.147312 1 request.go:645] Throttling request took 1.087973587s, request: POST:https://10.100.0.1:443/api/v1/namespaces/tidb-cluster/configmaps

Start by tracing the TiDB Operator reconcile cycle and its resource creation calls, focusing on the ConfigMap POST requests described in the report. Determine how existing resources are handled and verify that repeated reconciliations no longer produce 409 Conflict errors or unnecessary create attempts.