GCP NODE20 INVENTORY

Use cases

Three situations where teams use this matrix around the decommission window.

Functions-only shop before 30 October

Who: A platform engineer with dozens of 2nd-gen functions.

Task: List every nodejs20 function and schedule runtime bumps.

Steps: Select products=functions, shape=source, deadline=before; copy list command; filter nodejs20; open tickets per service.

Result: A prioritized migrate board before create/update blocks.

Cloud Run mix of source and containers

Who: A team that lift-and-shifted some services as images and left others on buildpacks.

Task: Avoid migrating containers as if they were managed runtimes.

Steps: Select mixed products and mixed_shape on the matrix; export the checklist; tag each service in a spreadsheet as source or container; only bump managed runtimes on the source lane; schedule image rebuilds and base-image CVEs on the container lane separately.

Result: Two workstreams with clear owners and no wasted effort “migrating” containers as if Google managed their Node runtime.

Incident inventory after enforcement

Who: On-call finds deploys failing on nodejs20.

Task: Find remaining managed Node 20 quickly.

Steps: Select deadline=after on the matrix; run the emitted list/describe commands in the failing project; migrate production source services first; defer paid extended-support debates until the inventory spreadsheet exists and is shared in the incident channel.

Result: A factual list for incident commanders instead of anecdotal “we thought containers were fine” guesses.