Replies: 2 comments 2 replies
-
My simple solution is:
Quite simple but not zero downtime as the Runners might be restarted due to changes. For zero downtime you have to deploy the module twice during release time as you described above. One thing I am missing is, "setting the Runners to pause" in your description above. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Just found out, that |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey community! I was wondering how y'all are managing zero downtime when updating your GitLab Runner using Terraform? Do you have a nifty way to do zero downtime or do you just have scheduled maintenance windows? I'm curious what y'all managed to do regarding this subject. I myself have at one time done the following in a Terraform pipeline using Hetzner cloud:
This worked pretty well, but doesn't feel like the best solution, so I'm curious what y'all have come up with.
Beta Was this translation helpful? Give feedback.
All reactions