cloud-run
SolidDeploy container apps to Google Cloud Run — ko or Dockerfile images to Artifact Registry, keyless CI via Workload Identity Federation, Secret Manager wiring. Use when shipping a service, web app, or ADK agent to GCP.
Install
Quality Score: 80/100
Skill Content
Details
- Author
- fmind
- Repository
- fmind/dotfiles
- Created
- 4 months ago
- Last Updated
- yesterday
- Language
- Go
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
cloud-run
Deploy headless robotics / sim / demo containers to Google Cloud Run: the build → Artifact Registry → Cloud Run path plus the gotchas that bite sim workloads (no UDP multicast for gz-transport/DDS, CPU allocated only while a request is open, session affinity for per-visitor instances, request timeout / concurrency for long-lived WebSockets, VPC subnet sizing). Use when: 'deploy to Cloud Run', 'gcloud run deploy', 'Cloud Build', 'Artifact Registry', 'host the sim in the cloud', 'Cloud Run WebSocket / Foxglove bridge times out', 'session affinity', '--no-cpu-throttling', 'GZ_RELAY / GZ_IP on Cloud Run', deploy auth from CI with a GCP service-account key. Owns the Cloud Run deploy mechanics that live-demo and environments point at. Not for: the demo orchestrator, session gateway, or mission-control page (live-demo); GPU-cloud/RunPod or uv-vs-Docker choice (environments); general non-robotics gcloud/GCP basics (upstream Google docs).
gcp-cloud-run-github-actions
GitHub Actions workflows for deploying containerized services to Google Cloud Run — auth, image caching, multi-job pipelines, VPC/Cloud SQL, post-deploy checks. Use when building CI/CD pipelines for Cloud Run.
cloud-architecture-gcp
GCP service-level architecture knowledge — compute (Cloud Run/GKE/Cloud Functions/GCE), data (Cloud SQL/Spanner/Firestore/Bigtable), messaging (Pub/Sub/Cloud Tasks/Workflows), analytics (BigQuery), edge (Cloud CDN/Load Balancing/API Gateway), storage + secrets (GCS/Secret Manager/Artifact Registry), and Vertex AI. Cost models, quotas, failure modes, and cold-start gotchas. Activate when the active cloud is GCP and the work involves designing, scaling, costing, or diagnosing GCP architecture (Cloud Run cold starts, Cloud SQL connection limits, Spanner hot spots, egress, Pub/Sub backlog).