Cloud Build 2gen host connection to GitLab Self-managed

[antonio_mazzeo]

Hello everyone! 🙂

Unfortunately I'm unable to connect to GitLab Self-managed from Cloud Build as described in this guide: https://cloud.google.com/build/docs/automating-builds/gitlab/connect-host-gitlab-enterprise-edition
GitLab is deployed in a GCE vm, added to a NEG and exposed via Regional internal Application Load Balancer. On top of that, I've published a service in Private Service Connect.
From another project, I've allocated a private IP address and registered the GitLab service from earlier in Service Directory.
Gitlab runs on https protocol through a self signed certificate and everything is set on europe-west1 region (vm, neg, lb, service, network).
I can connect to GitLab without issues on the VPC configured for the Service Directory service, but Cloud Build can't (giving "message": "Failed to verify authorizer_credential: Get \"https://****/api/v4/user\": generic::unavailable: retry RPC: maximum retry number 3 exceeded: harpoon unreachable error UNREACHABLE_CONNECT_TIMEOUT").
I tried connecting both on a private DNS name (zone configured on Service Directory) and directly to the IP assigned earlier for the Service Directory service (again, from the VPC everything works, Cloud Build hangs).

Is there something I'm missing? Self signed certificates are allowed?
Thank you!
Antonio

[Afvan]

Did you figure out - what was the issue here ?

becuase I'm also facing the same issue 😅

[Devbythebay]

Ensure that all necessary IAM roles are correctly set for Cloud Build to interact with your GitLab service.