Walkthrough: Expand Apigee X Pay-as-you-go to a new region using Private Service Connect

Hey All,

In this video I go through the setup for adding a second Apigee X runtime instance in a new region using Private Service Connect. I also show how to update the GCP network components that route traffic to the new Apigee X runtime.

⚠️ NOTE ⚠️ At the moment, there is a limitation on the GCP HTTPS Global Load Balancer where it's not able to have active health-checks when using PSC NEGs. Instead, the load balancer uses a passive health check that can lead to brief downtime during a region fail-over.

The alternative is to have the Global Load Balancer (classic) send traffic to a regional Managed Instance Group network bridge, which forwards traffic to corresponding Apigee X runtime instance. I have another video describing how to do this over at https://youtu.be/wzOpiGptSaE .

The video is split into chapters covering the following topics:

  • 00:00 Intro
  • 00:19 Agenda
  • 00:37 Overview of Existing Setup
  • 01:10 Action Plan
  • 01:58 Alternative CLI Approach
  • 02:29 Create runtime instance in new region
  • 02:57 How to come up with peering ranges
  • 03:21 Allocate peering ranges
  • 04:20 Update peering connection
  • 05:16 Create disk encryption key
  • 05:36 Grant IAM access to disk encryption key
  • 05:46 Attach environment to instance
  • 05:56 Service attachment project allow-list
  • 06:53 Pay-as-you-go Gateway-nodes before
  • 07:32 Pay-as-you-go Gateway-nodes after
  • 08:17 Create subnet for new PSC NEG
  • 08:51 Create new Private Service Connect (PSC) Network Endpoint Group (NEG)
  • 09:51 Update Global Load Balancer backend service
  • 10:59 Load balancing algorithm
  • 11:14 Testing approach
  • 11:42 Update helloworld API Proxy to show runtime instance region
  • 12:39 Multi-region end-to-end hellowworld API Proxy test
  • 13:30 Summary & Calls to Action
Contributors
Version history
Last update:
‎01-30-2023 04:10 PM
Updated by: