Cloud Run Dev/Test Service Has Min Instances over 0
Minimum instances are kept warm and billed so the first request avoids a cold start, a trade a dev/test service does not need to make.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Set minimum instances to zero on the Cloud Run service. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight applies a lifecycle policy, then checks the change took.
- Applies to
- Cloud Run on Google Cloud
- The fix, by hand
- Open Cloud Console → Cloud Run → Services → the resource → EDIT and DEPLOY NEW REVISION.
- Under Container, sidecars, volumes, networking, security → Container → set Minimum number of instances to 0 (or a lower value).
- Deploy the revision and watch p95 / p99 latency for the next traffic peak.
ZopNight does this for you after a guided review.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1209- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.