runner-registration-token is needed even if runner-token is being used
Our organization is currently trying to improve the automation of the GitLab runner provisioning. We are using helm charts to perform this step. We are migrating from old runner registration token to runner token. The helm chart states that the secret
parameter should point to a Kubernetes secret where runner-registration-token
and runner-token
contains.
After creating a secret with runner-token
only, the registration of runner failed. I also tried adding runner-registration-token
as blank field. However the registration fails. The registration only succeeds when we input the glrt-*
token on both runner-token
and runner-registration-token
on a secret, before referencing the helm chart to the secret file. Why would still we need runner-registration-token
with glrt-*
token if it is being deprecated?
Upon further checking the secrets generated from manual creation vs from helm chart, the secrets are the same.
Has anyone experienced the same issue?