THE FIELD GUIDE / OPERATIONS
Google Cloud & IAP
Reach a VM through direct SSH or an authenticated IAP tunnel.
Choose the route
Under Server → Connection, select Direct SSH with a reachable private or static external address, or Google Cloud IAP with project, zone, instance and port. Both retain the same server key, restricted bridge and pinned host fingerprint.
Prepare IAP
Use the dedicated GCP integration runtime to isolate Google Cloud CLI and cloud identity, or follow the repository’s existing GCP-ready app/worker image setup for the complete installation. Configure a dedicated gcloud identity, enable Compute Engine and IAP APIs, grant narrowly scoped IAP tunnel and instance-read permissions, and configure the guest SSH firewall for IAP. Test the saved connection before enrolling broadly.
Use the GCP-ready installer
./install-gcp.sh --project YOUR_PROJECT --zone us-central1-a --instance TEST_VM \
--public-url https://patchy.example.com:8443Run from a trusted checkout on a Linux Docker host with Compose v2 and Python 3. The installer prepares the CLI-capable runtime and verifies token acquisition and instance read access.
Dedicated integration node
The optional GCP integration node reports identity and readiness to the deployment dashboard and exposes scoped authentication, instance lookup, connection verification and IAP operations to controllers and workers. Explore the isolated GCP runtime.
Cloud fleet operations
Read-only cloud inventory and lifecycle visibility complement connection routing. Reviewed isolation and rebuild workflows keep cloud changes tied to incident evidence and validated recovery paths.
Open the application reference for capability scope and technical details.
Open Open GCP.md on GitHub ↗