Looker (Google Cloud core) southbound access to external services using Private Service Connect

The following Codelabs explain how to set up southbound access from Looker (Google Cloud core) to external services using Private Service Connect.

• Codelab: Looker (Google Cloud core) PSC Southbound HTTPS Internet NEG SMTP

  In this codelab, you will create a southbound connection to Looker (Google Cloud core)'s SMTP service using an internal TCP proxy load balancer and internet network endpoint group (NEG) with the FQDN notifications-pa.googleapis.com invoked from a Looker (Google Cloud core) PSC as a Service Consumer.

• Codelab: Looker (Google Cloud core) PSC Southbound access to Cloud SQL PSC

  In this codelab, you will perform a southbound connection to Cloud SQL deployed with Private Service Connect as a Service Producer.

• Codelab: Looker (Google Cloud core) PSC Southbound SSH Internet NEG

  In this codelab, you will perform a southbound SSH connection to GitHub using an internal TCP proxy load balancer and internet network endpoint group (NEG) invoked from Looker (Google Cloud core) PSC as a Service Consumer.

• Codelab: Looker (Google Cloud core) PSC Southbound HTTPS Internet NEG

  In this codelab, you will perform a southbound HTTPS connection to GitHub using an internal TCP proxy load balancer and internet network endpoint group (NEG) invoked from a Looker (Google Cloud core) PSC as a Service Consumer.

• Codelab: Looker (Google Cloud core) PSC Southbound Hybrid NEG to on-premises

  In this codelab, you will perform a southbound connection to an on-premises Postgres database over H-VPN using an internal TCP proxy load balancer and hybrid network endpoint group (NEG) invoked from a Looker (Google Cloud core) PSC as a Service Consumer.