PinPole User Guide — GCP supplement
Version 2.0 · New in the split guide structure (no GCP chapter in v1.0)
Read Shared features first. This page is Google Cloud–specific.
Implementation note: service JSON specs in the codebase live under a gpc folder — documentation and the app refer to them as GCP services.
1. GCP on the canvas
- Palette entries map to Google Cloud products (Cloud Run, GKE, Cloud Storage, Pub/Sub, Vertex AI, etc.).
- Infrastructure placement uses VPC network name, region/zone, and subnet type (private/public) consistent across nodes that belong to the same network story.
- Validation prevents impossible edges according to GCP-oriented patterns encoded in the product.
Catalogue: GCP catalog lists each service, internal node ID, and configuration sections.
2. Simulation (GCP)
Simulations approximate Google Cloud scaling limits, latency, and cost drivers based on your node parameters.
- Prefer explicit machine shapes, min/max instances, and regional choices that mirror intended production.
- Use execution history to compare runs after you change Autoscaling, Cloud CDN, or data tiers.
Shared workflow: Run simulation, Interpret results.
3. Infrastructure code and export (GCP)
| Target | Notes |
|---|---|
| JSON | Portable graph/config export for integrations (when exposed). |
| Terraform | Typical hand-off for GCP teams; confirm exact maturity in Export. |
| Deployment Manager / gcloud | May appear over time as export targets. |
| PNG / GIF | Visual exports from the canvas toolbar or recording features — Canvas tools. |
Shared detail: Shared features — §10–11.
4. Deploy to Cloud — Coming soon (GCP)
One-click / guided deploy from PinPole into a live GCP project is coming soon. Current best practice:
- Validate in PinPole with simulation and recommendations.
- Export artefacts (JSON / Terraform as available).
- Apply with your existing Terraform, Cloud Build, or GitOps process.
Live reference for managed deploy today: AWS supplement.
5. Cloud Terminal (GCP context)
Cloud Terminal is confirmed for GCP workspaces — same capabilities as other providers: ask about quotas, topology, and config against the modelled environment during workflows.
Details: Cloud Terminal.
6. Cost and quotas
- Estimated $/mo in runs honours GCP-flavoured assumptions; validate with the Google Cloud Pricing Calculator and your contracts.
- Watch quota fields in node panels (APIs, CPU, egress assumptions).
7. Related docs
| Topic | Link |
|---|---|
| Shared workflows | Shared features |
| Service index | GCP catalog |
| Roadmap | Upcoming features |
Return to User guide overview · Shared features · AWS · Azure