How autoscaling GitLab CI works on AWS Fargate

Autoscaling GitLab Runner offers a scalable and cost-efficient solution for executing CI/CD jobs on cloud-hosted virtual machines, and with the release of GitLab 12.10, it now supports AWS Fargate managed containers. This advancement allows users to leverage container orchestration solutions, such as AWS Elastic Kubernetes Service and Google Kubernetes Engine, for executing GitLab CI/CD jobs. The GitLab Runner Custom executor enables the creation of drivers for non-natively supported platforms, and the newly developed GitLab AWS Fargate driver uses the AWS Fargate run-task action to schedule tasks, with the pipeline job executing on a container built from a specified image. However, AWS Fargate's inability to support privileged mode poses challenges for Docker-in-Docker operations, though GitLab is committed to iterating on solutions for these limitations. With this update, GitLab provides a diverse array of options for autoscaling CI jobs across major cloud platforms, including cloud-delivered virtual machines and various container orchestration platforms, reinforcing its aim to offer the most comprehensive solution for executing CI jobs at scale.

No tracked trend matches for this post yet.