<!-- This issue template can be used a great starting point for feature requests. The last section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. --> ## Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ## Problem to solve Provide insights into agent activities at the group level. The users at the group level might not have access to the agent configuration project. As a Release Manager, in order to see the various deployments we own, I want to know what project activities happened around Kubernetes. As a Software Engineer, in order to move on with testing my changes, I want to know if my changes got deployed successfully to a cluster. ## Proposal ### List the agents available for the group List the agents available for the group with basic connection status information - are we ok to show a link to the agent config project? ### Details view - Show instructions to use this agent in CI/CD - Show the list of pipelines and project accessing the given Agent via the CI/CD Tunnel #### Future Once manifest projects are not restricted to the agent configuration project: - Show the list of projects within the group that act as a manifest project for the given agent, and their latest commit and sync status ## Intended users Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) ## User experience goal The user should get insights into what is being deployed from under the given project using a specific agent, and what agents are accessible within the group.