`runner-token` should be saved for redeployments if using secrets and `unregisterRunners` is false
Registering a runner providing the runner-registration-token
and the option unregisterRunners: false
implies a registration, with the corresponding runner-token
that, in theory, could be used for a redeployment of the runner.
The problem is that runner-token
isn't being persisted somewhere between deployments. But if K8s secrets are being used (the option runners.secrets
), then it could be persisted.
My expectation is that on first deployment the runner-registration-token
gets saved using K8s secrets until the registration is done and then runner-token
gets also saved using K8s secrets. Further redeployments don't need a registration anymore (remember unregisterRunners: false
) and reuse the saved runner-token
.