The resource table was truly an incredibly powerful addition to the platform. However, it was not perfect from day one. My objective here was to take what was a complex YAML file, distill what was important, and provide users a clean experience to view their resource details. Initially, we (meaning I) made the mistake of trying to pull out the information I deemed important and provide the users with a very clean, and spacious, UI to view those details. We quickly realized this is not what the user wanted. They might be relying on other key details that we weren't pulling, additionally they had a lot more resources than we anticipated, so we needed a change.
This was the genesis of the resource table. I know, you might be thinking "Big deal, it's just a table", and normally I'd agree with you, however we were able to ingest an incredible amount of data and present it in a grokkable way. The resource table normalized the data and allowed users to add new columns to view what was important to them, enabling them to search for their specific resources, granular filtering, and sorting.
Due to the fact that the table was designed in such an extendable and customizable way, we were able to use it throughout the Containership Cloud platform in a variety of ways including RBAC, clusters, nodes, and of course for Kubernetes resources. Each one required some customizing, but because the base component was robust the updates were minor and greatly improved the experience for each flow. For example, the cluster status bar changes whenever there is an issue with a node on the cluster, users get a readable description based on the roles they've created, and resources have editable labels they can interact with.