Match EphemeralRunner status with Runner status in the UI

[Moser-ss]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

ARC (Actions Runner Controller)

Discussion Details

Problem
When we get information about an EphemeralRunner, we get something like this.

NAME                               GITHUB CONFIG URL              RUNNERID   STATUS    JOBREPOSITORY   JOBWORKFLOWREF   WORKFLOWRUNID   JOBDISPLAYNAME   MESSAGE   AGE
arc-runner-xkx27-runner-ltrdm   https://github.com/example   9255755    Running                                                                               95m

Or this if we get the yaml object

status:
  phase: Running
  ready: true
  runnerId: 9255755
  runnerJITConfig: foobar
  runnerName: arc-runner-xkx27-runner-ltrdm

We don't have a way to identify if the Runner is already in use or not, unless we try to check if one of the following properties exists in the EphemeralRunner

• jobDisplayName
• jobRepositoryName:
• jobWorkflowRef:
• workflowRunId

Suggestion
It would be great if we had the property busy, as we do from the API, to inform us if the EphemeralRunner is busy. We could check inside the cluster which runners are processing or not.
Also, it would be great if the information were available as an annotation in the pod.

Why is this feature relevant?
This kind of information would help manage the cluster, such as consolidating nodes and kicking out runners from underutilized nodes. But to do that safely, we can only do so if the Runner is not in use.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐