Lucas will show how to use Kubernetes secrets with wasmCloud components and capability providers.
You can use Kubernetes as the secrets backend for a given policy, and then a component or provider can use a secret with that policy.
The secrets backend is a binary that runs alongside the wasmCloud host.
Lucas demonstrates a simple application consuming the secret and then revealing it in the terminal.
By integrating with Kubernetes secrets, you get access to the entire Kubernetes secrets ecosystem—you can make use of secrets stored in the AWS secrets manager or wherever else.
Jochen: This is awesome for enabling people to use deployed infrastructure that they already have.
Brooks: So you deploy this, and you have a one-stop-shop for using secrets with wasmCloud on Kubernetes.
Joonas: There is a plan to also create a native integration for AWS Secrets Manager down the line, but this is a great way to unlock the use cases we don’t have a “native” backend implementation for today.
WASI 0.2.1 is coming this week. In wasmCloud, we will get this as an update to wasmtime.
Users won't need to update anything on component, provider, or host side.
The main feature coming in WASI 0.2.1 is feature gates, allowing you to provide features "since" a certain version in the WIT.
This way, you'll know if your runtime supports a new feature before instatiation.
Bailey: It will probably be a couple of weeks for wasmtime to update and then for us to consume that within wasmCloud. The other thing to note is that we've added a lot more documentation inside of WASI interfaces themselves.