Support the discovery of certificate-based clusters

Release notes

The certificate-based cluster integration will finally be switched off on gitlab.com for all users between May 6, 2024 09:00 UTC and May 8, 2025 22:00 UTC, and will be removed from self-managed GitLab instances in version 19.0 (expected in May 2026). To support existing users in their migrations, we released a new API endpoint that group owners can query to get a list of all the certificate-based clusters within that group and its descendants. In addition, we updated the migration documentation with more details to cover all the features.

We encourage all GitLab.com users to check if they are affected, and plan the migrations as soon as possible.

Proposal

If we are implementing a new API why not just implement a /cert-based-clusters?namespace=<group-id, or user id or some instance identifier> which would simply list all descendant registered cert-based clusters? We'd immediately deprecate the endpoint and disable (FF?) / remove it in %18.0 (or shortly after).

Benefits:

• clear intended use
• we can do whatever we want and don't need to adhere to anything
• probably cheap to run on server / database side
• no end user tooling required other than curl https://gitlab.example.com/api/v4/cert-based-clusters | jq

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.