Home

K1S WorkerBee Wiki

WorkerBee is a local MCP workbench for building, deploying, probing, and exporting k1s-powered cloud-native applications on a developer machine. It is designed for coding agents, but the CLI is useful for human-driven local operations too.

Start Here

• Getting Started: install, start MCP, connect an agent, and run the first project.
• Installation: NixOS: Nix developer shell and NixOS trust guidance.
• Installation: Debian and Ubuntu: apt prerequisites, Python environment, and runtime setup.
• macOS Best Effort: source install, Docker or Podman, trust store notes, and unsupported edges.

Runbooks

• Basic Use: day-to-day commands for MCP, projects, manifests, logs, and probes.
• Operations Runbook: status checks, cleanup, restart patterns, trust, and security review.
• LAN Ingress, DNS, and CA: explicit LAN mode, WorkerBee DNS, CA download, and device setup.
• Advanced Operations: runtime selection, containerd privilege, remote k1s deploy, and artifact handoff.
• Advanced k1s Development: sibling k1s checkouts, direct containerd profiles, and profile validation.
• Direct Containerd k1s Profile Validation: copy/paste ops pattern for validating WorkerBee profiles from a sibling k1s agent shell.
• Troubleshooting: common failures and the first commands to run.

Core Capabilities

• Shared local MCP daemon with project-scoped state and lifecycle controls.
• Global dashboard with project controls, ingress state, DNS state, and CA download guidance.
• Local HTTPS ingress through Caddy for *.workerbee.localhost.
• Explicit LAN ingress with optional WorkerBee DNS forwarding for local devices.
• Dashboard CA download, explicit CA export, system trust, browser NSS trust, and LAN CA download workflows.
• Native k1s manifest staging, local deploy, remote k1s deploy, and bundle export.
• Image builds, status, logs, bounded exec, HTTPS probes, cleanup, and security review.
• Advanced direct containerd profiles for k1s controller/runtime development.

High Value Commands

workerbee doctor
workerbee mcp start
workerbee mcp status
workerbee projects
workerbee ingress status
workerbee ingress ca --output workerbee-ca.crt
workerbee trust status

WorkerBee does not install its local CA automatically. Use workerbee trust install --target system or workerbee trust install --target nss only when you explicitly want to trust WorkerBee's Caddy CA on the host.