You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "martin-schulze-e2m (via GitHub)" <gi...@apache.org> on 2026/03/02 13:30:47 UTC
Re: [I] perf: Initial configuration takes too long [apisix-ingress-controller]
martin-schulze-e2m commented on issue #2726:
URL: https://github.com/apache/apisix-ingress-controller/issues/2726#issuecomment-3984412478
I restarted to get the logs from ingress controller:
```
# the three following lines repeat many times for different values
manager 2026-03-02T12:59:05.999Z INFO status.updater status/updater.go:143 received a status update {"namespace": "<redacted>", "name": "<redacted>", "kind": "ApisixUpstream"}
manager 2026-03-02T12:59:06.000Z INFO controller-runtime controller/controller.go:239 Starting Controller {"controller": "gateway", "controllerGroup": "gateway.networking.k8s.io", "controllerKind": "Gateway"}
manager 2026-03-02T12:59:06.000Z INFO controller-runtime controller/controller.go:248 Starting workers {"controller": "gateway", "controllerGroup": "gateway.networking.k8s.io", "controllerKind": "Gateway", "worker count": 1}
# the next line repeat 9x more times for different namespace/name pairs and state_counts within 4ms
manager 2026-03-02T12:59:06.002Z INFO readiness readiness/manager.go:163 marking resource as done {"gvk": "apisix.apache.org/v2, Kind=ApisixRoute", "name": {"name":"<redacted>","namespace":<redacted>"}, "state_count": 8}
manager 2026-03-02T12:59:06.002Z INFO controller-runtime controller/controller.go:239 Starting Controller {"controller": "ingress", "controllerGroup": "networking.k8s.io", "controllerKind": "Ingress"}
manager 2026-03-02T12:59:06.003Z INFO controller-runtime controller/controller.go:248 Starting workers {"controller": "ingress", "controllerGroup": "networking.k8s.io", "controllerKind": "Ingress", "worker count": 1}
manager 2026-03-02T12:59:06.003Z INFO controllers.Ingress controller/ingress_controller.go:153 reconciling ingress {"ingress": "apisix-data-plane"}
manager 2026-03-02T12:59:06.003Z INFO controllers.Ingress controller/ingress_controller.go:558 service not found {"namespace": "apisix", "name": "apisix-data-plane"} manager 2026-03-02T12:59:06.003Z INFO readiness readiness/manager.go:163 marking resource as done {"gvk": "apisix.apache.org/v2, Kind=ApisixGlobalRule", "name": {"name":"<redacted>","namespace":"<redacted>"}, "state_count": 1} manager 2026-03-02T12:59:06.003Z INFO readiness readiness/manager.go:163 marking resource as done {"gvk": "networking.k8s.io/v1, Kind=Ingress", "name": {"name":"apisix-data-plane","namespace":"apisix"}, "state_count": 2}
manager 2026-03-02T12:59:06.003Z INFO controllers.Ingress controller/ingress_controller.go:153 reconciling ingress {"ingress": "<redacted2>"} manager 2026-03-02T12:59:06.003Z INFO readiness readiness/manager.go:163 marking resource as done {"gvk": "networking.k8s.io/v1, Kind=Ingress", "name": {"name":"<redacted2>","namespace":"<redacted2>"}, "state_count": 1}
manager 2026-03-02T12:59:06.005Z INFO controller-runtime.KubeAPIWarningLogger log/warning_handler.go:65 unknown field "status"
manager 2026-03-02T12:59:06.005Z INFO status.updater status/updater.go:143 received a status update {"namespace": "<redacted>", "name": "<redacted>", "kind": "ApisixUpstream"}
manager 2026-03-02T12:59:06.006Z INFO readiness readiness/manager.go:163 marking resource as done {"gvk": "apisix.apache.org/v2, Kind=ApisixRoute", "name": {"name":"<redacted>","namespace":"<redacted>"}, "state_count": 0}
manager 2026-03-02T12:59:06.006Z INFO readiness readiness/manager.go:163 marking resource as done {"gvk": "apisix.apache.org/v2, Kind=ApisixRoute", "name": {"name":"<redacted>","namespace":"<redacted>"}, "state_count": 0}
manager 2026-03-02T12:59:06.010Z INFO controller-runtime.KubeAPIWarningLogger log/warning_handler.go:65 unknown field "status"
# next two lines repeat 3x more times for different namespace/name pairs within 16ms
manager 2026-03-02T12:59:06.010Z INFO status.updater status/updater.go:143 received a status update {"namespace": "<redacted>", "name": "<redacted>", "kind": "ApisixUpstream"}
manager 2026-03-02T12:59:06.014Z INFO controller-runtime.KubeAPIWarningLogger log/warning_handler.go:65 unknown field "status"
# the next line repeats 13x with different namespaces/name pairs within one millisecond (one of them is kind ApisixGlobalRule)
manager 2026-03-02T12:59:06.027Z INFO status.updater status/updater.go:143 received a status update {"namespace": "<redacted>", "name": "<redacted>", "kind": "ApisixRoute"}
manager 2026-03-02T13:04:05.882Z INFO provider apisix/provider.go:256 Ready detected, starting sync loop
manager 2026-03-02T13:04:05.882Z INFO provider.client client/client.go:177 syncing all resources
manager 2026-03-02T13:04:05.882Z INFO provider.client client/client.go:201 syncing resources for config {"service_number": 13}
adc-server {"level":"info","message":"PUT /sync","requestId":"b0223828-cf1c-4bae-83e2-099e26055f84","timestamp":"2026-03-02T13:04:05.893Z"}
```
If these I find most notable:
1. the missing service for ingress apisix-data-plane, which seems to come from the previous installation of the bitnami apisix chart. I have no idea why this was not removed. I deleted it manually and retried without seeing a difference in timing, but the log line is gone. (I would have wished for that to be level warn so it had more visibility.)
2. the `unknown field "status"` messages (no warning either!) that seems to be connected to upstreams which had already been installed with the bitnami chart
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org