Meta tags:
description=Run WebAssembly on Kubernetes with the wasmCloud operator — native CRDs, Helm-based install, and ergonomic integration with your existing K8s cluster.;

Headings (most frequently used words):

wasmcloud, operator, the, kubernetes, on, makes, it, easy, to, run, and, webassembly, workloads, platform, get, started, with, clean, up, next, steps, install, deploy, wasm, component,

Text of the page (most frequently used words):
the (78), #wasmcloud (67), operator (33), cluster (25), kubernetes (24), and (21), for (20), kind (17), shell (17), runtime (15), service (14), hello (13), with (12), helm (12), world (12), workload (11), k3s (11), yaml (11), host (11), see (10), local (10), that (9), port (9), namespace (9), charts (9), nats (9), config (9), workloads (8), wasm (8), component (8), k3d (8), kubectl (8), values (8), https (7), hosts (7), http (7), default (7), via (7), you (7), chart (7), install (7), wash (6), delete (6), curl (6), can (6), main (6), create (6), get (5), platform (5), run (5), webassembly (5), resource (5), api (5), custom (5), crds (5), your (5), existing (5), ghcr (5), raw (5), githubusercontent (5), com (5), refs (5), heads (5), oci (5), version (5), gateway (5), community (4), this (4), lightweight (4), reference (4), definitions (4), workloaddeployment (4), from (4), svc (4), image (4), through (4), nodeport (4), name (4), traffic (4), pods (4), deploy (4), docker (4), all (3), linux (3), trademarks (3), page (3), security (3), next (3), started (3), overview (3), deployments (3), resources (3), more (3), examples (3), uninstall (3), running (3), deployment (3), verify (3), inside (3), full (3), expose (3), installation (3), manifest (3), components (3), spec (3), pointing (3), are (3), along (3), using (3), maps (3), use (3), kube (3), pattern (3), 30950 (3), directly (3), skip (3), 2026 (2), foundation (2), uses (2), list (2), trademark (2), usage (2), built (2), maintainers (2), slack (2), contributing (2), github (2), steps (2), clean (2), makes (2), easy (2), washlet (2), production (2), provides (2), section (2), used (2), environment (2), never (2), reachable (2), other (2), routing (2), note (2), guide (2), localhost (2), hostgroup (2), wasi (2), metadata (2), apiversion (2), exposes (2), endpointslice (2), set (2), will (2), user (2), sudo (2), loadbalancer (2), server (2), requirements (2), runs (2), following (2), command (2), ingress (2), each (2), also (2), deprecated (2), enabled (2), false (2), jetstream (2), these (2), infrastructure (2), copyright, llc, rights, reserved, has, registered, please, our, www, linuxfoundation, org, docusaurus, swag, contact, mailing, terms, conditions, privacy, policy, assessment, organization, youtube, linkedin, twitter, social, meeting, notes, calendar, wednesdays, previous, last, updated, eric, gregory, jun, edit, edge, constrained, alternative, securing, sandbox, model, networkpolicy, allowedhosts, complete, specification, explains, explore, advanced, directory, usr, bin, action, needed, remains, its, text, restart, curlimages, learn, about, walk, scale, hpa, keda, autoscaling, workloaddeployments, optimized, variant, answers, hosted, deploys, simple, interface, scheduled, incoming, handler, interfaces, package, hostinterfaces, hostselector, template, replicas, dev, v1alpha1, tcp, protocol, targetport, ports, clusterip, type, deploying, handles, takes, two, references, creates, whichever, once, ready, app, instance, find, configurable, build, own, provide, extended, capabilities, plugins, container, three, file, configures, which, chown, etc, rancher, mkdir, configure, sfl, distribution, only, prefer, typical, k8s, recipe, flag, node, without, going, bundled, traefik, flo, downloads, repository, starts, mapped, deletes, upon, completion, nodes, containers, info, already, have, creation, context, right, select, requires, tools, detailed, breakdown, responsibilities, request, flow, commonly, overridden, entire, deployed, installed, separately, wish, earlier, releases, included, separate, proxied, removed, future, release, now, handled, endpointslices, still, installs, pod, backwards, compatibility, reaches, standard, services, manages, defined, referenced, dns, resolves, cncf, project, connective, layer, transport, between, object, storage, carries, control, plane, communicates, sends, start, stop, requests, individual, subjects, self, register, publishing, heartbeat, messages, subscribes, bundles, automatically, connect, setting, endpoint, sandboxed, environments, binaries, surfaces, over, consists, core, parts, aligning, teams, adopt, progressively, integrate, tooling, registries, areas, cloud, native, ecosystem, leveraging, orchestrator, schedule, roadmap, governance, migration, troubleshooting, faq, glossary, recipes, templates, language, support, developing, introduction, developer, manual, cli, quickstart, what, search, star, 1500, docs, blog, content,

Text of the page (random words):
webassembly on kubernetes wasmcloud operator wasmcloud skip to main content wasmcloud blog community docs v2 v2 v1 0 82 star us 1500 github slack search get started what is wasmcloud installation quickstart platform overview wasm shell wash cli runtime kubernetes operator operator manual workload security custom resource definitions crds api reference developer guide introduction developing workloads language support templates examples recipes reference glossary faq troubleshooting migration to v2 community governance contributing maintainers roadmap kubernetes operator version v2 on this page kubernetes operator the wasmcloud operator makes it easy to run wasmcloud and webassembly workloads on kubernetes we use the operator pattern to run wasmcloud on kubernetes leveraging the orchestrator to schedule wasmcloud infrastructure and workloads by aligning to kubernetes teams can adopt webassembly wasm progressively and integrate wasmcloud with existing tooling for ingress registries ci cd and other areas of the cloud native ecosystem the wasmcloud platform on kubernetes along with the wasmcloud operator the wasmcloud platform on kubernetes consists of these core parts custom resource definitions crds for wasmcloud infrastructure and wasm workloads wasmcloud host s sandboxed runtime environments for webassembly components by default these are wash binaries using the wash host command to run a cluster host washlet that surfaces the wash runtime api over nats nats with jetstream cncf project that provides a connective layer for transport between operator and hosts along with built in object storage through jetstream nats carries all control plane traffic to the host the host never communicates directly with the kubernetes api the operator sends workload start stop requests to individual hosts via nats subjects and hosts self register by publishing heartbeat messages the operator subscribes to the helm chart bundles nats automatically you can also connect an existing nats cluster by setting nats enabled false and pointing the operator at your endpoint http traffic reaches workloads through standard kubernetes services the operator manages an endpointslice for each user defined service referenced by a workload so cluster dns e g my svc default svc cluster local resolves directly to the host pods see expose a workload via kubernetes service for the full pattern runtime gateway deprecated in 2 0 3 earlier releases included a separate runtime gateway deployment that proxied http traffic to workloads the gateway is deprecated as of 2 0 3 and will be removed in a future release routing is now handled by the operator via endpointslices the chart still installs a gateway pod by default for backwards compatibility set gateway enabled false to skip it the entire platform can be deployed with helm using the wasmcloud operator helm chart nats and hosts can also be installed separately if you wish for a detailed breakdown of each component s responsibilities and the request flow see the operator overview for commonly overridden chart values see the helm values reference get started with the wasmcloud operator installation requires the following tools kubectl helm v3 8 0 select your kubernetes environment existing cluster kind k3d k3s if you already have a kubernetes cluster skip cluster creation verify your kubectl context is pointing to the right cluster shell kubectl cluster info kind runs kubernetes nodes as docker containers requirements docker kind the following command downloads a kind config yaml from the wasmcloud wasmcloud repository starts a cluster with port 80 mapped for ingress and deletes the config upon completion shell curl flo https raw githubusercontent com wasmcloud wasmcloud refs heads main deploy kind kind config yaml kind create cluster config kind config yaml rm kind config yaml k3d runs a lightweight k3s cluster inside docker requirements docker k3d the port flag maps host port 80 to nodeport 30950 on the server node the hello world manifest exposes the workload as a nodeport service on port 30950 so this maps the wasm component directly to localhost 80 without going through k3d s bundled traefik loadbalancer shell k3d cluster create wasmcloud port 80 30950 server 0 if you d prefer the loadbalancer pattern more typical of k8s production deployments see the expose a workload via kubernetes service recipe k3s is a lightweight kubernetes distribution linux only install k3s shell curl sfl https get k3s io sh configure kubectl to use the k3s cluster shell mkdir p kube sudo cp etc rancher k3s k3s yaml kube config sudo chown user kube config install the wasmcloud operator use helm to install the wasmcloud operator from an oci chart image existing cluster kind k3d k3s shell helm install wasmcloud version 2 5 1 oci ghcr io wasmcloud charts runtime operator namespace wasmcloud create namespace f https raw githubusercontent com wasmcloud wasmcloud refs heads main charts runtime operator values local yaml the values local yaml file configures the host http port to 80 which the kind cluster config maps to host port 80 via a nodeport service shell helm install wasmcloud version 2 5 1 oci ghcr io wasmcloud charts runtime operator namespace wasmcloud create namespace f https raw githubusercontent com wasmcloud wasmcloud refs heads main charts runtime operator values local yaml shell helm install wasmcloud version 2 5 1 oci ghcr io wasmcloud charts runtime operator namespace wasmcloud create namespace f https raw githubusercontent com wasmcloud wasmcloud refs heads main charts runtime operator values local yaml shell helm install wasmcloud version 2 5 1 oci ghcr io wasmcloud charts runtime operator namespace wasmcloud create namespace f https raw githubusercontent com wasmcloud wasmcloud refs heads main charts runtime operator values local yaml along with the wasmcloud operator wasmcloud crds and nats the helm chart will deploy three wasmcloud hosts using the wasmcloud wash container image you can build your own hosts that provide extended capabilities via host plugins note you can find the full set of configurable values for the chart in wasmcloud wasmcloud charts runtime operator verify the deployment shell kubectl get pods l app kubernetes io instance wasmcloud n wasmcloud once all pods are running you re ready to deploy a wasm workload deploy a wasm component deploying a wasm component that handles http traffic takes two resources a kubernetes service that exposes the component and a workloaddeployment that references the service the operator creates an endpointslice for the service pointing at whichever host pods are running the workload yaml apiversion v1 kind service metadata name hello world spec type clusterip ports port 80 targetport 80 protocol tcp apiversion runtime wasmcloud dev v1alpha1 kind workloaddeployment metadata name hello world spec replicas 1 template spec hostselector hostgroup default kubernetes service name hello world components name hello world image ghcr io wasmcloud components hello world 0 1 0 hostinterfaces namespace wasi package http interfaces incoming handler this manifest deploys a simple hello world component that uses the wasi http interface scheduled on the default hostgroup and reachable inside the cluster at hello world default svc cluster local for a kind optimized nodeport variant that answers curl localhost on port 80 see the wasmcloud hosted hello world manifest used by the installation guide note learn more about workloaddeployments and other wasmcloud resources in the custom resource definitions crds section for the full service routing walk through see expose a workload via kubernetes service to scale a workloaddeployment with hpa or keda see autoscaling verify the component is reachable from inside the cluster shell kubectl run curl rm it image curlimages curl restart never curl s http hello world default svc cluster local text hello from wasmcloud clean up delete the workload deployment and its service shell kubectl delete workloaddeployment hello world kubectl delete service hello world uninstall wasmcloud shell helm uninstall wasmcloud delete the local kubernetes environment existing cluster kind k3d k3s no action needed your cluster remains running shell kind delete cluster shell k3d cluster delete wasmcloud shell usr local bin k3s uninstall sh next steps explore the wash examples directory for more advanced wasm component examples the custom resource definitions crds section explains the custom resources used by wasmcloud the api reference provides a complete api specification for securing workloads in production see workload security for the sandbox model allowedhosts and networkpolicy for edge or resource constrained deployments see lightweight deployments for a lightweight alternative to kind edit this page last updated on jun 16 2026 by eric gregory previous cluster hosts washlet next operator overview the wasmcloud operator makes it easy to run wasmcloud and webassembly workloads on kubernetes the wasmcloud platform on kubernetes get started with the wasmcloud operator clean up next steps community github contributing slack calendar wasmcloud wednesdays community meeting notes maintainers social twitter linkedin youtube organization security assessment privacy policy terms and conditions contact mailing list wasmcloud swag copyright 2026 wasmcloud llc all rights reserved the linux foundation has registered trademarks and uses trademarks for a list of trademarks of the linux foundation please see our trademark usage page https www linuxfoundation org trademark usage built with docusaurus