1"use strict";(self.webpackChunkwasmcloud_com=self.webpackChunkwasmcloud_com||[]).push([["19441"],{49299:function(e,a,n){n.r(a),n.d(a,{assets:()=>m,contentTitle:()=>d,default:()=>p,frontMatter:()=>l,metadata:()=>s,toc:()=>c});var s=n(94609),t=n(85893),o=n(50065),i=n(15655),r=n.n(i);let l={date:"2025-01-15",title:"wasmCloud Q1 2025 Roadmap: WebAssembly on Kubernetes",description:"WebAssembly on Kubernetes leads wasmCloud's Q1 2025 roadmap call: simplifying Helm and NATS deployment, provider testing, WASI Preview 3, and API stabilization.",keywords:["wasmcloud","webassembly","wasm component model","webassembly kubernetes","wasi p3","capability providers","wasmcloud roadmap","wash cli"],chapters:[{seconds:200,label:"Welcome and Q1 2025 roadmap planning"},{seconds:625,label:"Should roadmap items auto-close as stale?"},{seconds:828,label:"Provider SDK testing framework"},{seconds:1192,label:"wasi-nn provider and a new provider per quarter"},{seconds:1340,label:"wash CLI autocomplete and auto-generated docs"},{seconds:1717,label:"Multi-tenancy, cron job provider, and community videos"},{seconds:2240,label:"Roadmap structure and the ingress RFC"},{seconds:2738,label:"Shared components vs a built-in ingress"},{seconds:2874,label:"Bundling wasmCloud and wadm into wash"},{seconds:3126,label:"Tracking WASI Preview 3"},{seconds:3661,label:"Simplifying the wasmCloud Helm chart and NATS"},{seconds:4439,label:"Stabilizing CloudEvents, host IDs, and image references"},{seconds:4834,label:"Built-in HTTP client and consolidating wash"}],image:"https://i.ytimg.com/vi/1jVV0kPh4wM/maxresdefault.jpg",duration:6161,showTitle:!0,slug:"2025-01-15-community-meeting",speakers:["liam-randall","masoud-baharlouie","florian-furstenberg","mark-kovari","aditya-salunkhe","bailey-hayes","colin-murphy","lachlan-heywood","yordis-prieto","jochen-rau"],about:"wasmCloud",mentions:["Kubernetes","WebAssembly","WASI","WASIPreview3","wash","NATS","wadm","capabilityProvider"]},d=void 0,m={authorsImageUrls:[]},c=[];function u(e){let a={p:"p",strong:"strong",...(0,o.a)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:["\n",(0,t.jsx)(r(),{url:"https://www.youtube.com/watch?v=1jVV0kPh4wM"}),"\n",(0,t.jsx)("div",{style:{textAlign:"right",marginTop:"0.25rem",marginBottom:"1.5rem"},children:(0,t.jsx)("small",{children:(0,t.jsx)("a",{href:"https://www.youtube.com/watch?v=1jVV0kPh4wM",target:"_blank",rel:"noopener noreferrer",children:"Watch on YouTube \u2197"})})}),"\n",(0,t.jsxs)(a.p,{children:["The January 15, 2025 wasmCloud community call is the project's ",(0,t.jsx)(a.strong,{children:"Q1 2025 roadmap planning"})," session. Liam Randall walks the GitHub roadmap board live, gathering community feedback on the work that matters most for the quarter. A recurring theme is ",(0,t.jsx)(a.strong,{children:"WebAssembly on Kubernetes"}),": simplifying the platform Helm chart and hiding the NATS requirement for operators, plus an RFC for minimal-footprint ingress. The call also covers a provider SDK testing framework, tracking ",(0,t.jsx)(a.strong,{children:"WASI Preview 3"}),", bundling wasmCloud and wadm into the wash CLI, and stabilizing wasmCloud's CloudEvents and control-interface APIs nearly a year after the 1.0 release."]})]})}function p(e={}){let{wrapper:a}={...(0,o.a)(),...e.components};return a?(0,t.jsx)(a,{...e,children:(0,t.jsx)(u,{...e})}):u(e)}},50065:function(e,a,n){n.d(a,{Z:()=>r,a:()=>i});var s=n(67294);let t={},o=s.createContext(t);function i(e){let a=s.useContext(o);return s.useMemo(function(){return"function"==typeof e?e(a):{...a,...e}},[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:i(e.components),s.createElement(o.Provider,{value:a},e.children)}},94609:function(e){e.exports=JSON.parse('{"permalink":"/community/2025-01-15-community-meeting","editUrl":"https://github.com/wasmCloud/wasmcloud.com-dev/edit/main/community/2025-01-15-community-meeting.mdx","source":"@site/community/2025-01-15-community-meeting.mdx","title":"wasmCloud Q1 2025 Roadmap: WebAssembly on Kubernetes","description":"WebAssembly on Kubernetes leads wasmCloud\'s Q1 2025 roadmap call: simplifying Helm and NATS deployment, provider testing, WASI Preview 3, and API stabilization.","date":"2025-01-15T00:00:00.000Z","tags":[],"hasTruncateMarker":true,"authors":[],"frontMatter":{"date":"2025-01-15","title":"wasmCloud Q1 2025 Roadmap: WebAssembly on Kubernetes","description":"WebAssembly on Kubernetes leads wasmCloud\'s Q1 2025 roadmap call: simplifying Helm and NATS deployment, provider testing, WASI Preview 3, and API stabilization.","keywords":["wasmcloud","webassembly","wasm component model","webassembly kubernetes","wasi p3","capability providers","wasmcloud roadmap","wash cli"],"chapters":[{"seconds":200,"label":"Welcome and Q1 2025 roadmap planning"},{"seconds":625,"label":"Should roadmap items auto-close as stale?"},{"seconds":828,"label":"Provider SDK testing framework"},{"seconds":1192,"label":"wasi-nn provider and a new provider per quarter"},{"seconds":1340,"label":"wash CLI autocomplete and auto-generated docs"},{"seconds":1717,"label":"Multi-tenancy, cron job provider, and community videos"},{"seconds":2240,"label":"Roadmap structure and the ingress RFC"},{"seconds":2738,"label":"Shared components vs a built-in ingress"},{"seconds":2874,"label":"Bundling wasmCloud and wadm into wash"},{"seconds":3126,"label":"Tracking WASI Preview 3"},{"seconds":3661,"label":"Simplifying the wasmCloud Helm chart and NATS"},{"seconds":4439,"label":"Stabilizing CloudEvents, host IDs, and image references"},{"seconds":4834,"label":"Built-in HTTP client and consolidating wash"}],"image":"https://i.ytimg.com/vi/1jVV0kPh4wM/maxresdefault.jpg","duration":6161,"showTitle":true,"slug":"2025-01-15-community-meeting","speakers":["liam-randall","masoud-baharlouie","florian-furstenberg","mark-kovari","aditya-salunkhe","bailey-h
1ayes","colin-murphy","lachlan-heywood","yordis-prieto","jochen-rau"],"about":"wasmCloud","mentions":["Kubernetes","WebAssembly","WASI","WASIPreview3","wash","NATS","wadm","capabilityProvider"]},"unlisted":false,"prevItem":{"title":"Transcript: wasmCloud Q1 2025 Roadmap Planning on Kubernetes","permalink":"/community/2025-01-15-community-meeting-transcript"},"nextItem":{"title":"Transcript: wasmCloud Monorepos & Composing Wasm Components Across Languages","permalink":"/community/2025-01-08-community-meeting-transcript"}}')}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.