Define MVP functionality for Stackable UI

[nightkr]

No description provided.

[nightkr]

Looking at the current stackablectl, the commands that seem relevant for a read-only view would be service list (list all operator listeners, somewhat mocked up in #2) and maybe operator installed (lists all currently installed Stackable operators).

I think it could also be useful to have some kind of "installed products" view (which might even supersede listeners), but this would take a bit more work to design and integrate well.

[lfrancke]

Of the top of my head I'd like the following features, but we can prioritize these together

• List of all installed Stackable CRDs (including versions)
• List of all installed Stackable operators (including versions)
• List of all CustomResources for a Stackable CRD (i.e. all installed/about to be installed etc. products)
• For an installed product I'd like to see details including endpoint information
• It probably also makes sense to list endpoints per namespace
• For each installed product (where it makes sense) to also have a "connection details"/client information thing (which for HDFS would be a hdfs-site.xml & core-site.xml for example)
• Each installed product should also have a red/green/(maybe yellow) indication on general availability
• Links to log aggregation dashboards and/or grafana dashboards (I don't think we support this yet)

[nightkr]

I think all of these express a sensible desire, but some suffer from a bit of the XY problem that could take refinement.

For example,

• List of all installed Stackable CRDs (including versions)

can arguably serve two purposes here, either as a way to sanity check "am I running the latest version of the CRD?" or as a way to view API docs for your specific running cluster. Those are very different use cases, and don't even have the same notion of what a version is.

[lfrancke]

Yes, all of those can do with some refinement.
Questions like "is it latest version" we'll not be able to reliable answer because all of this needs to work offline as well.

For that specific thing all I want is a list of all installed Stackable CRDs including a list of all CRD versions.
Everything else is stuff we can add later (API docs etc. seem sensible for example)

Absolutely add your own ideas!
We might want to/have to think about mockups for this product.

[soenkeliebau]

What Lars wrote above sounds about right to me. One thing I'd like to at least consider/discuss fairly early on is, if it makes sense to have a split between admin and user functionality right of the bat. No idea how this might look, but it sorta kinda goes towards what @nightkr mentions in her comment as well, different groups of people may have different expectations for the same functions. Might be useful to accomodate that early on to avoid needless larger restructuring later on..

[nightkr]

I think in this case it could be accomodated by adding a column/field for "installed by operator version XX", separate from the list of API versions... But yeah, it's still a larger question worth thinking about.

[nightkr]

Closing this in favour of #12.