Tiger Xu / Zhonghu Xu

@howardjohn @ramaraochavali What do i need to promote this feature?

An special case i can think of is in multi tenant case, multi istio can be deployed in a single cluster. We donot want the crd{CR} to interference each other.

@howardjohn https://github.com/istio/istio/issues/31115

I donot think there are many users of discoverySelector who have CR created in namespaces that are not selected. For sake, I am fine to add a knob for this....

@howardjohn Can this be used for multi tenancy RFC https://docs.google.com/document/d/1y4liRJbQW0NCMeQtqMma46flVqs-izV1/edit?usp=sharing&ouid=105743966233121608166&rtpof=true&sd=true

Great， one selector makes much sense to me

What lb policy do you set? Better provide the gateway configdump

Is it because of connection reuse? The two requests goes to the same echo-server.

This is only my guess, for multi cluster gateway, gateway will lb the HTTP requests as TCP. So would you try more requests?

Yes, right, it is the connection reuse, lol