GhangZh commented on issue #2028: URL: https://github.com/apache/apisix-ingress-controller/issues/2028#issuecomment-2081353991
> We also found the same problem, apisix-ingress-controller when comparing apisix crd declarative configurations with etcd data, requesting apisix would cause apisix cpu resources to go up, and then go down again after a while  > > ```shell > 2024-04-26T19:34:15+08:00 warn ingress/compare.go:186 pluginConfig: 799f92e3 in APISIX but do not in declare yaml > 2024-04-26T19:34:15+08:00 warn ingress/compare.go:186 pluginConfig: 1668e488 in APISIX but do not in declare yaml > 2024-04-26T19:34:15+08:00 warn ingress/compare.go:186 pluginConfig: 2059c8b3 in APISIX but do not in declare yaml > 2024-04-26T19:34:15+08:00 warn ingress/compare.go:186 pluginConfig: 97d60823 in APISIX but do not in declare yaml > 2024-04-26T19:34:15+08:00 warn ingress/compare.go:186 pluginConfig: 6d49039a in APISIX but do not in declare yaml > 2024-04-26T19:34:15+08:00 warn ingress/compare.go:186 pluginConfig: 47eee264 in APISIX but do not in declare yaml > 2024-04-26T19:34:15+08:00 warn ingress/compare.go:186 pluginConfig: 16cc31 in APISIX but do not in declare yaml > ``` I'm experiencing the same scenario, please help look at it. Now as soon as I restart apisix-ingress-controller, apisix cpu goes up and then down again, about 5k+ apisixroutes and 5k+ upstreams @shreemaan-abhishek @Sn0rt -- 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]
