Global view for instance-level cluster deployments/environments
Problem to solve
Currently, users of a project-level cluster can see environments created via deployments as well as pod usage (when using deploy boards) of their cluster via the Operations>>Environments page. However, a cluster administrator who configures an instance level cluster cannot see the environments deployed to the cluster nor pods in use by each environment unless they check the "environments" page project by project.
Intended users
Operators
Proposal
- Provide an "Environments" tab on the instance-level cluster page
- Provide a global view of environments created via GitLab deployments to the cluster (only available environments for MVC, stopped environments available as a follow up.
- Provide a view of pod count for each environment (correct use of deploy boards required)
- Provide a link to "environments" portion for each project
The operator is less concerned about "what" is being deployed and more with the usage of the resources in the cluster, for example:
- number of environments created via a GitLab deployment
- pods used for particular environments
- total pods being used in cluster
Solution
For instance-level clusters, add a tab on the individual cluster page that shows deployments to that cluster. That tab will include a table that lists deployments per project. It will show the number of pods used. The total number of pods used in that cluster will be shown next to the column label.
| ------ | Pods match deploy board criteria | Pods do not match criteria |
|---|---|---|
| Has k8s deployment | Show deployment job #id, show pods list 
|
Show deployment job #id, empty pods list (similar to deploy boards) 
|
| Has non k8s deployment | No row | No row |
| Has no deployment | No row | No row |
Empty state copy:
No deployments found
Ensure your environment is part of the deploy stage of your CI pipeline to track deployments to your cluster.
Permissions and Security
The same user-type who can see the "Kubernetes" menu currently should be able to see the "environments" page.
Documentation
Testing
What does success look like, and how can we measure that?
TBD