---
title: "Install wasmCloud — CLI and Kubernetes | wasmCloud"
description: "Install the wash CLI and deploy wasmCloud to Kubernetes for running secure WebAssembly components across any cloud, datacenter, or edge environment."
canonical: "https://wasmcloud.com/docs/installation/"
---

Version: v2

# Install wasmCloud

Install the parts of the [wasmCloud platform](https://wasmcloud.com/docs/overview/) that you need depending on what you want to accomplish:

- If you want to **develop and publish Wasm applications**, [install the Wasm Shell (`wash`) CLI](https://wasmcloud.com/docs/installation/#install-wash).
- If you want to **run Wasm workloads on Kubernetes**, [install wasmCloud on Kubernetes](https://wasmcloud.com/docs/installation/#install-wasmcloud-on-kubernetes).

For instructions to authenticate downloaded binaries, container images, and SBOMs, see [Verify releases](https://wasmcloud.com/docs/verify-releases/).

## Install `wash`

**macOS and Linux**

**Install script**

In your terminal, run the installation script to download and install the latest version of `wash` (**`2.12.2`**):

shell

```shell
curl -fsSL https://wasmcloud.com/sh | bash
```

The script installs `wash` to `~/.wash/bin` and automatically updates your shell profile. Open a new terminal session to use `wash`.

**Customizing the install location**

To install to a different directory, set `INSTALL_DIR`:

shell

```shell
curl -fsSL https://wasmcloud.com/sh | INSTALL_DIR=/usr/local/bin bash
```

To skip automatic PATH modification (for example, if you manage your own dotfiles):

shell

```shell
curl -fsSL https://wasmcloud.com/sh -o install.sh && bash install.sh --no-modify-path
```

**Homebrew**

If you have [Homebrew](https://brew.sh/) installed, you can install `wash` with:

shell

```shell
brew install wasmcloud/wasmcloud/wash
```

Homebrew updates your PATH automatically. You're ready to use `wash` in any terminal session.

**Windows**

**Install script**

In PowerShell, run the installation script to download and install the latest version of `wash` (**`2.12.2`**):

powershell

```powershell
iwr -useb https://wasmcloud.com/ps1 | iex
```

The script installs `wash` to `%USERPROFILE%\.wash\bin` and automatically adds it to your user PATH. Open a new terminal session to use `wash`.

**Customizing the install location**

To install to a different directory, set `INSTALL_DIR`:

powershell

```powershell
$env:INSTALL_DIR = "C:\tools\wash"; iwr -useb https://wasmcloud.com/ps1 | iex
```

To skip automatic PATH modification:

powershell

```powershell
iwr -useb https://wasmcloud.com/ps1 -OutFile install.ps1; .\install.ps1 -NoModifyPath
```

**winget**

If you have [winget](https://learn.microsoft.com/en-us/windows/package-manager/winget/) installed, you can install `wash` with:

powershell

```powershell
winget install wasmCloud.wash
```

winget updates your PATH automatically. Open a new terminal session to use `wash`.

**Source**

You will need [`cargo`](https://doc.rust-lang.org/cargo/getting-started/installation.html) to install from source.

shell

```shell
git clone https://github.com/wasmcloud/wasmCloud.git
cd wasmCloud
cargo install --path crates/wash
```

Pre-built binaries for macOS, Linux, and Windows are [available on GitHub](https://github.com/wasmcloud/wasmCloud/releases).

Verify that `wash` is properly installed and check your version for **`2.12.2`** with:

bash

```bash
wash -V
```

Now that `wash` is installed, the next step is to [build and publish a Wasm application](https://wasmcloud.com/docs/wash/developer-guide/build-and-publish/).

## Install wasmCloud on Kubernetes

Installation requires the following tools:

- [`kubectl`](https://kubernetes.io/docs/tasks/tools/#kubectl)
- [Helm](https://helm.sh/docs) v3.8.0+

You'll also need a Kubernetes environment. We recommend [`kind`](https://kind.sigs.k8s.io/docs/user/quick-start/#installation) for the best local Kubernetes experience.

### Local Kubernetes environment

You can use the one-liner below to start a `kind` cluster with a configuration from the [`wasmCloud/wasmCloud`](https://raw.githubusercontent.com/wasmCloud/wasmCloud/refs/heads/main/deploy/kind/kind-config.yaml) repository.

shell

```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
```

### Install the wasmCloud operator

Use Helm to install the wasmCloud operator from an OCI chart image, using the [values for local installation](https://raw.githubusercontent.com/wasmCloud/wasmCloud/refs/heads/main/charts/runtime-operator/values.local.yaml). The overlay disables the deprecated Runtime Gateway by default — HTTP traffic is routed by the operator via EndpointSlices tied to standard Kubernetes Services:

shell

```shell
helm install wasmcloud --version 2.12.2 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
```

> **Existing wasmCloud state in the cluster**
>
> If you've previously installed the wasmCloud operator (in any namespace), `helm install` may fail with:
>
> text
>
> ```text
> Error: INSTALLATION FAILED: ... ClusterRole "wasmcloud-runtime-operator-..." cannot be imported into the current release
> ```
>
> Helm 3 does not re-import cluster-scoped resources owned by a previous release. If you no longer need the prior install, fully clean up its cluster-scoped resources:
>
> shell
>
> ```shell
> helm uninstall wasmcloud --namespace <previous-namespace>
> kubectl delete clusterrole -l app.kubernetes.io/instance=wasmcloud
> kubectl delete clusterrolebinding -l app.kubernetes.io/instance=wasmcloud
> kubectl delete crd -l app.kubernetes.io/instance=wasmcloud
> ```
>
> **Deleting the CRDs also deletes any existing `WorkloadDeployment`, `Host`, `Workload`, `WorkloadReplicaSet`, and `Artifact` resources in the cluster.** Make sure you have manifests checked in (or otherwise saved) for anything you want to recreate before running the CRD delete.
>
> After cleanup, re-run the install command above.

Verify the deployment:

shell

```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 workload

Apply the [wasmCloud-hosted manifest](https://raw.githubusercontent.com/wasmCloud/wasmCloud/refs/heads/main/templates/http-hello-world/manifests/workloaddeployment.yaml), which contains a `NodePort` Service and a `WorkloadDeployment` that references it by name. The operator creates an EndpointSlice for the Service pointing at the host pods running the workload, so the NodePort on port 30950 (mapped to host port 80 by the kind cluster config) reaches the component directly:

shell

```shell
kubectl apply -f https://raw.githubusercontent.com/wasmCloud/wasmCloud/refs/heads/main/templates/http-hello-world/manifests/workloaddeployment.yaml
```

Use `curl` to invoke the Wasm workload with an HTTP request:

shell

```shell
curl localhost -i
```

text

```text
Hello from wasmCloud!
```

For more information on each of these steps, see [Kubernetes Operator](https://wasmcloud.com/docs/kubernetes-operator/).

## Clean up

Delete the workload deployment and its Service:

shell

```shell
kubectl delete workloaddeployment hello-world
kubectl delete service hello-world
```

Uninstall wasmCloud:

shell

```shell
helm uninstall wasmcloud --namespace wasmcloud
```

Delete the local Kubernetes environment:

shell

```shell
kind delete cluster
```

## Next steps

- Read the [Overview](https://wasmcloud.com/docs/overview/) for an explanation of core concepts in wasmCloud.
- Explore the [`wash/examples` directory](https://github.com/wasmCloud/wasmCloud/tree/main/examples) for more advanced Wasm component examples.
- Check out the [Developer Guide](https://wasmcloud.com/docs/wash/developer-guide/) for information on building Wasm components.

Last updated on **Nov 20, 2026** by **Victor Adossi**
