Describe your problem
Currently, a couple of functions have WASM-support enabled (kptdev/krm-functions-catalog#898; kptdev/krm-functions-catalog#911; kptdev/krm-functions-catalog#921).
To actually be able to use these WASM-versions of the function, they need to also be built automatically when new tags are created, etc. and added to the multi-arch images available.
Open questions: how to deal with functions that have not been ported yet? Should there be an allowlist, how to indicate the availability of this in the catalog-docs?
For testing these versions of the functions #3587 is already there.
Describe your problem
Currently, a couple of functions have WASM-support enabled (kptdev/krm-functions-catalog#898; kptdev/krm-functions-catalog#911; kptdev/krm-functions-catalog#921).
To actually be able to use these WASM-versions of the function, they need to also be built automatically when new tags are created, etc. and added to the multi-arch images available.
Open questions: how to deal with functions that have not been ported yet? Should there be an allowlist, how to indicate the availability of this in the catalog-docs?
For testing these versions of the functions #3587 is already there.