Spot instances as GitHub Actions runners
The article discusses the use of EC2 spot instances as self-hosted runners for GitHub Actions. It highlights the cost benefits and flexibility of using spot instances compared to GitHub's managed runners. The author shares insights on setting up a self-hosted runner architecture tailored to specific CI workloads.
- ▪GitHub's managed runners can be expensive for high-volume workloads, costing around $38,000 per month for 80,000 runner-hours.
- ▪Self-hosted runners allow for instance shape flexibility, enabling users to select the necessary EC2 instance type for their builds.
- ▪Using self-hosted runners provides direct access to private resources within a VPC, eliminating the need for proxies or tunnels.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3937478) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Khachatur Ashotyan Posted on May 23 Spot instances as GitHub Actions runners #aws #cicd #githubactions #devops My CI/CD Odyssey (3 Part Series) 1 Jenkins as a Code, or how I stopped clicking around in the UI 2 MacOS Workers, or how I built my own Mac cloud 3 Spot instances as GitHub Actions runners Part 1 was the foundation - Jenkins as a Code, ephemeral workers, the whole thing. Part 2 was the painful platform - macOS.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
