-
Notifications
You must be signed in to change notification settings - Fork 240
Updating the Toil Gitlab Runner
Adam Novak edited this page Apr 18, 2024
·
7 revisions
To update the runner, you probably should now just destroy the old instance and make a new instance, following the instructions at Gitlab CI Autoscaling Setup.
To update Toil's Gitlab runner, you'll first need a kube config to access the cluster (email Erich Weiler).
Next, run this to get the current runner config:
helm -n toil get values gitlab-toil-kubernetes-runner
This will print something like the following (relevant part shown):
checkInterval: 30
concurrent: 20
gitlabUrl: https://ucsc-ci.com/
imagePullPolicy: Always
rbac:
create: false
serviceAccountName: toil-svc
runnerRegistrationToken: averyverysecrettoken
runners:
config: |
[[runners]]
name = "Kubernetes Runner"
output_limit = 40960
[runners.kubernetes]
namespace = "toil"
image = " "
poll_timeout = 86400
privileged = true
service_account = "toil-svc"
cpu_limit = "4000m"
cpu_request = "4000m"
memory_limit = "15Gi"
memory_request = "15Gi"
ephemeral_storage_limit = "20Gi"
ephemeral_storage_request = "20Gi"
service_cpu_limit = "4000m"
service_cpu_request = "4000m"
service_memory_limit = "8Gi"
service_memory_request = "8Gi"
service_ephemeral_storage_limit = "20Gi"
service_ephemeral_storage_request = "20Gi"
helper_cpu_limit = "500m"
helper_cpu_request = "500m"
helper_memory_limit = "256M"
helper_memory_request = "256M"
helper_ephemeral_storage_limit = "20Gi"
helper_ephemeral_storage_request = "20Gi"
Write this into a file called “values.yml”.
Update so that helm knows what the latest version is:
helm repo update
Finally, update the runner:
helm upgrade --namespace toil gitlab-toil-kubernetes-runner -f values.yml gitlab/gitlab-runner
That's it, though you can sanity check here to see the new runner (and what should be the updated version):