Support setting secrets via environment variables
What does this MR do?
Allows setting token secrets via environment variables.
I removed the optional block from the secret, as how the deployment template is written it must exist. Since the files will always show up in /secrets
, I changed the check for file to check for env var before using file.
Why was this MR needed?
Not all k8s encryption tooling supports secrets from a volume.
What's the best way to test this MR?
Leave runnerRegistrationToken
and runnerToken
unset, the pod should still start.
Setting CI_SERVER_TOKEN
and/or REGISTRATION_TOKEN
with envVars
should allow the runner to operate.
What are the relevant issue numbers?
Edited by Joshua Perry