Marcos Candeia
Marcos Candeia
Totally! My bad, I really missed the assignment above, thanks for the headsup
I agree with @Taction, how about [proxy-wasm](https://github.com/proxy-wasm/spec) ABI especification? I don't know if it's too much for our middlewares but it supports a lot of operations and it is already...
cc: @johnewart @artursouza @yaron2 @tmacam
Excellent question, We can, but it requires changing our component registry behavior or a hint in the component crd telling the runtime if such component is pluggable(I’m not a fan...
>A runtime error would be the correct way to handle this scenario Runtime error in this case means shutting down the sidecar? Keep in mind that it could be out...
I like the simplicity but it seems that it blocks a lot of things in the way, for example, if we add more attributes in the pluggable component this needs...
Your proposal is fine considering the requirements now. But it is just a way to add an "inline" pluggable component, so we can move all fields from pluggable component crd...