Building a Kubernetes monitoring dashboard in Rust. Why not?
summary
A Rust terminal Kubernetes dashboard called KDash terminal dashboard that imitates K9s but with a simpler UX gets built and shipped as cargo/binaries and brew/scoop; it uses tui-rs + crossterm + tokio + kube-rs, a channel-driven, multi‑threaded architecture with Arc/Mutex for shared state, and shows lower CPU/memory than k9s or kubectl watch. Log streaming is fragile, cross‑arch clipboard and arm builds cause pain, and VS Code debugging is often painful, but the UI/network thread split fixes freezes.
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 1:45K Dash overview and demo
- 3:27Choosing Rust over Go
- 6:13Value proposition of Rust
- 8:17Rust language strengths
- 11:45Developer perspective
- 13:27Memory and thread safety
- 17:25Concurrency and abstractions
- 19:50Benchmarking and performance
- 24:38Language features and community
- 26:27Overcoming learning hurdles
- 30:20Rust as a general-purpose tool
- 32:38Project architecture and libraries
- 36:12Challenges and lessons learned
related talks
54mRust, Kubernetes, and the Cloud
38mRusty Container Ships: Kubernetes outside the Datacentre
40mVisualizing Kubernetes: The Power of Dashboard
26mDeep Dive: Kubernetes (UI) SIG
36mRust and Skaffold for Iterative Development on Kubernetes
17mRust in Production
34mState of the UI: Leveraging Kubernetes Dashboard
31mThe Rusty Boat