Apigee X Northbound + Private Service Connect : GA

[iambaskar]

We are happy to announce that Apigee X support for using Private Service Connect (PSC) for client-to-Apigee (northbound) traffic is now GA.  PSC Northbound will allow customers to remove Bridge VMs (MIG) and use L7 PSC instead to send traffic to Apigee. 

Supported northbound PSC features:

• You can use PSC with any new or existing Apigee instance.
• You can attach multiple PSC network endpoint groups (NEGs) to the Envoy-based, Google Cloud global external HTTP(S) load balancer. Refer Expanding Apigee to multiple regions.
• PSC is supported with VPC Service Controls.
• You can set an outlier detection traffic policy on the backend service for handling failover scenarios automatically. See the following for more information:
  • Traffic policies
  • Configure outlier detection
  • REST Resource: backendServices

See also Northbound networking with Private Service Connect and Migrate northbound routing to Private Service Connect.

[boriskraizman]

Here is a question, can we use global external load balancers? I see there is a restriction on using a classic GLB and what would be a difference using the new one with Envoy?

[iambaskar]

Unfortunately, classic GXLB does not support PSC endpoints. So, you need to provision new Envoy based GXLB to make use of the PSC feature.

The differences between the load balancers can be found @ https://cloud.google.com/load-balancing/docs/https