Unknown labels with GitHub Actions Runner AutoScale Set

[kratsg]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

ARC (Actions Runner Controller)

Discussion Details

When following all the instructions for setting up the GHARC AutoScaleSet, I have the following UI view

1. Everything is running on linux hardware, so I would have expected a linux label to automatically be added. Why is this not the case?
2. Why are there two different runner groups? It's likely due to the listener vs the scaleset but this isn't super clear?
3. How can one add additional labels or create groups of homogeneous runners based on the heterogeneous hardware we have? That is, we might have a group of AMD cores and a group of Intel cores

For the above image screenshot on the GitHub UI in the Actions->Runner tab/subsection, this is what the k8s view looks like using K8SLens:

I would appreciate if the documentation could be improved and someone can explain if this is expected or not.

[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. ⭐