Kuack: Transforming Browsers into Kubernetes Worker Nodes

Kuack is a Virtual Kubelet provider that transforms browsers into Kubernetes worker nodes, enabling distributed computing at the edge using WebAssembly.

What is Kuack?

Kuack enables Kubernetes to schedule WebAssembly (WASM) workloads to browser-based agents. Instead of running pods on expensive cloud servers, Kuack can execute them in users' browsers - turning millions of idle devices into a massive compute cluster.

Key Features

• Virtual Kubelet Integration: Works with standard Kubernetes APIs
• Multi-Platform Support: Same image runs on Linux nodes and browser agents
• Zero Installation: Works in any modern browser
• Resource Aggregation: Sums CPU, memory, and GPU from connected agents

Overview of Functionality

1. Agent Connection: Browser agents connect to Kuack Node using WebSockets to report their available resources.
2. Resource Aggregation: Kuack Node sums the resources from all connected agents, presenting a virtual node to Kubernetes.
3. Pod Scheduling: Kubernetes schedules WASM-compatible pods to the virtual node, and the Node selects an available agent for execution.
4. WASM Execution: Agents download the WASM binary from the Registry Proxy and execute it directly in the browser.
5. Result Streaming: Execution results and logs are streamed back to the Kubernetes cluster via the Node.

Limitations

Kuack is designed for specific workload types:

• Stateless workloads
• CPU-intensive tasks
• Short-lived jobs
• WASM-compatible code

It's not an option for:

• Stateful services (databases, caches)
• Long-running services
• Privileged operations
• Network services (listening on ports)

Contributing

Contributions are welcome! Areas where help is needed:

• Documentation improvements
• Additional example applications
• Bug fixes and stability improvements
• Feature implementation

Links

• Website: https://kuack.io

Status

Early Development: Kuack is currently a proof of concept. Not recommended for production workloads yet.