Community Calls
Custom Interfaces, Distributed RPC Errors & the Wasm Component Model
The February 26, 2025 wasmCloud community call digs into the Wasm component model and the realities of distributed computing. Brooks Townsend demos a proposal for handling transport-level failures in custom interfaces — a well-known RPC error type, defined in WIT, that lets a WebAssembly component gracefully catch errors like a missing link, an unreachable target, or a disconnected NATS, instead of trapping. The call also previews KubeCon EU 2025, walks through wasmCloud's new auto-generated release notes driven by conventional commits, and covers community questions on built-in providers, wasi:http, and a community-built Cron capability provider.
Robust Rollouts & Rollbacks for the Wasm Component Model
The February 19, 2025 wasmCloud community call is a deep dive into how the platform should roll out and roll back Wasm component model applications in production. Brooks Townsend walks through a large RFC for robust, zero-downtime upgrades: reporting component and provider status in the host inventory, shifting lattice-wide state writes out of individual hosts and into wadm via a new control interface, and making provider configuration a request/response operation so the host actually knows whether a rollout succeeded. The discussion ranges from CI and license-compliance housekeeping through to where canary and blue-green deployments fit — and whether the host should grow a Kubernetes-style extension model.
WebAssembly Workload Identity with SPIFFE/SPIRE and NATS
The February 12, 2025 wasmCloud community call is anchored by a live demo of WebAssembly workload identity. Joonas Bergius shows how wasmCloud can adopt SPIFFE — with the open-source SPIRE reference implementation — to give every host a cryptographically verifiable identity and secure its NATS connection through auth callout, without distributing any secrets. Brooks Townsend bookends the demo with a proposal to define wasmCloud's CloudEvents as auto-generated JSON Schema, a new conventional-commits pipeline for cleaner release notes, and a plan to freeze wash while its library and CLI merge into one crate.
Workload Identity (SPIFFE) and wash Plugins as Wasm Components
The February 5, 2025 wasmCloud community call pairs two forward-looking RFCs. Joonas Bergius walks through a workload identity proposal built on SPIFFE — an infrastructure-agnostic, cryptographically verifiable identity for hosts, providers, and components that can secure NATS connectivity, enable secret-less OCI pulls, and establish mutual TLS across clusters. Then the team makes the case for turning the wash CLI into a Wasm component-based plugin system — the dog-food argument that the Wasm component model should be "the last plugin system you'll ever need." Brooks Townsend closes with a Q1 roadmap check-in.
WebAssembly and Kubernetes, Provider Supervision & wash 0.38
The January 29, 2025 wasmCloud community call leans into resilience and developer experience. Brooks Townsend demos a new feature that lets the wasmCloud host supervise and automatically restart a capability provider that exits unexpectedly, Taylor walks through a Helm chart that aggregates benchmarking results into ConfigMaps for CNCF testing infrastructure, and the team digs into the wash 0.38 release with extended registry overrides and interface wildcards. After the formal agenda, Bailey Hayes fields a community question on WebAssembly and Kubernetes — why wasmCloud integrates with Kubernetes rather than replacing it — and the call closes with a deep, freewheeling discussion of error handling, Protobuf, and WIT.