kpack icon indicating copy to clipboard operation
kpack copied to clipboard

Add RFC: kp dashboard

Open aemengo opened this issue 4 years ago • 7 comments

Readable

aemengo avatar Nov 13 '20 19:11 aemengo

Have you considered creating an Octant plugin? We recently created a plugin for Knative.

scothis avatar Nov 13 '20 21:11 scothis

Have you considered creating an Octant plugin? We recently created a plugin for Knative.

+1, I actually drafted this comment when I saw this! Octant plugins are pretty easy to build (even I can do it!) and written in Go which might help the community contribute to it.

Possible disadvantages might be tying to Octant's roadmap/feature set, but I don't know how much of a deal breaker that is.

imjasonh avatar Nov 13 '20 21:11 imjasonh

We have investigated an Octant plugin as well. So, this would likely be in addition to an octant plugin.

matthewmcnew avatar Nov 16 '20 19:11 matthewmcnew

I'm a huge fan of the "Details" panel. @aemengo I may have expressed this point to you when we initially spoke about this RFC. The Details panel is currently organized based on whether the object is namespace or cluster scoped. I think that if it were instead organized based on the logical mapping of utilized resources (i.e. image -> builder -> clusterstore (buildpacks)/clusterstack) it would more effectively address the problem of following the chain of each individual resource by inspecting objects you call out in the Problems section.

mgibson1121 avatar Nov 20 '20 23:11 mgibson1121

@ImJasonH and @scothis you make a good point that this proposal takes the CLI a step closer to a web app GUI, but I think its actually accomplishing something quite different.

A full web app would allow the user to accomplish tasks, the same ones the CLI enables, just in a more visual way. As proposed, I believe this RFC is a new piece of functionality, a "map" display for the user to pull up and see where they want to go next. It doesn't enable the full debugging workflow. It's just one single step in that workflow, a wayfinding step, that would allow you to then identify the kpack resource that you want to troubleshoot. One of the weaknesses of the kp cli today is that it doesn't show connections between resources very well, even though the heirarchy / "flow" of resources (stack+store => builder => image => build) is one of the foundational concepts of kpack.

For these reasons, I would be in favor of this RFC being a part of the kp CLI.

sampeinado avatar Nov 24 '20 16:11 sampeinado

Last month we got some feedback from a kpack user asking if there is any way to see the association between a ClusterBuilder and an image using the 'kp' CLI. This one more piece of evidence that suggests this kind of high level "map" view would be helpful as part of the CLI experience!

sampeinado avatar Jan 04 '21 16:01 sampeinado

@aemengo / @sampeinado ⛏️ digging this one back up. It sounds like the idea of a "map" has been brought up a few times. What do you all envision it looking like? Given this is a GUI, got any mock ups?

jromero avatar Sep 21 '21 18:09 jromero