Adding option to create listener pods in same namespace as AutoscalingRunnerSet

[ordovicia]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

ARC (Actions Runner Controller)

Discussion Details

ARC creates listener pods in the controller's namespace.
For example, if the controller is deployed in arc namespace and a user creates an AutoscalingRunnerSet in target namespace,
child resources like EphemeralRunnerSet will be created in target, while the listener pods will be created in arc namespace.
To allow the listener pods to interact with EphemeralRunnerSet and other resources in target, a RoleBinding is created in target with the listener's ServiceAccount as the subject.
This occurs the following issues:

• The RoleBinding crosses namespace boundaries.

Depending on a cluster's security requirements, creating RoleBindings that span namespaces may be restricted. In this case, ARC cannot be used because the RoleBinding cannot be created.

• Listener pods' specification must be configured for cluster management addons.

The namespace where the listener pods are created is the namespace where cluster management addons (ARC is one) are deployed. Depending on the cluster configuration, special settings may be required for these pods, such as node selectors or tolerations. While we can configure these by specifying listenerTemplate, requiring cluster management addon configurations to be defined in user-created resources like AutoscalingRunnerSet feels unnatural.

To address these issues, would it be feasible to add an option to create listener pods in the same namespace as AutoscalingRunnerSets?
This would keep the RoleBinding within target namespace and eliminate the need for listener pod configuration.

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

[MohammedSardarSaajit4488]

Thanks for acknowledging this. Just wanted to highlight that having listener pods in the same namespace as AutoscalingRunnerSets would simplify permissions and configs a lot for us. Looking forward to any updates on this.