Baoyuantop commented on issue #2783: URL: https://github.com/apache/apisix-ingress-controller/issues/2783#issuecomment-4667169991
Thanks for the detailed report @taherbohri. There seem to be two separate issues here. The first error: status.conditions[0].message: Too long: may not be more than 32768 bytes is a Kubernetes status update failure, not APISIX Gateway rejecting the route config. When sync fails, the ingress controller writes the failure details into the CRD condition message. With a large ApisixRoute / many paths, the aggregated message can exceed Kubernetes' limit for a condition message, and the status update is rejected. The controller should cap or summarize this message before writing it back to status. The later error: failed to sync config PUT /apisix/admin/configs HTTP/1.1 500 is a different failure in the ADC / APISIX standalone Admin API sync path. The access log only shows that APISIX returned 500; it is not enough to identify the root cause. In standalone mode, APISIX stores the full config in the `standalone-config` shared dict, whose default size is 10m, so a large generated config may hit a shared-dict capacity issue or another APISIX-side error. We need the APISIX error log or the ADC response body to confirm. Could you please provide: 1. APISIX Gateway `error.log` around the same timestamp, not only access log; 2. Full ingress-controller logs around `failed to sync config`; -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
