Repository navigation
Conversation
|
Nice, are you aware of the Maybe event better, your usage of a more modern tooling would enhance the visible experience of the existing dashboard, if the dashboard would be refactored to use your libraries. |
Oh, no I'm not. But now that I looked at it: it doesn't provide the kind of views I intend with the watch ui.
This is a sound idea, so what's the plan? Ditch this PR and re-implement the dashboard based on this work? Or keep both views in the code until someone managed to re-implement the dashboard? |
What about telling your KI to refactor the dashboard with the tooling in your |
|
Some linter errors must be fixed though |
|
Great effort! I am also not sure if we should really add a dedicated command along with We can have a session on consolidating the ideas such that we can turn this into a more comprehensive user experience (probably more K9s like with the current dashboards as alternative list views). |
I made a PR to integrate it into the dashboard #399 |




Description
This PR adds a new subcommand,
cluster watch. It's a TUI using the bubbletea and lipgloss modules. The TUI doesn't do much yet, it only allows the operator to view current state of a cluster as well as errors, logs and node status. The TUI is (yet) completely read-only, so no administrative operations are implemented.Please note, that I had to turn
output.humanizeDuration()intooutput.HumanizeDuration(), otherwise I couldn't use it incmd/cluster_watch.go.Screenshots:
Peace view
Update view
Used AI-Tools ✨
None used.
Noteworthy
-->