Documentation
The guide first, then the design notes the product was built from. Every page is generated from markdown in the repository, so none of it can drift from what is committed.
Guide
Install it, run it, and use the four screens.
Install and run
One binary, no runtime, no setup step.
First run
What happens when it reads your kubeconfig, and how environments are inferred.
The app list
How objects become apps, and how health is derived.
Logs
Every replica merged into one stream, with its availability edges marked.
The timeline
History reconstructed from the cluster, and where its knowledge ends.
Resolved configuration
What the container actually received, and what changed since the last revision.
Promotion and drift
Is the fix in prod yet, and how do two environments differ.
Port-forward, exec, guardrails
The three things that write, and the two gates in front of them.
Keyboard
The command palette, and everything reachable from it.
The config file
Optional, strict, and never written by kubeside.
Permissions
What it reads, what it asks the cluster, and why nothing is hidden.
When things are missing
Unreachable clusters, expired sessions, refused reads, absent metrics.
Design notes
The research and the decisions the product was built from.
The problem
Landscape research, complaint clusters, the four uncovered gaps.
Personas
Five users, one stakeholder, three anti-personas.
Product spec
Principles, the four screens, non-goals, anti-requirements.
Multi-cluster
Environments, promotion, cross-environment diff, prod guardrails.
Architecture
Stack, data flow, storage, auth, performance budget.
Roadmap
Milestones and what shipped in each.