Nick Young
Nick Young
I'd really recommend using the dynamic client with controller-runtime, as mentioned above by @bgagnon in https://github.com/projectcontour/contour/issues/2487#issuecomment-622074626. We are moving Contour in the direction of using the controller-runtime pieces more, for...
It's kind of intended that there not be matching rules, so this is really an escape valve for when that happens in error. If you want multiple targets for traffic,...
Thanks for these great notes @cten!
I think that we'll need to write this documentation again once the Operator has support for multiple installations as well.
I agree that there are risks of weird interactions, definitely. But I think the functionality it gives you is, on the whole, worth it. Being able to migrate from Ingress...
We haven't made any progress on this one for 1.16, moving to 1.17.
Still no progress, bumping to 1.18.
Currently, Contour's session persistence works like this: If you enable it, Contour will tell Envoy to generate a browser session cookie and hash backends based on that cookie. We achieve...
> Since the upstream service does not know the hashing algorithm that Envoy uses, it cannot possibly create a cookie that would lead to Envoy selecting that particular instance for...
I seem to recall that other load balancers allow specifying the backend by prepending it to the cookie text or something? Without something that allows the generating service to tell...