Community Calls

June 3, 2026

Agenda

• v2.3.0 released!
  • workload env/config/secrets in wash/config.yaml
  • bench infrastructure
  • namespace host plugin spans
  • wasmtime 45
  • wasi-otel rc2
  • Support runtime.wasmcloud.dev apiGroup RBAC to be namespaced vs Cluster
  • OTel trace roll-up
  • Operator fuzz testing
  • wasip3 canary image
  • moved building test fixtures to xtask
• DEMO: xtask changes
• DEMO: OTel trace roll-up
• DEMO: benches
• WASIP3 templates and examples https://github.com/wasmCloud/wasmCloud/issues/5015
• Additional roadmap items getting started #4939

Endive Java Wasm Host, JCO WASI P3 & the Component Model

The May 27, 2026 wasmCloud community call centers on the Wasm component model and the languages reaching it. Bailey Hayes demos Endive — the Bytecode Alliance's newly announced Java WebAssembly runtime — by building a wasmCloud host in Java that schedules workloads over NATS, and by embedding Wasm functions alongside plain Java handlers in an Eclipse Vert.x app. Victor Adossi shares that JCO 1.20 now passes all 46 upstream Wasmtime WASI P3 tests with a new Preview Three Shim, putting WASI P3 on track to launch in about two weeks, and the team walks its Q2 roadmap toward that release.

CI Hardening, Continuous Fuzzing & Cross-Component Streams

The May 20, 2026 wasmCloud community call opens with the launch of AI-generated meeting notes and transcripts for every wasmCloud Wednesday, then digs into security: Bailey Hayes walks through the wasmCloud 2.2 release, CI hardening with CodeQL and OpenSSF Scorecard, and a new continuous-fuzzing story for the Kubernetes runtime operator. Aditya demos component socket tunneling — a forked SQLx driver talking to MySQL over WASI sockets — which leads into a deep discussion of cross-component streams and futures in the Wasm component model, where Bailey argues that composing components is both simpler and ~5x faster than wiring them through the Wasmtime linker.

wasmCloud CI Hardening, Cache Pre-Compilation & Benchmarking

The May 13, 2026 wasmCloud community call covers CI security hardening — including cryptographic attestations for OCI artifacts, zizmor-based workflow linting, and status gates — alongside a deep look at the new cache artifact pre-compilation pipeline that offloads CPU-intensive Cranelift AOT compilation to a dedicated process. Bailey Hayes demos the "Are We Fast Yet?" performance dashboard with Criterion and Cachegrind benchmarks, and the team discusses Pulley interpreter performance (10x vs native, compared to 60x for JS/Python interpreters), WASI TLS progress, and the path to WASI P3.

WebGPU Demos, Namespace-Level Hosts & MySQL Connection Pooling

The May 6, 2026 wasmCloud community call packed in four demos showcasing WebGPU integration with TensorFlow.js and raw GPU compute, a major Kubernetes deployment change that moves wasmCloud hosts to namespace-level scope, a new workload configuration system for environment variables and secrets, and a MySQL connection pooling component built on WASI sockets. The call also covered the first successful automated release of wasmCloud v2.07 with CI hardening improvements.