Runner lock & untagged jobs setting can not be saved as IaC
Summary
Runner lock (for project specific runners) & untagged jobs setting can not be saved by IAC and gets lost if runner pod crashes. Allowing these settings to be saved by IaC can mitigate the crash issue I mentioned in #82 by atleast allowing the settings to stay the same after a re-registration is triggered by a crash/restart of the pod.
Steps to reproduce
- Register a project specific runner in Openshift.
- Restart the gitlab-runner-runner-xxxx-xxxx pod in your Openshift project
- Visit the Settings > CI/CD > Runners page of the projects and observe a new registration present.
- Click edit on the runner and see that run untagged jobs and runner lock has been reset.
Actual behavior
Openshift gitlab-runner-runner-xxxx-xxxx pod restart triggers a runner re-registration. Project lock & run untagged jobs is not preserved and the runner needs to be re-enabled for additional projects and re-locked.
Expected behavior
Suggested mitigation
Runner lock & untagged jobs setting can be saved as IaC to atleast preserve these settings if a re-registration is triggered.
Prefered behavior
Openshift gitlab-runner-runner-xxxx-xxxx pod uses the already established registration after a restart. Project lock is to be preserved and the runner should stay enabled for projects where it was previously enabled.