G1

@oshai Sadly after upgrading the version, the same situation appears again. I encountered `ConnectionStillRunningQueryException` when running multiple read-only queries grouped with a transaction. [Here](https://github.com/jasync-sql/jasync-sql/blob/master/mysql-async/src/main/java/com/github/jasync/sql/db/mysql/MySQLConnection.kt#L344) This issue may seem to be...

@oshai Thanks to @FutureGadget, I found that query multiplexing in a same connection doesn't recommended. Now I can close this issue directly.

In Admin API, a state different from the `.spec.healthCheck.passive.healthy.httpCodes` defined in `ApisixUpstream` is being returned. ``` "active": { "type": "http", "concurrency": 10, "http_path": "/", "timeout": 1, "healthy": { "http_statuses": [...

It seems that health checks are made as they are without being rewritten to each host defined in `externalNodes` on the log. ``` 2024/03/07 13:27:02 [warn] 51#51: *1196791 [lua] balancer.lua:82:...

@tokers @tao12345666333 @Revolyssup @shreemaan-abhishek

@Revolyssup Logs below: ```yaml 2024-03-12T14:58:40+08:00 info ingress/ingress.go:121 init apisix ingress controller 2024-03-12T14:58:40+08:00 info ingress/ingress.go:123 version: Version: 1.8.0 Git SHA: no-git-module Go Version: go1.20.13 Building OS/Arch: linux/amd64 Running OS/Arch: linux/amd64 2024-03-12T14:58:40+08:00...

@Revolyssup The domains are modified and provided for security reasons. ```yaml apiVersion: apisix.apache.org/v2 kind: ApisixUpstream metadata: name: feature-flags-nodes-upstream spec: loadbalancer: type: roundrobin passHost: node scheme: https externalNodes: - type: Domain...

@Revolyssup Got these two lines below: ``` 2024-03-13T13:46:13+08:00 error apisix/apisix_upstream.go:845 update status {"status": {"conditions":[{"type":"ResourcesAvailable","status":"True","observedGeneration":1,"lastTransitionTime":"2024-03-13T05:46:13Z","reason":"ResourcesSynced","message":"Sync Successfully"}]}} W0313 13:46:13.985770 1 warnings.go:70] unknown field "status.conditions[0].lastTransitionTime" ```

@Revolyssup As you just mentioned, this is the result of erasing and re-applying both `ApisixRoute` and `ApisixUpstream`. ``` 2024-03-13T13:49:24+08:00 warn apisix/cluster.go:599 failed to check health for cluster default: dial tcp...

@Revolyssup It is distributed in the form of Helm Chart using ArgoCD, a CD tool, so I think you should see that it is distributed in the same namespace.