2023-03-04 22:38:38 +05:30
- title : "`runnerRegistrationToken` parameter for GitLab Runner Helm Chart" # (required) The name of the feature to be deprecated
2023-01-13 00:05:48 +05:30
announcement_milestone : "15.6" # (required) The milestone when this feature was first announced as deprecated.
2023-03-04 22:38:38 +05:30
removal_milestone : "17.0" # (required) The milestone when this feature is planned to be removed
2023-01-13 00:05:48 +05:30
breaking_change : true # (required) If this deprecation is a breaking change, set this value to true
reporter : pedropombeiro # (required) GitLab username of the person reporting the deprecation
2023-03-04 22:38:38 +05:30
stage : Verify # (required) String value of the stage that the feature was created in. e.g., Growth
issue_url : https://gitlab.com/gitlab-org/gitlab/-/issues/381111 # (required) Link to the deprecation issue in GitLab
2023-01-13 00:05:48 +05:30
body : | # (required) Do not modify this line, instead modify the lines below.
The [`runnerRegistrationToken`](https://docs.gitlab.com/runner/install/kubernetes.html#required-configuration) parameter to use the GitLab Helm Chart to install a runner on Kubernetes is deprecated.
As part of the new [GitLab Runner token architecture](https://docs.gitlab.com/ee/architecture/blueprints/runner_tokens/), in GitLab 15.8 we plan to introduce :
2023-03-04 22:38:38 +05:30
- A new method to bind runners to a GitLab instance leveraging `runnerToken`.
2023-01-13 00:05:48 +05:30
- A unique system ID saved to the `config.toml`, which will ensure traceability between jobs and runners.
2023-04-23 21:23:45 +05:30
2023-03-04 22:38:38 +05:30
From GitLab 17.0 and later, the methods to register runners introduced by the new GitLab Runner token architecture will be the only supported methods.
2023-04-23 21:23:45 +05:30
end_of_support_milestone : "16.6" # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
