> ## Documentation Index
> Fetch the complete documentation index at: https://docs.akua.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Local testing
> Test your applications locally with Multipass before deploying to production
Multipass is the perfect tool for testing worker configurations locally without any cloud costs. Built by Canonical specifically for testing scenarios, Multipass lets you quickly spin up Ubuntu VMs on your local machine to test worker setups before buying production machines. It provides free local testing, rapid iteration (quickly create, destroy, and recreate test workers), and production simulation (test exact worker setup procedures in a local environment).
**Performance considerations**: Local testing with Multipass will be slower than production servers due to your home internet connection (typically much slower than datacenter 1–10+ Gbps links) and limited local resources. Ensure your VM has at least 1 CPU and 3 GB RAM for reliable testing.
Akua's managed KaaS architecture is designed so your workers don't need a public IP address. When a worker starts, it automatically creates an outbound Konnectivity tunnel to the control plane, allowing the control plane to reach the kubelet securely.
## Prerequisites
Install Multipass on your development machine:
**Using Homebrew (recommended)**
```bash Install Multipass theme={null}
brew install multipass
```
**Manual download**
Download from [https://multipass.run](https://multipass.run)
Install the .pkg file
```bash Verify installation (macOS) theme={null}
multipass version
```
**Using Snap (recommended)**
```bash Install Multipass theme={null}
# Ubuntu/Debian and most Linux distributions
sudo snap install multipass
```
**Manual download**
Download from [https://multipass.run](https://multipass.run)
Follow distribution-specific installation instructions
```bash Verify installation (Linux) theme={null}
multipass version
```
**Using Chocolatey (recommended)**
```powershell Install Multipass theme={null}
choco install multipass
```
**Manual download**
Download installer from [https://multipass.run](https://multipass.run)
Run the .exe installer
```powershell Verify installation (Windows) theme={null}
multipass version
```
## Setting up a test worker
First, ensure you have an active cluster in your [Akua dashboard](https://akua.dev/clusters). You'll need the worker setup command from this cluster.
Create a new Ubuntu VM with adequate resources for testing:
```bash Create and verify VM theme={null}
# Create VM with recommended specs for testing
multipass launch --name akua-worker --cpus 2 --memory 4G --disk 20G
# Verify VM is running
multipass list
```
Use `--cpus 4 --memory 8G` for more realistic production testing scenarios.
```bash Connect to VM theme={null}
# SSH into the Multipass VM
multipass shell akua-worker
```
You're now inside the Ubuntu VM, ready to test the worker setup.
In your Akua dashboard, navigate to your [active cluster](https://akua.dev/clusters), click the **"Quick Actions"** menu, select **"Add a worker"**, and copy the bootstrap command.
Inside the Multipass VM, run the worker setup command:
The setup will automatically:
* Install Kubernetes components
* Configure networking
* Join the worker to your cluster
* Establish outbound tunnel to control plane
Check your Akua dashboard — the worker should appear as "Active" within 1–2 minutes.
Your test worker is now connected and ready for testing product installs.
## Testing product installs
With your Multipass worker connected, you can test complete product install workflows:
1. **Create test products** in your Akua dashboard
2. **Deploy to test cluster** using your Multipass worker
3. **Verify installs** work correctly
4. **Iterate configurations** without cloud costs
**Product ingress considerations**: If your product exposes services and expects a public IP, you'll need to use your local VM's IP address instead. Get it with `multipass info akua-worker`. This depends on each product's deployment — some products use cloudflared tunnels which work without extra configuration, while others may require manual IP configuration for local testing.
## Cleanup and management
### VM management
```bash Manage VM lifecycle theme={null}
# Stop the VM when not testing
multipass stop akua-worker
# Start it again when needed
multipass start akua-worker
# Delete when done testing
multipass delete akua-worker
multipass purge
```
### Worker cleanup
When you're done testing, remove the worker from your cluster:
1. In the Akua dashboard, go to your cluster
2. Find the Multipass worker in the worker list
3. Remove it to keep your cluster clean
## Advanced testing scenarios
Test multi-worker scenarios by creating multiple VMs:
```bash Create multiple test workers theme={null}
# Create additional test workers
multipass launch --name akua-worker-2 --cpus 2 --memory 4G --disk 20G
multipass launch --name akua-worker-3 --cpus 2 --memory 4G --disk 20G
# Connect each one using the same worker setup command
```
Test with minimal resources to simulate constrained environments:
```bash Create minimal test worker theme={null}
# Minimal test worker
multipass launch --name akua-minimal --cpus 1 --memory 2G --disk 10G
```
Test network scenarios by configuring Multipass networking:
```bash Create network test VM theme={null}
# Custom network configuration
multipass launch --name akua-network-test --network name=bridge
```
## Troubleshooting
* Check available system resources (CPU, RAM, disk)
* Verify Multipass service is running: `multipass version`
* Try with lower resource requirements: `--cpus 1 --memory 2G`
* Ensure VM has internet connectivity: `curl -I https://akua.dev/worker.sh`
* Verify the worker token hasn't expired (30 minutes)
* Try the setup command with `sudo` explicitly
* Wait 2–3 minutes for registration to complete
* Check VM system time is synchronized
* Verify outbound HTTPS connections work
* Check Akua dashboard shows cluster as "Active"
## Related topics
Use the same commands on production servers.
Understand how clusters work in Akua.
Set up a managed cluster to test against.
Add persistent storage to your test cluster.