gcp-load-balancing

To configure a GCP external HTTP(S) load balancer with SSL termination, you need to set up backend services, URL maps, target proxies, and managed SSL certificates. This Skill generates those production-ready configurations using gcloud CLI commands or Terraform HCL.

Yes, you can use Terraform to set up a GCP load balancer for Cloud Run. This Skill generates Terraform HCL to configure serverless Network Endpoint Groups (NEGs), allowing you to route external traffic to serverless backends like Cloud Run, Functions, and App Engine.

The best way to add Cloud Armor policies to a GCP load balancer is to attach security policies directly to your backend services during configuration. This Skill generates the necessary gcloud or Terraform configurations to integrate Cloud Armor for traffic protection.

Yes, GCP load balancing supports both internal and external traffic management. This Skill facilitates the setup of both external HTTP(S) load balancers for internet-facing traffic and internal load balancers for private network traffic using gcloud CLI and Terraform.

To generate health checks for GCP backend services and instance groups, you define health check parameters within your load balancer configuration. This Skill produces production-ready configurations that include necessary health checks for various backend types like instance groups and serverless NEGs.