Skip to content

Document Google Cloud compute environment VPC networking options [COMP-2106] - #1695

Open
justinegeffen wants to merge 8 commits into
masterfrom
docs/COMP-2106-google-cloud-vpc
Open

Document Google Cloud compute environment VPC networking options [COMP-2106]#1695
justinegeffen wants to merge 8 commits into
masterfrom
docs/COMP-2106-google-cloud-vpc

Conversation

@justinegeffen

@justinegeffen justinegeffen commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Jira https://seqera.atlassian.net/browse/EDU-1303

What

Documents the VPC networking advanced options for the Google Cloud compute environment in the Seqera Cloud docs:

  • VPC — select an existing network in the project, with automatic discovery in the form. Shared VPC and fully qualified network references are also accepted.
  • Subnets — one or more subnets in the selected VPC and compute environment region.
  • Network tags — tags applied to launched VMs for firewall rule targeting.
  • Use private address — launch VMs without a public IP address (requires Cloud NAT and Private Google Access on the VPC).

Changes

  • platform-cloud/docs/compute-envs/google-cloud.md — add the four options to the Advanced options section.

This change applies to the Seqera Cloud docs only. The Enterprise pages will be updated when this functionality is included in an Enterprise release.

…P-2106]

Add the VPC, Subnets, Network tags, and Use private address advanced
options to the Google Cloud compute environment page in the Seqera Cloud
docs. These options are available in Seqera Cloud only; Enterprise docs
will follow when the feature is included in an Enterprise release.
@netlify

netlify Bot commented Jul 28, 2026

Copy link
Copy Markdown

Deploy Preview for seqera-docs ready!

Name Link
🔨 Latest commit 9a134d0
🔍 Latest deploy log https://app.netlify.com/projects/seqera-docs/deploys/6a6b5c00b89c8b00087f0e88
😎 Deploy Preview https://deploy-preview-1695--seqera-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@justinegeffen justinegeffen added the cloud-next In the current Cloud staging release. label Jul 29, 2026
Comment thread platform-cloud/docs/compute-envs/google-cloud.md
Comment thread platform-cloud/docs/compute-envs/google-cloud.md Outdated
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Specifying a subnet that does not exist in the compute environment region, or that does not belong to the selected VPC, causes compute environment creation to fail.
:::

- **Subnets**: One or more subnet names within the selected VPC and the compute environment region. VMs are placed in the first listed subnet at launch time; Intelligent Compute may distribute worker VMs across all listed subnets, in order. Leave blank to let Platform select the first available subnet on the network. This field has no effect when no VPC is specified.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jonmarti, this makes sense to me based on your feedback. Just checking if it's accurate?

Comment thread platform-cloud/docs/compute-envs/google-cloud.md
Comment thread platform-cloud/docs/compute-envs/google-cloud.md
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Specifying a subnet that does not exist in the compute environment region, or that does not belong to the selected VPC, causes compute environment creation to fail.
:::

- **Subnets**: One or more subnet addresses within the selected VPC and the compute environment region. VMs are placed in the first listed subnet at launch time; Intelligent Compute may distribute worker VMs across all listed subnets, in order. Leave blank to let Platform select the first available subnet on the network. This field has no effect when no VPC is specified.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"subnet addresses" isn't accurate for either interface. The field takes subnet names (the resource name, e.g. my-subnet), not IP/CIDR ranges. The form's dropdown lists names, and the API contract (GoogleCloudConfig.subnetworks) is documented as "short names or fully-qualified paths" — an address would fail. Should be "subnet names".

Comment thread platform-cloud/docs/compute-envs/google-cloud.md Outdated
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1. Dev/PM/SME Needs a review by a Dev/PM/SME cloud-next In the current Cloud staging release. deslop-to-do

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants