Kuat

There are pros and cons to each. You can't do mTLS with simple calls, which you need to call in-cluster backends. I think we need both versions: one for basic...

How did you compile the module? Wasm instruction set does not support exceptions in principle (it does not have goto), so relooper must be applied to structure the control flow....

Looks like code is compiled with O3 which disables all exception handling. See https://emscripten.org/docs/optimizing/Optimizing-Code.html#optimizing-code-exception-catching. DISABLE_EXCEPTION_CATCHING=0 can override but Emscripten recommends against exceptions to keep code small and fast. On Wed,...

> I just read up a bit on relooper, I don't fully understand though how it would help with exception handling? > It seems to process a CFG, that is...

@ijsnellf I'm driving the effort. All the bits are in place, but not connected end-to-end. Mixer rules will allow using expressions for header values, which can depend on request attributes...

@linsun We don't want to do this _just_ with mixer rules. For simple things, route rules work fine. You need Mixer for any external adapters trying to influence request metadata....

@linsun Let me clarify. Mixer-driven header operations are not meant for automatic header propagation. It's meant for building higher-level workflows with adapters and istio config. For example, a mixer authorization...

@costinm 1. All variations are possible: - local rate limit on outbound route at ingress; - global rate limit on outbound route at ingress; - local rate limit on app...

Right, I haven't heard a single use case that only needs service-service rate limit. The least common denominator API does not answer anyone's needs. You are right, this is just...

It's ok to retry on 429/503 but the client needs to back-off. I think what John suggested is just a regular LB which does not take into account back pressure....