Skip to content

Change runner token deprecation/removal schedule to 17.0 and 18.0

Vladimir Shushlin requested to merge vshushlin/runner-token-deprecation-180 into master

What does this MR do and why?

A lot of users in Feedback issue: New Runner registration flow (#387993 - closed) are worried about upcoming changes to runner registration.

We still don't have everything in place to help users to migrate, especially when it comes to git-ops setups:

  1. we only recently released support for the terraform provider
  2. we still don't have support for creating runners via Helm chart (as users are used to)

This MR makes 2 things:

  1. change the schedule to deprecate with a fallback in 17.0, and remove in 18.0
  2. clarifies that old runners will still work even after that

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports