GitHub, the world’s leading Artificial Intelligence (AI)-powered developer platform, has introduced several new updates for GitHub Actions to further support enterprise customers, bringing stronger security and even more power to GitHub-hosted runners.
The updates include Azure private networking for GitHub-hosted runners, GPU-hosted runners for Machine Learning, and additional runner SKUs.
Azure Private Networking for GitHub-Hosted Runners Generally Available Now
Azure private networking for GitHub-hosted runners is now generally available. This feature allows developers to run Actions workflows on GitHub-hosted runners that are connected to their Azure virtual network, without compromising on security or performance.
GitHub-hosted runners provide powerful compute in the cloud for running CI/CD and automation workflows that are fully managed, eliminating the overhead of managing and maintaining infrastructure. However, enterprises having strict networking and security requirements prevent them from using GitHub-hosted runners to their full potential, specifically:
- Secure access to private resources within their on-prem or cloud-based locations, such as databases, artifactory, storage accounts, or APIs.
- Enforce network security policies and outbound access rules on the runners to reduce data exfiltration risks.
- Isolate their build traffic from the public internet and route it through their existing private network connections (ex. VPN or ExpressRoute).
- Monitor network traffic for any malicious or unusual behavior as workflows run.
With Azure private networking, organisations can easily create GitHub-hosted runners that are provisioned within their Azure virtual network and subnet of choice. Thereafter, Actions workflows can securely access Azure services like storage accounts, databases, and on-premises data sources such as an Artifactory through existing, pre-configured connections like VPN gateways and ExpressRoutes.
Focusing on Security
Additionally, security is front and center with this update. Any existing or new networking policies, such as Network Security Group (NSG) or firewall rules, will automatically apply to GitHub-hosted runners giving platform administrators comprehensive control over network security, all managed within a single place.
“At Deutsche Vermögensberatung (DVAG), we always focus on delivering great products to our customers. By executing our CI/CD workflows on GitHub-hosted runners, the burden of managing our own infrastructure has been lifted. This shift has provided our developers and DevOps administrators with precious time to dedicate to innovation, thus ultimately accelerating our products’ time to market,” explained Florian Koch, Lead Developer IT Platform at Deutsche Vermögensberatung.
Koch added: “One of the standout features of GitHub Actions is the ability to securely and privately integrate with Azure networking, which empowers us to establish secure and private connections from GitHub-hosted runners to our internal resources. With minimal administrative overhead we can effectively manage many resources including Kubernetes clusters, databases, and Virtual Machines,”
Introducing Additional Runners SKUs
GitHub has also introduced the latest additions to the GitHub-hosted runner fleet, 2 vCPU Linux and 4 vCPU Windows runners, supporting auto-scaling and private networking features.
Previously, GitHub’s supported SKUs ranged from 4 vCPU (Linux only) to 64 vCPU, prompting substantial feedback requesting smaller SKUs with the same auto-scaling and private networking capabilities. These newly introduced smaller machines are geared to specifically support scenarios where smaller machine sizes suffice yet the demand for heightened security and performance persists.
Additionally, Apple silicon (M1) hosted runners, specifically macOS L (12-core Intel) and macOS XL (M1 w/GPU hardware acceleration) which were previously in public beta, are now generally available.
GPU-Hosted Runners Available in Public Beta
Moreover, GitHub has announced GPU-hosted runners in public beta. This new runner empowers teams working with machine learning models such as large language models (LLMs) or those requiring GPU graphic cards for game development to run these more efficiently as part of their automation or CI/CD process, empowering teams to do complete application testing, including the ML components, with GitHub Actions.
The GPU SKU comes equipped with auto-scaling and private networking features. GitHub is initially rolling out support for a 4-core SKU with 1 T4 GPU, and has more SKUs planned for later this year.
What’s Next?
GitHub is dedicated to continuous improvement, driven by user feedback, to ensure that the platform delivers an unparalleled user experience. Here’s a glimpse into some exciting enhancements on the horizon for GitHub-hosted Actions runners.
Reliability continues to be top priority as GitHub introduces new functionalities. GitHub is actively engaged in significant efforts to enhance the overall scalability and reliability of the GitHub Actions platform, underlined by the profound impact any service disruption has on a user.
Tanmayee Kamath, Senior Product Manager at GitHub, said: “We’re focused on elevating the Azure private networking feature set, enabling the creation of network configurations encompassing multiple virtual networks. Additionally, we’re streamlining setup processes through scripting and implementing best practices for VNET peering to accommodate unsupported Azure regions.”
Kamath further stated: “For customers not utilising Azure, we’re developing private networking solutions tailored to address similar challenges surrounding private resource accessibility, outbound control, and network monitoring. These solutions will seamlessly integrate with other leading cloud providers such as AWS and GCP.”
Soon, users will have the ability to craft custom VM images natively in Actions, bundling all necessary software and tools to expedite build and test procedures for even the most intricate or expansive projects.
Furthermore, GitHub is committed to enhancing runner SKUs to meet the evolving demands of the user base. This includes the introduction of additional GPU SKUs, ARM SKUs, and any other variants driven by customer demand.
Azure private networking for GitHub-hosted runners is generally available across Team and Enterprise Cloud plans, the newly added 2 vCPU Linux and 4 vCPU Windows SKUs are generally available across Team and Enterprise plans, and GPU runner is available in public beta across Team and Enterprise plans.
Head to GitHub’s blog post here to learn more about these updates.
Archive
- October 2024(44)
- September 2024(94)
- August 2024(100)
- July 2024(99)
- June 2024(126)
- May 2024(155)
- April 2024(123)
- March 2024(112)
- February 2024(109)
- January 2024(95)
- December 2023(56)
- November 2023(86)
- October 2023(97)
- September 2023(89)
- August 2023(101)
- July 2023(104)
- June 2023(113)
- May 2023(103)
- April 2023(93)
- March 2023(129)
- February 2023(77)
- January 2023(91)
- December 2022(90)
- November 2022(125)
- October 2022(117)
- September 2022(137)
- August 2022(119)
- July 2022(99)
- June 2022(128)
- May 2022(112)
- April 2022(108)
- March 2022(121)
- February 2022(93)
- January 2022(110)
- December 2021(92)
- November 2021(107)
- October 2021(101)
- September 2021(81)
- August 2021(74)
- July 2021(78)
- June 2021(92)
- May 2021(67)
- April 2021(79)
- March 2021(79)
- February 2021(58)
- January 2021(55)
- December 2020(56)
- November 2020(59)
- October 2020(78)
- September 2020(72)
- August 2020(64)
- July 2020(71)
- June 2020(74)
- May 2020(50)
- April 2020(71)
- March 2020(71)
- February 2020(58)
- January 2020(62)
- December 2019(57)
- November 2019(64)
- October 2019(25)
- September 2019(24)
- August 2019(14)
- July 2019(23)
- June 2019(54)
- May 2019(82)
- April 2019(76)
- March 2019(71)
- February 2019(67)
- January 2019(75)
- December 2018(44)
- November 2018(47)
- October 2018(74)
- September 2018(54)
- August 2018(61)
- July 2018(72)
- June 2018(62)
- May 2018(62)
- April 2018(73)
- March 2018(76)
- February 2018(8)
- January 2018(7)
- December 2017(6)
- November 2017(8)
- October 2017(3)
- September 2017(4)
- August 2017(4)
- July 2017(2)
- June 2017(5)
- May 2017(6)
- April 2017(11)
- March 2017(8)
- February 2017(16)
- January 2017(10)
- December 2016(12)
- November 2016(20)
- October 2016(7)
- September 2016(102)
- August 2016(168)
- July 2016(141)
- June 2016(149)
- May 2016(117)
- April 2016(59)
- March 2016(85)
- February 2016(153)
- December 2015(150)