> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/deploy/deploy-on-google-cloud/plan-google-cloud-networking-and-connectivity.md).

# Plan Google Cloud Networking and Connectivity

Plan subnet address ranges, Flex connectivity, and the iSCSI network path between your application hosts and Silk DataPods.

Before deploying Silk on Google Cloud, plan the IP address ranges for Flex and the Silk cluster, identify how Flex will reach required services, and decide how application hosts will connect to your DataPods. Use the pre-installation site survey to record these decisions with the Silk deployment team and your network team.

{% stepper %}
{% step %}

## Plan VPCs and subnet address ranges

Your application and database hosts use your existing host VPC. The Flex deployment creates a dedicated Flex VPC and subnet using the CIDR range you provide. When you create the cluster, Flex creates the remaining Silk VPCs and subnets using the address ranges you specify. Have those ranges ready before deployment so Silk can provision the networks.

{% hint style="warning" %}
**Silk creates its own VPC networks and subnets.**

Deploying Silk into an existing VPC or using pre-created Silk subnets isn't currently supported. Don't create the Silk VPC networks or subnets before deployment.
{% endhint %}

<table><thead><tr><th width="221.8519287109375">Silk network</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Flex</strong></td><td>Hosts the Flex VM, which provides Silk management and API services.</td></tr><tr><td><strong>Management</strong></td><td>Carries management traffic between Silk components.</td></tr><tr><td><strong>Data 1</strong></td><td>Carries iSCSI traffic between application hosts and DataPods.</td></tr><tr><td><strong>Data 2</strong></td><td>Carries replication traffic.</td></tr><tr><td><strong>Internal 1 and Internal 2</strong></td><td>Carry traffic between Silk cluster nodes.</td></tr></tbody></table>

Record the Flex subnet range separately from the cluster ranges. When you create the cluster, you can provide an address range for Flex to allocate across the cluster subnets or specify each cluster subnet range individually.

Choose a cluster size that supports your initial deployment and expected growth: **Small** (`/24`), **Medium** (`/23`), or **Large** (`/21`). The cluster size determines the available address space and the maximum number of Silk resources you can deploy. You select the size at cluster creation, and that selection is fixed for the life of the cluster.

Check the planned ranges against existing networks. The Flex and cluster ranges must not overlap with each other or with networks they'll connect to. In particular, confirm that the Data 1 subnet doesn't overlap with the host VPC's subnet ranges, because VPC Network Peering requires non-overlapping ranges.

Confirm that your organization policies permit Silk to create the required networking resources, including VPC networks, subnets, firewall rules, and peering connections. For service account and IAM planning, see [Plan Google Cloud Resources and Permissions](/deploy/deploy-on-google-cloud/plan-google-cloud-resources-and-permissions.md).
{% endstep %}

{% step %}

## Plan Flex access and outbound connectivity

Identify where administrators will connect from and how they will reach Flex and the SDP Management Console. Review the planned access paths with your network team before deploying Flex.

If your organization restricts outbound access, review the destinations required for deployment and ongoing operations. Verify that Flex can resolve the required hostnames and that your egress policy permits the connections:

<table><thead><tr><th width="245.5555419921875">Destination</th><th>Purpose</th></tr></thead><tbody><tr><td><code>*.gce.archive.ubuntu.com</code></td><td>Ubuntu operating system updates.</td></tr><tr><td><code>clarity.silk.us</code></td><td>Silk HTTPS call home.</td></tr><tr><td><code>storage.googleapis.com</code></td><td>Google Cloud Storage access for Silk HTTPS call home.</td></tr></tbody></table>
{% endstep %}

{% step %}

## Plan host connectivity to DataPods

Use Google Cloud VPC Network Peering between the host VPC and the Silk Data 1 VPC to provide the iSCSI path. Configure peering after Flex creates the cluster and the Data 1 VPC is available.

Before deployment:

1. Identify the host VPC, the application host subnets that need storage access, and who can configure peering on each side.
2. If the VPCs are in different projects, have both project IDs available.
3. Review the firewall rules and organization policies that apply to the iSCSI data path and confirm they permit TCP port `3260` from the application hosts to the DataPods over Data 1.

After configuring both sides of the peering connection, verify that it is **Active**, confirm that the expected subnet routes are present, and test iSCSI connectivity from the application hosts. If your topology requires an additional route from the DataPod to the host iSCSI subnet, review the route with your network team. The SDP Management Console supports configuring static routes on the applicable c.nodes.
{% endstep %}

{% step %}

## Plan replication connectivity

If you plan to replicate between DataPods, identify the source and target replication subnets and confirm how they will reach each other over Data 2. Review routing and firewall requirements for that path. If the DataPods need static routes to reach each other's replication subnets, plan those routes on both systems.
{% endstep %}

{% step %}

## Verify networking readiness

### VPCs and address ranges

* [ ] The Flex subnet range and cluster address plan match the site survey.
* [ ] The cluster size supports your expected growth.
* [ ] The planned ranges don't overlap with existing networks, including the host VPC subnets that will peer with Data 1.
* [ ] Organization policies permit Silk to create the required networking resources.

### Flex access and egress

* [ ] Your organization's network team has reviewed how administrators will reach Flex and the SDP Management Console.
* [ ] DNS resolution and outbound access are in place for required destinations.

### Host and replication connectivity

* [ ] The teams responsible for both VPCs are ready to configure peering after cluster creation.
* [ ] Firewall and routing requirements for host iSCSI traffic are documented.
* [ ] If you plan to use replication, the source and target DataPods have a planned network path.

Keep the finalized address ranges and cluster size consistent with the information provided to Silk Support for your cluster file. If key inputs change after the file is generated, request a new cluster file.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.silk.us/deploy/deploy-on-google-cloud/plan-google-cloud-networking-and-connectivity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
