wasmCloud is designed to fit seamlessly into existing cloud native ecosystems, integrating with Kubernetes using an operator to take full advantage of components and WASI APIs without re-platforming.
The WebAssembly component model enables a new world of composable, language-agnostic applications. But components aren’t containers. In order to take full advantage of the component model’s composability and interoperability, an orchestrator needs to be tailored to the WebAssembly ecosystem—not shoehorned in. wasmCloud uses the operator pattern and the open source wasmcloud-operator to smoothly interoperate with Kubernetes.
We can achieve smooth interoperability with Kubernetes and wasmCloud by using the operator pattern and the open source wasmcloud-operator.
Running wasmCloud alongside Kubernetes lets you take advantage of WebAssembly on Kubernetes without accepting artificial limits, and decoupling your WebAssembly functionality from your K8s clusters themselves keeps your system as flexible and maintainable as possible.
Up and down the stack, wasmCloud is designed to just work with cloud native standards.
wasmCloud’s policy service API makes it easy to communicate with external policy servers using engines like Open Policy Agent.
wasmCloud emits OpenTelemetry signals for traces, logs, and metrics, compatible with your favorite observability tooling.
Develop Backstage plugins with any language using Cosmonic Labs’ bigband project.
Smoothly integrate Argo CD for GitOps flow using our concordance-gitops example.
wasmCloud pulls Wasm components packaged as Open Container Initiative (OCI) images—so it’s simple to store application components and providers in your existing private registries.
wasmCloud manifests use the same Open Application Model specification in many different extensions to Kubernetes. If you’ve worked with K8s, you should be right at home.