AGENT SKILL
cloud-run
Deploy and debug headless robotics containers on Google Cloud Run.
- License 许可
- MIT
- 所属仓库
- robium-ai/robium
- 最近更新
- 2026-10-07
- Stars
- ★ 108
- Forks
- 2
01 前言 Front Matter
- name
- cloud-run
- description
- Deploy and debug headless robotics containers on Google Cloud Run.
02 资源文件 3
- 参考文档DEPLOYMENT.md4.8 KB
- 参考文档FAILURES.md2.4 KB
- 参考文档GAZEBO-ROS2.md2.3 KB
03 SKILL.md 正文
Cloud Run
Treat Cloud Run as a request-driven web runtime, not a conventional robot host.
Shape the workload for Cloud Run
- Expose one HTTP port and keep durable state outside the instance.
- Decide whether startup is covered by a held request. Under request-based billing, background robot or simulator boot can lose CPU when no request is open; instance-based CPU changes the cost model.
- Expect WebSocket sessions to inherit the request timeout and instance lifecycle. Size the timeout to the intended session, not to an assumed default.
- Scale to zero unless a paid warm floor is explicitly justified. State the session cost, fleet ceiling, and cold-start expectation.
- General container composition belongs to
integration; the session gateway and visitor lifecycle belong tolive-demo.
Verify before deploying
- Check current commands, flags, quotas, WebSocket behavior, and pricing in
official Cloud Run documentation and the
gcloud run deployreference. - Read DEPLOYMENT.md when building, choosing billing and concurrency, configuring affinity, authenticating CI, or validating the deployed route.
- Treat Robium's measured values as compatibility evidence tied to their workload and date. Re-measure CPU, memory, timeouts, and fleet size for the application being deployed.
- Public shells require a separate threat model for credentials and egress; unauthenticated reachability is not a security design.
Account for robotics networking
- Cloud Run does not provide the multicast discovery expected by Gazebo transport or DDS. A single-container deployment needs an explicit local discovery strategy and evidence that the actual graph communicates.
- For the proven Gazebo Harmonic, ROS 2, and Nav2 deployment conditions, read GAZEBO-ROS2.md. Do not copy those values into a different stack as defaults.
- Route bridge protocol, layouts, and client behavior to
foxglove; Cloud Run only owns how the HTTP/WebSocket route reaches the container.
Debug from the boundary inward
- Distinguish image pull, CPU starvation, transport discovery, application readiness, proxy behavior, affinity, and VPC capacity before changing the application.
- Read FAILURES.md for the evidence that separates common failures.
- A probe under request-based billing must remain open long enough to cover the work it is testing; connect-and-drop can create the failure it appears to diagnose.
Done
- The immutable image starts with the selected billing mode and resource limits.
- Readiness and the real HTTP or WebSocket path work through Cloud Run.
- Idle capacity, session timeout, fleet ceiling, authentication, and cleanup behavior match the stated cost and security boundaries.
04 同仓库更多 Skills
visualization
Choose between RViz2, Foxglove, Lichtblick, and Rerun to inspect robot behavior.
★ 108
testing
Choose proportional evidence for robotics software before claiming it works.
★ 108
test-assets
Choose and manage reproducible worlds, models, datasets, and recordings for robotics tests.
★ 108
skill-author
Author and structure practical Robium skills without unnecessary context or ceremony.
★ 108
simulation
Choose between Gazebo, Isaac Sim, and MuJoCo and define what the simulation must prove.
★ 108
rviz2
Inspect and debug live ROS 2 robot state with RViz2.
★ 108