Multi-pane workspace
Keep resources, commands, traffic, and events visible together instead of constantly switching tools.
KubeMan brings resource views, a persistent shell, traffic flow, events, saved layouts, and workspace administration into a single multi-pane console designed for day-to-day cluster work.
$ kubectl get pods
api-748d Running
worker-2a1 Running
jobs-41c Pending
Traffic flow
Events
Normal · Pulled image
Warning · Back-off restart
Normal · Scaled deployment
Console foundation
Keep resources, commands, traffic, and events visible together instead of constantly switching tools.
The Docker bundle includes a companion shell with kubectl, Helm, AWS CLI, Git, jq/yq, editors, and networking tools.
Treat traffic and cluster resources as connected operational signals rather than isolated rows.
First launch uses a one-time startup code, Google identity, and a designated initial administrator.
Kube and AWS configuration mount read-only. The Docker socket and macOS filesystem are not exposed.
Preserve useful workspace arrangements for repeated investigations and administration tasks.
Container boundary
The web console, bootstrap service, persistent volumes, and companion shell are packaged for Docker Desktop. Shell history and the non-root home directory persist while sensitive system state stays in dedicated volumes.
$ docker compose up --build -d
open http://localhost:3080
Project status
The repository establishes the working web-console foundation and Docker workflow. Its documentation explicitly identifies isolated cluster-agent and secret-broker services as the next boundary for broader real-cluster execution and credential storage.
The roadmap extends the same security model into monitoring, alert lifecycle, AWS infrastructure signals, Slack notifications, and permission-aware queries.