> 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/google-cloud-deployment-overview.md).

# Google Cloud Deployment Overview

Explore the architecture, components, and workflow for deploying Silk in your Google Cloud environment.

Silk runs within your Google Cloud environment, providing storage for application and database workloads while managing the underlying cloud resources through Silk Flex.

Deploying Silk involves preparing your Google Cloud project, deploying Flex, creating a Silk cluster, and provisioning DataPods. This article introduces the architecture and deployment sequence so you can understand how the components fit together before starting the installation.

The following architecture diagram shows how Silk Flex, DataPods, and application hosts fit within a Google Cloud environment.

## Google Cloud deployment architecture

Silk is deployed within a customer-managed Google Cloud project. Your application and database hosts remain in their existing host Virtual Private Cloud (VPC), while Silk creates dedicated VPC networks and subnets for its components.

Flex provides the orchestration and management layer. It creates the cluster's networking resources, provisions DataPods, and manages cloud resources throughout the deployment's lifecycle. DataPods provide the storage platform for your application data.

<figure><img src="https://3771785211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRoeFiUtkaS7g8f3vjz5%2Fuploads%2FoZslssn6u4nqK1rBtJrp%2Fgcp-architecture.png?alt=media" alt=""><figcaption></figcaption></figure>

After cluster creation, VPC Network Peering connects your host VPC to the Silk Data 1 VPC, providing the network path for iSCSI traffic between application hosts and DataPods.

## Key deployment components

<table data-search="false"><thead><tr><th width="279.25927734375">Component</th><th>Deployment role</th></tr></thead><tbody><tr><td><strong>Google Cloud project</strong></td><td>Contains the Google Cloud resources used by the Silk deployment, including virtual machines, networks, and imported Silk images.</td></tr><tr><td><strong>VPC networks and subnets</strong></td><td>Provide dedicated paths for Flex, management, application data, replication, and internal cluster communication. Silk creates these resources during deployment and cluster creation.</td></tr><tr><td><strong>Silk Flex</strong></td><td>Orchestrates cluster creation, provisions DataPods, and manages the cloud resources required for ongoing Silk operations.</td></tr><tr><td><strong>Silk DataPods</strong></td><td>Provide storage to application hosts and run on Compute Engine instances. DataPod compute nodes (c.nodes) process storage I/O, while data nodes (d.nodes) provide the underlying storage resources. d.nodes are grouped into protected media nodes (m.nodes), and the compute and storage layers scale independently.</td></tr><tr><td><strong>Application and database hosts</strong></td><td>Run your workloads and access storage on DataPods over iSCSI through the host VPC's connection to Silk.</td></tr><tr><td><strong>Google Cloud deployment services</strong></td><td>Google Cloud Marketplace and Infrastructure Manager deploy Flex. Compute Engine supplies the virtual machines used by Flex and DataPods.</td></tr><tr><td><strong>Service accounts and IAM permissions</strong></td><td>Authorize deployment and management operations. A Deployment service account provisions Flex through Marketplace deployment. After deployment, Flex uses the project's Compute Engine default service account for cluster creation and ongoing operations.</td></tr><tr><td><strong>Silk Clarity and supporting services</strong></td><td>Support monitoring, health reporting, image delivery, and lifecycle operations thorugh outbound connectivity from the Silk environment.</td></tr></tbody></table>

The detailed deployment documentation defines the required permissions, APIs, quotas, and connectivity for these components.

## Network connections

Silk separates traffic across six dedicated VPC networks:

* **Flex:** Hosts the Flex virtual machine and its management API services.
* **Management:** Supports management traffic and communication between Silk components.
* **Data 1:** Carries iSCSI traffic between application hosts and DataPods.
* **Data 2:** Supports replication traffic.
* **Internal 1 and Internal 2:** Support internal cluster communication.

You define the required address ranges during deployment and cluster configuration. Silk then creates the associated VPC networks and subnets.

{% hint style="warning" %}
Deploying Silk into an existing VPC or using pre-created Silk subnets is not currently supported.
{% endhint %}

Once the cluster networks exist, configure VPC Network Peering between the host VPC and the Silk Data 1 VPC. Routing and firewall rules must allow the required iSCSI traffic. Flex also requires outbound HTTPS connectivity to Silk services for monitoring and lifecycle operations.

## Deployment workflow

{% stepper %}
{% step %}

### Plan the deployment

Work with the Silk deployment team to complete a pre-installation site survey. Confirm the target project, region and zone, planned DataPod configuration, network address ranges, and expected capacity requirements.

Plan for a cluster size that accommodates your anticipated growth. The selected cluster size cannot be changed after cluster creation.
{% endstep %}

{% step %}

### Prepare the Google Cloud environment

Validate resource quotas, machine type availability, required APIs, service account permissions, and network connectivity. Request access to the Silk image repository and obtain the environment-specific cluster configuration file from Silk Support.

This preparation ensures that Flex can create and manage the resources required for your deployment.
{% endstep %}

{% step %}

### Deploy Flex

Deploy Flex from Google Cloud Marketplace using Infrastructure Manager. Specify the deployment settings, including the Flex subnet address range. The deployment creates the Flex virtual machine and its networking resources.
{% endstep %}

{% step %}

### Create the Silk cluster

Import the Silk-provided c.node and d.node images into your deployment project. In Flex, upload the cluster configuration file and configure the cluster size, network address range, and default settings.

Flex creates the cluster and its required Google Cloud resources.
{% endstep %}

{% step %}

### Provision storage and connect hosts

After cluster creation, configure VPC Network Peering between the host VPC and Silk Data 1 VPC. Validate routing and firewall rules, then provision DataPods and storage resources and configure your application hosts for iSCSI access.
{% endstep %}
{% endstepper %}

## Next steps

For guidance on configuration planning, see [Plan a Silk Deployment](/deploy/plan-your-deployment/plan-a-silk-deployment.md) and [Cluster and DataPod Sizing](/deploy/plan-your-deployment/cluster-and-datapod-sizing.md).


---

# 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/google-cloud-deployment-overview.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.
