Bring Your Own Infrastructure to GitHub Codespaces

[yonggamer]

🏷️ Discussion Type

Product Feedback

Body

I would like to suggest introducing support for self-hosted infrastructure in GitHub Codespaces, allowing developers and organizations to run their development environments on their own hardware instead of relying exclusively on GitHub-hosted compute.

GitHub Actions already supports self-hosted runners, and I think a similar concept would be a great addition to Codespaces.

Proposed Feature

Allow users to connect their own infrastructure to GitHub Codespaces, such as:

Dedicated Linux servers or virtual machines.

Self-hosted homelab infrastructure.

Kubernetes clusters.

Private cloud or on-premises infrastructure.

A lightweight agent, similar to the GitHub Actions self-hosted runner, could register with a GitHub organization and manage the provisioning of Codespaces environments.

Why is this useful?

Cost savings: Use existing hardware instead of paying for GitHub-hosted compute.

Hardware flexibility: Choose custom CPU, RAM, GPU, and storage configurations.

Privacy and security: Keep development environments within privately managed infrastructure.

Private networking: Access internal databases, services, and resources directly.

Enterprise support: Meet specific security, compliance, and data residency requirements.

Homelab support: Allow individual developers and self-hosting enthusiasts to use their own servers.

Expected Developer Experience

Ideally, everything would continue working exactly as it does with regular GitHub Codespaces:

Browser-based VS Code.

VS Code desktop integration.

Existing devcontainer.json configurations.

Port forwarding.

Extensions and development tooling.

Codespaces lifecycle management.

The only difference would be where the actual development environment runs.

It would also be great to support a hybrid approach, allowing developers to choose between GitHub-hosted and self-hosted compute when creating a Codespace.

Final Thoughts

I believe this would make GitHub Codespaces considerably more flexible and accessible.

The infrastructure model used by GitHub Actions self-hosted runners seems like a good starting point for implementing this functionality.

My main request is to bring a Bring Your Own Infrastructure (BYOI) option to GitHub Codespaces, giving developers control over where their development environments run while retaining the existing Codespaces experience.

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