Skip to content

Set up your own GitLab Runner within seconds using cloud-init on Hetzner, Exoscale, Azure or any other public cloud provider.

Notifications You must be signed in to change notification settings

lclc/gitlab-runner-cloud-init

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 

Repository files navigation

GitLab Runner cloud-init

Set up your own GitLab Runner within seconds using cloud-init.

Make sure you adjust the following points in the cloud-ini file:

  • Set your own SSH Keys at ssh_authorized_keys
  • Set your GitLab registration-token
  • Set the instances name in description
  • Adjust the tag-list (optional)
  • Allow port 9252 to be accessible from your Prometheus instance for monitoring (optional)

It will also configure Unattended-Upgrades to automatically install security upgrades and the latest versions of GitLab Runner (they update every month).

This has been tested with Ubuntu LTS 20.04 and 22.04 on Hetzner Cloud, Exoscale, and Microsoft Azure.

Note: GitLab-Runner version 16.0 will remove the current registration-token approach and replace it with something new (which hasn't been implemented yet). For more information see the Next GitLab Runner Token Architecture-epic. This repositories cloud-init file will have to be updated.

About

Set up your own GitLab Runner within seconds using cloud-init on Hetzner, Exoscale, Azure or any other public cloud provider.

Resources

Stars

Watchers

Forks