Identify runners that are registered using the legacy token
Release notes
As users migrate from registration tokens to authentication tokens for runners, it's difficult to know which runners in the fleet were created using the old reg tokens. Now, you can identify those runners to migrate them over or delete them altogether.
Problem to solve
As users migrate from registration tokens to authentication tokens for runners, it's difficult to know which runners in the fleet were created using the old reg tokens.
Intended users
User experience goal
The user should be able to identify which runners were created with reg tokens.
Proposal
- Add and expose
registration_type
to the API. This way, customers can run API queries to get that information. - Flag these runners in the runners list
- Remove this in 18.0, when all customers will be migrated over.
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
- We should see much fewer runners that are created with reg tokens because of this, aka customers will migrate quickly.
- We should see fewer requests coming in for support on this (right now, we are manually querying how many runners were registered with reg tokens vs. auth tokens).
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.