Introduce Registry only crawling to CMBR
Based on analysis in gitlab-org/gitlab#351229 (comment 930320297), we need to introduce Registry-specific load.
Staging registry located at https://registry.staging.gitlab.com
and it's a separate service. It appears that service needs some authentication. It's possible that Registry load may be a subset of API which specifically targeted to container registry.
Steps
-
Explore if using GET requests from Container Registry API generates traffic to Registry -
Explore if it's possible to authenticate and emulate navigation to https://registry.staging.gitlab.com/v2/<project>/tags/list
-
If it's not possible, explore if running cmbr
just againsthttps://registry.staging.gitlab.com
generates traffic
-
-
Add new registry
traffic option and sendGET /projects/:id/registry/repositories/:repository_id/tags
requests to list registry repo tags -
Add registry load job similar to generate_load_api
orgenerate_load_web
if steps above were successful
Registry endpoints
Example URL requests to Staging registry based on Kibana logs https://nonprod-log.gitlab.net/goto/841c3400-c798-11ec-b3a6-472d0398dd6e:
Edited by Nailia Iskhakova