Regarding the cluster generated for the ServiceEntry about istio HOT 8 OPEN

cc @howardjohn @hzxuzhonghu

from istio.

ref Issue: #50119

from istio.

If user wants the FQDN they should use it directly. I am not sure its appropriate for us to assume they do not want DNS searching.

For the double endpoint, are you sure you have just that SE? The port is 8081 which suggests to me you may have another SE so its merging and adding both endpoints

from istio.

If user wants the FQDN they should use it directly. I am not sure its appropriate for us to assume they do not want DNS searching.

Is it only possible to write FQDN to Endpoint under serviceEntry? The host should be also used for other purposes, and it would be a problem to write it as a FQDN directly, right?

For the double endpoint, are you sure you have just that SE? The port is 8081 which suggests to me you may have another SE so its merging and adding both endpoints

There is no second serviceEntry, just because of my editing mistake.

from istio.

I cannot reproduce the double endpoints, can you give more info

from istio.

I cannot reproduce the double endpoints, can you give more info

There are some gateway resources configured in the environment that may be relevant to this.

from istio.

Endpoints are generated from inner endpointShard, which is generated from endpointslice controller or SE controller. I am sure it is unrelated to any gateway resource

from istio.

Endpoints are generated from inner endpointShard, which is generated from endpointslice controller or SE controller. I am sure it is unrelated to any gateway resource

the Endpoints (static) configdump have load_balancing_weight property, It may be related to the EndpointsByNetworkFilter

from istio.