For Github ephemeral runners, we will need our own custom images since the images provided by Github are packer templates for azure explicitly.
Since we are using AWS services, we will need custom AMIs tailored to AWS built with packer. The pre-built AMIs will be uploaded with packer and used by the runners.
There was the option of just creating an AMI from snapshot of our dedicated runners. That would require spinning an instance up every 2 weeks with the AMI, update the packages and then snapshot a new AMI again to be used by the runners.
The best option is to just create packer images using HCL templates, and have CI build and upload the new AMI bi-weekly. Then just update one line in the runner terraform to use the new AMI image id.
### Tasks
- [x] create HCL packer template and AMI for Ubuntu
- [x] create HCL packer template and AMI for Windows 2022
DaMandal0rian
commented
3 months ago
For Github ephemeral runners, we will need our own custom images since the images provided by Github are packer templates for azure explicitly.
Since we are using AWS services, we will need custom AMIs tailored to AWS built with packer. The pre-built AMIs will be uploaded with packer and used by the runners.
There was the option of just creating an AMI from snapshot of our dedicated runners. That would require spinning an instance up every 2 weeks with the AMI, update the packages and then snapshot a new AMI again to be used by the runners.
The best option is to just create packer images using HCL templates, and have CI build and upload the new AMI bi-weekly. Then just update one line in the runner terraform to use the new AMI image id.