Google Cloud global external Application Load Balancer Configuration Skill

Purpose & Agent Guidance

This skill enables the agent to guide users through a structured, 6-step discovery process to design and deploy Google Cloud global external Application Load Balancers (incorporating Cloud CDN, Cloud Armor, and Service Extensions).

Assumptions & Target Environments:

• This skill assumes it is called from environments (such as Gemini CLI, Antigravity, etc.) where the Google Cloud CLI (gcloud) can be executed.
• If gcloud is not available or accessible, the skill cannot perform automated resource discovery or managed deployment actuation. In such environments, the skill will limit its support to guiding the design and generating Terraform HCL configurations.

When executing this skill, the agent must:

• Map user workload requirements to simplified, opinionated best-practice configurations using actual Google Cloud product names.
• Progressively disclose details, hiding advanced complexity unless the user explicitly asks for customization.
• Leverage the reference documents in the references/ directory to perform resource discovery, code generation, actuation, and drift detection.

The 6-Step Configuration Flow

Step 1: Basics

• Project Discovery: Consult references/resource-discovery.md to auto-detect the Google Cloud project ID. Present the discovered project ID to the user.
• Ask the user for the foundational details of their load balancer:
  • Name & Description: What should we call this load balancer?
  • Protocol Selection: Do they need HTTP, HTTPS, or both?
  • Certificate Management: Do they want to use Google-managed certificates or bring their own existing certificates?

Step 2: Origin Configuration

Help the user define their backend workloads through a strictly sequential, step-by-step loop. Do NOT ask everything at once. All steps are mandatory.

• Sub-step A - Origin Setup: Ask if they have a single origin or need multi-origin support. Wait for response.
• Sub-step B - Origin Types: Ask them to select the backend types from: Cloud Storage Buckets, Compute Engine Managed Instance Groups (MIGs), Google Kubernetes Engine (GKE) Clusters, Cloud Run Services, or External/Internet origins (IP/FQDN). Wait for response.
• Sub-step C - Origin Definition Loop: Execute the following loop sequentially for EACH origin type selected in Sub-step B. Wait for the user to answer for one origin before asking about the next: