澄潭

另外看上去是console界面上配置的，ingress yaml也提供下吧，在higress-system命名空间下

{"authority":"web.test.com","bytes_received":"0","bytes_sent":"15","downstream_local_address":"192.168.201.50:443","downstream_remote_address":"192.168.201.103:54807","duration":"9054","istio_policy_status":"-","method":"GET","path":"/ping?target=grpc.iotbull.com:443","protocol":"HTTP/1.1","request_id":"043d4be7-5aa9-474f-9bda-c5d58bda32ec","requested_server_name":"web.test.com","response_code":"503","response_flags":"URX","route_name":"web-test","start_time":"2024-04-08T10:29:24.954Z","trace_id":"f6c8e00c3196ec8cf5a37bfe645a6fa7","upstream_cluster":"outbound|80||go-web.default.svc.cluster.local","upstream_host":"172.20.135.157:8888","upstream_local_address":"172.20.85.192:52034","upstream_service_time":"9054","upstream_transport_failure_reason":"-","user_agent":"PostmanRuntime/7.37.0","x_forwarded_for":"192.168.201.103"} 看日志是HTTP/1.1呀，不是gRPC请求，而且upstream host字段是172.20.135.157:8888，没有请求8080

@ldl-home 有调试通吗，看你上面发的日志不是gRPC请求

We will implement this functionality through plugins instead of annotations This feature can be implemented by using routeCluster in the plugin and using it with httpcall. Interested developers are welcome...

@haifzhu 有点问题，应该在回调里迭代处理下一个trypath

@alexzzh 我更倾向于把这个开关加到higress core的xds侧，不侵入istio代码。在不开启istio资源的情况下，所有pilot discovery向envoy推送的配置都是由higress core转换生成的，所以只需在higress core侧开关控制即可。

嗯 可以的，controller的registry暴露统一的ready信息，再通过debug接口让Console查询比较合理，欢迎有兴趣的同学认领

ready状态统计可以基于： https://github.com/alibaba/higress/blob/8c817cf80a609481b89aa032be098d3c3c982446/registry/reconcile/reconcile.go#L236 提供debug查询接口可以扩展这里httpMux的handler： https://github.com/alibaba/higress/blob/8c817cf80a609481b89aa032be098d3c3c982446/pkg/bootstrap/server.go#L392-L402

@zzjin 这个configmap我们不希望放到用户命名空间下，而是放在系统命名空间下（如:higress-system)，统一交由集群SRE来管理

@2456868764 这个配置里的cert字段是否应该是higress的子字段比较合理