Michael Bell

Are there known issues ? It seems problematic to wait a year until after java 21 comes out for an official wiremock 4 support

Jetty 11 is now EOL, so Jetty 12 support is needed.

You should never have unbounded or unset requests, or the node cannot fulfill the requests. Simple as that. If you feel like living semi-dangerously, override the defaults. But my opinion...

I think you guys are asking for it to be set to 10m/10m. That's fine. I think if memory serves it was originally request 10m/limit 100m, and I merely asked...

@Nowheresly yours is a partial fix and works because the mockhttprequest (iirc) explicitly mocks this interface. However if you play with cookies, you'll get another error, since the Cookie class...

Remember it actually didn't work even for that pod - once restarted it flipped out too!

It worked in the sense of emitting correcr metrics - until restarted - the worst of all worlds ;)

I agree that would be great . But other than introducing a first class metrics classifier (and hence being able maybe to add mock data ) I dunno how you...

I guess the very minimum would be nice if istio logs showed the cel expression that was faulty - the error message as is ain’t terribly easy to suss

I have my doubts "eating" the warning as opposed to logging it and displaying the faulty entry is good customer experience. But then that's why I opened this ticket for...