<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=423523) </details> <!--IssueSummary end--> With the move to the new runner creation workflow, the runner description is only stored for the configuration in the server (`ci_runners` table), which is created either in the UI or through the `POST /user/runners` REST API. In the previous workflow, the Helm chart passed a description consisting of the pod name, which then allowed users to see the pod name in e.g. the runner details page: | registration token | runner creation in UI | | ------ | ------ | | {width="800px"} | {width="800px"} | To provide the same experience, we'd need to: - Create a `description` column in the `ci_runner_machines` table, similar to the one in `ci_runners`. - Pass the description used in `gitlab-runner register` back to the server to be incorporated in the `ci_runner_machines` table. Currently, the challenge is that the `ci_runner_machines` record is created in response to a `POST /runners/verify` API call, and it doesn't make sense to add a description in that API. The other API that triggers a creation of the `ci_runner_machines` record is the `POST /jobs/request` endpoint. - Display the `ci_runner_machines` description in the runner manager rows, and possibly in other pages which are displaying the runner description. Created from [user report](https://gitlab.com/gitlab-org/gitlab/-/issues/423020#note_1532207258). <!-- template sourced from https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Default.md -->