Compute Engine service attachments accept --routing-mode in beta

Introduced 2026-08-04 · score 0.93

HOW TO USE IT

When creating or updating a Compute Engine service attachment in beta, set `--routing-mode` to `PACKET_INJECTION` or `STANDARD_ROUTING` to choose its tunneling routing mode.

WHY THIS HELPS

Set a routing mode when creating or updating a Compute Engine service attachment.

REQUIREMENTS AND LIMITATIONS

• Availability: beta
• create: NAME (required): Name of the service attachment to create.
• create: --nat-subnets (required): Producer-provided subnetworks to use for NAT.
• create: --producer-forwarding-rule / --target-service (required): Specify exactly one: the target forwarding rule, or the URL of the target service.
• update: NAME (required): Name of the service attachment to update.
• --routing-mode: Sets the tunneling routing mode. Allowed values: `PACKET_INJECTION` (traffic is reinjected into the consumer network) or `STANDARD_ROUTING` (de-encapsulated response traffic is returned to the client). The docs do not state these values are mutually exclusive; choose one value.
• create: --region: Region of the service attachment; omission may prompt for a region in interactive mode.
• update: --region: Region of the service attachment; omission may prompt for a region in interactive mode.
• Prerequisite: Use the beta command track. For creation, an existing producer forwarding rule or target service and NAT subnetworks are required.

FIRST-PARTY EVIDENCE

• https://docs.cloud.google.com/sdk/docs/release-notes#57900_2026-08-04
• https://docs.cloud.google.com/sdk/gcloud/reference/beta/compute/service-attachments/create
• https://docs.cloud.google.com/sdk/gcloud/reference/beta/compute/service-attachments/update

Check the installed version and the source before using it. Entry JSON

Report a problem with this card