Allow GitHub App credentials for ARC to be defined in a different namespace to the AutoscalingRunnerSet

[lacarvalho91]

Select Topic Area

Product Feedback

Body

We're operating a multi tenancy platform where we have ARC autoscaling runner sets applied to dedicated namespaces for each tenant. Tenants need to have secrets access in this namespace. The problem we have is that the githubConfigSecret for a runner MUST live in the same namespace as the runner, this means tenants will be able to access that secret.

What we really want is to be able to create the GitHub App secret in the ARC controller namespace and for it to be used for all runners.

This line means it will always read a secret from the same namespace as the runner itself, maybe we could consider passing one in from controller config and using that instead? and then falling back to current behaviour if a global secret is not configured.

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