Keith Mattix II
Keith Mattix II
I think a firmer support policy is useful here a la what we have for k8s. Saying something like: "Istio will support as stable the standard channel for the last...
This is a Kubernetes validation: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names. Is there a reason you need mixed-case services?
Yeah agreed, I definitely underestimated the # of people who relied on host header match for service routing. (1) is probably the least controversial approach...I can anticipate lots of strong...
@LugiaChang is your Wasm plugin written in Javascript by any chance?
Hm, in that case, I think v8 is throwing the error; in my experience, RangeError comes from Javascript world. I think what is happening is that your stress test looks...
IMO, I wouldn't worry about this too much from a production perspective. Unless someone is trying to DoS you, you probably won't trigger the conditions for this. We should definitely...
Well the issue is that your stress tester is sending too many resets too quickly; regular service traffic shouldn't be resetting that soon
@howardjohn @ramaraochavali what's the expected behavior here? One of the changes in #48071 is that wildcard host matching stopped being bidirectional (this was one of the things that was causing...
@qts0312 What's your use-case? Is there a reason your FQDN VirtualService needs to match a wildcarded ServiceEntry?
@qts0312 I think this is actually very simple: the curl is to port 9090, and the VirtualService is only for port 80. Therefore, the only route on port 9090 is...