Containers · 3 November 2026

Google Cloud Run Admin API v2

Containers now accept the Cloud Run Admin API v2 services methods at /compat/google-cloud-run: set the client's endpoint to https://<your API host>/compat/google-cloud-run and use a Runtime API key as the bearer token. services.create, services.get, services.list (paginated with pageSize and pageToken), services.patch and services.delete are supported; each service is a Container labeled with its project and location, and a service under another project or location returns 404. One container's image, command, args, env (name and value pairs), workingDir, one port, resources.limits.cpu (1, 2, 4 or 8) and resources.limits.memory (512Mi to 32Gi), scaling.minInstanceCount, scaling.maxInstanceCount and maxInstanceRequestConcurrency map to the Container's spec, with Cloud Run's defaults: a service scales to zero unless minInstanceCount is set. Any other field returns 400 with a message naming it. Create, patch and delete return their operation with done: true, so clients do not poll. services.patch replaces the whole template, so its body must include template.containers[0].image; updateMask and etag return 400. A service's name holds its Container ID, not the serviceId requested; serviceId follows Cloud Run's rule (1 to 49 lowercase letters, digits and hyphens, starting with a letter) and is the create's idempotency key for 24 hours, so a retried create returns the same service instead of creating a second one; once that service is deleted, a create with the same serviceId creates a new one. Revisions, traffic other than 100% to the latest revision, validateOnly, allowMissing and the IAM methods are not yet available.