22-How to create a Private Service Connect endpoint with your custom published Service in GCP

An endpoint connects to services in another VPC network using a Private Service Connect forwarding rule. Each forwarding rule counts toward the per project quota for Private Service Connect forwarding rules to access services in another VPC network.
When you use Private Service Connect to connect to services in another VPC network, you choose an IP address from a regular subnet in your VPC network.
The IP address must be in the same region as the service producer's service attachment. The IP address counts toward the project's quota for Internal IP addresses.
When you create an endpoint, it is automatically registered with Service Directory, using a namespace that you choose, or the default namespace, goog-psc-default.
If you want to make the endpoint available from more than one region, turn on global access.

[@GulabDigambarNandanvar]

This should work for the below case.
2 Diff Projects, 2 diff. network, 2 Jenkins,1 Windows JH - from the JH needs to access both Jenkins via private IP for that needs to networking.
For networking, I am looking for another option like VPC peering and PSC, Can you please let me PSC will work in this use case.

[@thecloudbaba8668]

If you want to expose Jenkins as a service to your consumer, yes you can use PSC.. peering also works here

[@user-tq1mi8iq6f]

if we are using shared VPC network, can we create endpoints in service projects

[@thecloudbaba8668]

You can but what is the use case ?

[@user-tq1mi8iq6f]

i want to create private uptime check but VPC information is showing only in host project not in the service project i.e monitoring project.

[@thecloudbaba8668]

I think you can do that.. will try to cover this use case .. could you elaborate more specific details around your requirements..

[@user-tq1mi8iq6f]

Thanks@@thecloudbaba8668 i would like to create private uptime check for the applications which are running on GCP VM and GKE clusters with internal IP only.