Google Cloud · Cloud service
Google Cloud Load Balancing with OrchestrAI
Catalog exported 2026-09-02
Build a Google Cloud HTTPS load balancer from chat: health checks, backends, URL maps, certificates, proxies.
OrchestrAI exposes 7 Cloud Load Balancing operations: 3 are low-risk (read-only or low-impact), and 4 create or modify resources and run only after you confirm the plan.
What teams use it for
Teams use OrchestrAI to assemble an external HTTPS load balancer in the right order without memorizing the seven-resource sequence: health check, backend service, URL map, SSL certificate, SSL policy, target HTTPS proxy, and forwarding rule. Each piece is recorded in the ledger so the whole chain can be reviewed as one unit later. Coverage is create-only, with no operation to list, update, or delete any of these components, so editing an existing URL map or retiring a load balancer happens outside chat.
Every Cloud Load Balancing operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Create Health Check |
Create a GCP health check for load balancing | Low risk | No |
Create SSL Policy |
Create a GCP SSL policy for HTTPS load balancing | Low risk | No |
Create URL Map |
Create a GCP URL map for HTTP(S) load balancers | Low risk | No |
Create Backend Service |
Create a GCP backend service for load balancing | Creates resources | No |
Create Forwarding Rule |
Create a GCP forwarding rule for load balancing | Creates resources | No |
Create SSL Certificate |
Create a GCP SSL certificate for HTTPS load balancing | Creates resources | No |
Create Target HTTPS Proxy |
Create a GCP target HTTPS proxy | Creates resources | No |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create an HTTP health check on port 8080 path /healthz called api-hc
- Create a backend service api-backend using api-hc with the web-mig instance group as its backend
- Set up an HTTPS front end for api-backend with a managed certificate for api.example.com and a global forwarding rule on port 443
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Which load balancing operations does OrchestrAI wait for confirmation on?
- Health checks, SSL policies, and URL maps are rated low. Backend services, SSL certificates, target HTTPS proxies, and forwarding rules are medium because they create billable or public-facing resources, and every mutation is shown as a plan before it runs.
- Can OrchestrAI modify an existing Google Cloud load balancer?
- No, the current operations only create new components, so changes to an already-deployed load balancer must be made in the console or with gcloud.
- Which Cloud Load Balancing operations need an extra approval step?
- None of the Cloud Load Balancing operations currently carries a step-level approval gate; they are read-only or run after plan confirmation like any other change.
Other Google Cloud services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.