Access to spinnaker-community GCP project across VPC service control

[urbanenomad]

We are looking to use spinnaker-community in our GCP GKE cluster but we are also protecting our cloud resources via VPC Service control which blocks all egress and ingress traffic to other GCP projects not within the VPC service control. So any external projects will get blocked from accessing any GCP APIs such as cloud storage access or container registry or artifact registry. The only way to get access to these external cloud resources is to get the GCP project number of external cloud project. I am trying to get access to the following public cloud resources

us-docker.pkg.dev/spinnaker-community/docker/halyard

Which is listed in the spinnaker-helm templates. I was wondering if it is possible to get the GCP project number associated with this account so that I can white list it in my egress read policy within our GCP VPC service control to get access.

[abhinaybyrisetty]

Not sure if the container registry (us-docker.pkg.dev/spinnaker-community/docker) is hosted on GCP. Please reach out in the community slack channel, SIG team might have some idea on this.