Many AWS customers are using https://gitlab.com/ for their DevOps needs, including source control, and continuous integration and continuous delivery (CI/CD). For the SaaS edition, GitLab offers hosted runners, and customers can provide their own runners as well.

In this post, we’ll discuss how customers can maximize their CI/CD capabilities by managing their GitLab runner and executor fleet with https://aws.amazon.com/eks/.

We’ll tag the x86 runner with x86, x86-64, and amd64, thereby reflecting the most common nicknames for the architecture, and we’ll tag the arm64 runner with arm64.

private runnerConfig(): string { return ` [[runners]] [runners.kubernetes] namespace = "{{.Release.Namespace}}" image = "ubuntu:16.04"[runners.kubernetes.node_selector]"kubernetes.io/arch" = "${this.arch}""kubernetes.io/os" = "linux""karpenter.sh/capacity-type" = "spot"[runners.kubernetes.pod_labels] gitlab-role = "runner" `.trim(); }}

Related Articles