Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 52,609
    • Issues 52,609
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,544
    • Merge requests 1,544
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #353468
Closed
Open
Issue created Feb 22, 2022 by Viktor Nagy (GitLab)@nagyv-gitlab🕊Developer

Agent list design cleanup

Release notes

Problem to solve

The GitLab agent for Kubernetes related views could handle a holistic approach to assure that they will scale as we add more functionality at the project and group levels.

The current situation is:

  • every agent is registered in a project, let's call it the agent configuration project
  • every agent connection can be shared with other groups and projects to support CI/CD workflows
  • WIP every agent will be able to grab and deploy Kubernetes manifests from other projects to support GitOps workflows

In terms of views

  • we have a project level view for the agent configuration project

We miss view

  • to see agents available for CI/CD workflows within a project
  • to see agents available for GitOps workflows within a project outside the agent configuration project
  • to see agents available for CI/CD workflows within a group - designs are ready
  • to see agents available for GitOps workflows within a group

The available data is different for an agent configuration project and when only the connection is available.

Mural board to "explain" the chaos

Proposal

Design the missing UI and UX to see agents available fo:

  • CI/CD workflows within a project
  • GitOps workflows within a project outside the agent configuration project
  • GitOps workflows within a group

Notes

The designs for agents available for CI/CD workflows within a group - are ready

Intended users

  • primarily: Infrastructure and Platform Engineers
  • secondarily: Software Engineers (for shared CI/CD agents connections)

Figma link

Wireframes

Feature Usage Metrics

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.

Edited Jul 12, 2022 by Ali Ndlovu
Assignee
Assign to
Time tracking