## Goal The agent requires much monitoring, like - having an overview of the synced status of manifest repositories, - seeing a connection status of the agents - seeing basic insight into the running agents, like number of pods - seeing agent activities - etc... ## Approach We want to provide a reverse tunnel from CI into the cluster. While we reach that goal, we want to move in small steps, and provide value along the way. One milestone in this direction is to [provide the ability for GitLab to reach out to an installed `agentk`](https://gitlab.com/groups/gitlab-org/-/epics/4591). A first value we can get out of GitLab reaching out to `agentk` is to provide basic insights into `agentk`s activities, status. ## Proposal The initial designs are in the following issues: - [listing view](https://gitlab.com/gitlab-org/gitlab/-/issues/323058/) - [details view](https://gitlab.com/gitlab-org/gitlab/-/issues/298752) ### What might provide the most value? 1. [Synced status of manifest projects](https://gitlab.com/gitlab-org/gitlab/-/issues/258603) 1. [Basic connectivity information](https://gitlab.com/gitlab-org/gitlab/-/issues/230571#iteration-1) 1. [An activity stream](https://gitlab.com/gitlab-org/gitlab/-/issues/277323) 1. What pages do we think need to be created for the management interfaces, 1. The usage of each page if more than one, i.e. what does someone who comes to these pages expect to see? 1. What edge cases and errors we migh have to consider. 1. other ideas? ### What is a reasonable MVC? 1. provide a list of tokens and basic information about the agent, kas and the cluster 1. provide status feedback about the connection and tokens used ## See also This epic is about management interfaces around the agent, not around the applications deployed/managed by the Agent! For information on the applications deployed, please check [the Kubernetes Dashboard epic](https://gitlab.com/groups/gitlab-org/-/epics/2493)