Skip to content

Multiple runners

This merge request enable registering multiple runners with a single helm chart. I am publishing just as a workaround or start-point to support this feature.

This PR it's not compatible with any other chart version.

Changes:

  • The following features are being configured using command line when registering the runner instead of using ENV variables. They are now runners specifics and should be specified using runners[]. instead of runners
    1. secretName is now cacheSecretName and values should following the name convention: s3access-[runner-name], google-application-credentials-[runner-name], gcsaccess-[runner-name] or azureaccess-[runner-name]
    2. runnerRegistrationToken
    3. name
    4. tags
    5. locked
    6. executor
    7. protected
    8. service
    9. runUntagged
  • Removed the following deprecated properties:
    1. runners.image
    2. runners.imagePullPolicy
    3. runners.imagePullSecrets
    4. runners.namespace
    5. runners.requestConcurrency
    6. runners.nodeSelector,
    7. runners.nodeTolerations,
    8. runners.podLabels,
    9. runners.podAnnotations
    10. runners.privileged
    11. runners.pollTimeout
    12. runners.outputLimit
    13. runners.builds
    14. runners.services
    15. runners.helpers
    16. runners.pod_security_context
    17. runners.env
  • runners.secrets it's not supported anymore, use the runners.configs[].config.registrationToken to specify the registration tokens, and runnerToken is not supported at all (didn't code because I didn't need it)
Edited by Guilherme Torres Castro

Merge request reports