### Release notes ### Problem to solve During the discussion for https://gitlab.com/gitlab-org/gitlab/-/issues/432573+, there was a realization that there had not been enough exploration on different navigation options into the Kubernetes Dashboard. One of the un-explored ideas was a tree view that worked as an entry-point into the dashboard. We ran https://gitlab.com/gitlab-org/ux-research/-/issues/2829+ which deemed the tree view successful and something users want in their workflow. This issue is intended to capture work being done to refine the design based on the solution validation outcome. ### Intended users * Sasha - [Software Developer](https://gitlab.com/gitlab-org/gitlab/-/issues/432573 "Kubernetes menu") * Priyanka - [Platform Engineer](https://handbook.gitlab.com/handbook/product/personas/#priyanka-platform-engineer) * Allison - [Application OPs](https://gitlab.com/gitlab-org/gitlab/-/issues/432573 "Kubernetes menu") ### User experience goal Provide users with a tree visualization that better helps them understand their deployment, as well as navigate into the Kubernetes Dashboard. ### Proposal **Successful iteration from testing:**  **Improvements include:** * Users wanted to interact with the single stat details for the pods, it seemed confusing to them that those weren't clickable and they couldn't drill down more. * The tree view itself probably will not be feasible on the environment index page, therefore we'll need to create a design to house it on the environment details page. * Having Pod and Log beside so closely beside each other in the UI confused some people, some thought the pod single stats were related to logs and vice versa. * With so much extra data on the page now, some users didn't quite clue in that the top information was the deployment. * The drop-down in the tree might be seen as a collapse/expand icon, as that's what their main action has been on the page so far. * Some iconography was a bit unclear (what does an orange warning mean in the pod box etc). * remove(?) the pod numbers from the top * the design should support 100+ pods / deployment * the design should support 1-50 deployments, services, etc ... * move the "logs" button closer to individual pods (e.g. to the pod details view or pod list view) * clarify the meaning of the `>` icons * given the scale requirements, it might make sense that `>` opens the given branch, so we don't have to load the whole tree at once * in the 1st iteration `>` showed more info about the specific node * provide more info about the visualised resources (show the status at least) ### First iteration For the first iteration, we are starting with the Kustomization resource as it provides an Inventory object with all related resources. The tree view will initially contain a Kustomization and a list of related deployments. The user can click on each deployment to build a branch with related replicaSets and pods. The resources should be watched for changes. Metrics we want to measure: * number of deployments shown * click on a deployment ### Documentation ### Availability & Testing ### Available Tier ### Feature Usage Metrics ### What does success look like, and how can we measure that? ### Is this a cross-stage feature? Work was done in collaboration with \~"group::foundations" (cc: @aregnery) ### What is the competitive advantage or differentiation for this feature? ### Links / references _This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc._ <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->