⚠Hey All, 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. The previous version of the provisioning wizard (accessible at apigee.google.com/setup) uses this approach.
Great stuff Miguel! I wanted to ask you about something. Private Service Connect service attachments use a NAT subnet that hides the Consumer VPC network. Is there any way to define or view that subnet from Apigee? I'm asking because when I view the api logs, there is a weird IP from a DoD range that is marked as "client_ip".
⚠Hey All, 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. The previous version of the provisioning wizard (accessible at apigee.google.com/setup) uses this approach.
Nice walkthrough Miguel, glad to see the wizard is now using Private Service Connect instead of Managed Instance Group.
hope you create a video on how to build internal load balancer for apigee
Great stuff Miguel! I wanted to ask you about something. Private Service Connect service attachments use a NAT subnet that hides the Consumer VPC network. Is there any way to define or view that subnet from Apigee? I'm asking because when I view the api logs, there is a weird IP from a DoD range that is marked as "client_ip".