cloud-run
Deploy and debug headless robotics containers on Google Cloud Run.
Install
npx skills add https://github.com/robium-ai/robium/tree/main/skills/cloud-run
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install robium-ai-robium@llmmart
git clone https://github.com/robium-ai/robium.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole robium-ai/robium collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
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.
Files (robium)
-
DEPLOYMENT.md 4.8 KB
Loading… -
FAILURES.md 2.4 KB
Loading… -
GAZEBO-ROS2.md 2.3 KB
Loading… -
SKILL.md 2.9 KB
--- name: cloud-run description: Deploy and debug headless robotics containers on Google Cloud Run. --- # 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 to `live-demo`. ## Verify before deploying - Check current commands, flags, quotas, WebSocket behavior, and pricing in [official Cloud Run documentation](https://cloud.google.com/run/docs) and the [`gcloud run deploy` reference](https://cloud.google.com/sdk/gcloud/reference/run/deploy). - Read [DEPLOYMENT.md](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](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](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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.