---
cuppy_hub: gcp
cuppy_path: changelog/2026-10-21-compute-family.md
cuppy_section: docs
cuppy_doc: EZJG-ST7B
cuppy_doc_uuid: ec8005a4-b8ac-4bc3-9fa9-47d92c66b1bd
cuppy_permalink: https://cuppy.io/gcp/d/EZJG-ST7B
cuppy_version: 1
cuppy_updated: 2026-10-23T16:16:52.575Z
cuppy_canonical: https://cuppy.io/gcp/docs/changelog/2026-10-21-compute-family
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: 2542ee0d5bb5c1c8dfb27de92d426dac52d1f95e791ef427fe92a8971e4abb7a
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---


# Compute family — first release

## Added

| Document | What it carries |
|---|---|
| `reference/compute/compute-engine.md` | the six machine families and their series, the naming grammar, where custom types are allowed |
| `reference/compute/gke-cluster-modes.md` | Autopilot and Standard, the responsibility split, the two billing dimensions |
| `reference/compute/cloud-run.md` | the four resource types, the immutable revision, jobs to executions to tasks |
| `reference/compute/cloud-functions.md` | the renaming, the Cloud Run platform underneath, the four capability differences |
| `reference/compute/errors.md` | the startup, import, deploy-permission, 429 and 503 strings with cause, check and fix |
| `guides/compute/deploy-a-container-on-cloud-run.md` | seven steps, ending in a verification that separates 429 from 503 |
| `guides/parity/compute.md` | the one-to-three Cloud Run mapping, and the concurrency row that is a correctness risk |

## The two headline facts

1. **The product names changed.** "Cloud Functions" and "2nd gen" are both old; it is **Cloud Run functions**,
   and a modern function deploys *as a Cloud Run service*.
2. **A modern function instance serves up to 1000 concurrent requests**, where 1st gen served one and AWS
   Lambda's execution environment serves one at a time. Code written under the one-request assumption has
   races on Google Cloud. This is documented as a **migration correctness risk**, not a tuning note, in
   `guides/parity/compute.md` §2.

## Absences recorded rather than filled in

- The machine-resource page **prints no last-updated date**, the only page in this release that does not. Series
  availability is zonal and is read live rather than written down.
- The GKE cluster-mode page describes Autopilot's restrictions at the level of "privileges and configuration
  options" and **does not enumerate every forbidden field**; the document says to check specific Pod specs
  against Autopilot's own constraints page.

## Known missing

- **Compute Engine and GKE error catalogues.** The family's error document covers Cloud Run only, because that
  is where a migrated container lands. GKE node-pool and Compute Engine quota failures are not catalogued.
- Managed instance groups, autoscaling policies and instance templates.
- Sole-tenant nodes, Confidential Computing, Spot VMs and preemptibility.
- Artifact Registry, named in the parity table and not documented.
- Cloud Run service-to-service authentication and VPC egress settings (partly covered in the networking family).


---
<!-- cuppy -->
You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 91 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/gcp/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.
<!-- /cuppy -->