perf: Initial configuration takes too long

[martin-schulze-e2m]

Issue Faced

When starting up the ingress controller with several route CRDs (8 routes, 6 upstreams), it takes about 5 minutes to send the first sync request to the apisix instance. This means that there is a downtime of 5m if no apisix instance has the current configuration, e.g. when migrating from another chart (bitnami).

Logs

Note the timestamps

{"level":"info","message":"ADC server is running on: /sockets/adc.sock","timestamp":"2026-02-27T09:26:11.662Z"
{"level":"info","message":"PUT /sync","requestId":"ef75a39f-035f-4d18-8d2e-5dc3c10d9870","timestamp":"2026-02-27T09:31:43.141Z"} 

Steps to Reproduce

1. Install apisix helm chart
2. observe apisix pod not ready for ~5 minutes

Environment

• APISIX Ingress controller version: image apache/apisix-ingress-controller:2.0.1

Version: 2.0.1
Git SHA: 
Go Version: go1.24.11
Building OS/Arch: /
Running OS/Arch: linux/amd64

• Kubernetes cluster version (run kubectl version): v1.29.15