Community Calls
Path to wasmCloud v2: RC6 Plan, gRPC, P2→P3 WIT Translator & WIT Map Support
The first wasmCloud community call of 2026 — January 7 — focuses on the release plan for wasmCloud v2 RC6. Lucas Fontes walks through a GitHub project dashboard of the issues and PRs still open, what's validated vs needs validation, and which features land in v2.0 vs a fast-follow point release. The big additions targeted for RC6: multi-Wasm dev (services + components side-by-side), NATS authentication for the host and operator, Kubernetes workload IDs for resiliency, in-memory Blobstore and wasi-keyvalue in wash dev, and a published WIT package for wash. Deferred to point releases: component restart (semantics conflict with orchestrator behavior in clusters), virtual TCP/UDP loopback (waiting for Wasmtime 41 to avoid a Wasmtime fork), and integration tests with the new fixture handling. Aditya commits to refactoring the gRPC PR to be default behavior (not modular) by end of week. ossfellow shares his LLM-driven P2→P3 WIT translator built as a Goose recipe, which sparks a broader conversation about where this kind of tooling could live (personal repo first, possibly wasm-tools later). Yordis Prieto lands a major WIT map type addition to wasm-tools and is working on the Wasmtime host bindings for it next. Bailey closes with the v2 syntax changes from the latest WASI P3 RC and a discussion of the wash → wasmCloud monorepo move ahead.
wasmCloud v2 RC5: wash new, the Wasm Component Model & Agentic AI
The December 17, 2025 wasmCloud community call is a short, focused look at wasmCloud v2 Release Candidate 5 and the developer experience for building Wasm component model projects. Eric Gregory walks through how wash new has been refactored — the old interactive templating wizard is gone, replaced by cloning an example repo directly from a Git URL — and demos the updated Rust hello world that now uses the wstd standard library for Wasm components. Liam Randall closes with the news that the Linux Foundation has launched an Agentic AI Foundation, with Anthropic donating the Model Context Protocol (MCP).
WebAssembly on Kubernetes: Volume Mounts, Services & HTTP Ingress
The December 10, 2025 wasmCloud community call is all about running WebAssembly on Kubernetes in production. Eric Gregory walks through a new doc and demo for mounting Kubernetes volumes into a Rust component in wasmCloud v2, then shares a fresh overview of workload services as the stateful companions to stateless components. Lucas Fontes lays out the project's biggest remaining deficiency — HTTP ingress across many hosts — and proposes an intelligent ingress gateway that routes by ephemeral workload ID for zero-downtime deployments, all without tying wasmCloud to Kubernetes.
wasmCloud v2 Services, the Wasm Component Model & WASI P3
The December 3, 2025 wasmCloud community call digs into how the Wasm component model shapes wasmCloud v2, where a workload is composed of stateless components plus a new stateful primitive called a service. Lucas Fontes demos a service that opens TCP sockets and acts as localhost for the components in a workload — ideal for connection pooling, proxying, and persistent state — and the team explains how it leans on cooperative threads coming in WASI P3. The call also covers the move of WASI to a monorepo, the rename of the wasmCloud operator to the wadm operator, the C++ challenges behind compiling protobuf to WebAssembly, and the progress of the wasi-tls proposal.
C++ Wasm Components, gRPC & the Wasm Component Model in wasmCloud v2
The November 26, 2025 wasmCloud community call is a hands-on tour of the Wasm component model maturing across the C/C++ toolchain and into wasmCloud v2. Bailey Hayes demos a Bytecode Alliance example that builds a 67 KB WebAssembly HTTP server using modern, ergonomic C++ bindings on wasi:http, walks through how cooperative threads and exception handling are landing in wasi-libc, and shows protobuf compiling out of the box. The call closes with how gRPC rides over a protocol-agnostic wasi:http, plus a deep discussion of how workload identity works in wasmCloud v2 on Kubernetes — replacing v1's identity delegation with a unique workload ID assigned at scheduling time.