> 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-resources-and-permissions.md).

# Plan Google Cloud Resources and Permissions

Plan the Google Cloud resources, service accounts, permissions, and quota needed to deploy Silk.

Before deploying Silk on Google Cloud, plan the project, compute capacity, networking, and permissions needed for your environment. Confirming these requirements early helps prevent delays during Flex deployment, cluster creation, and DataPod provisioning.

{% stepper %}
{% step %}

## Complete the pre-installation site survey

Work with the Silk deployment team to complete the pre-installation site survey before creating deployment resources or requesting a cluster configuration file.

During the survey, confirm:

* Target Google Cloud project, region, and zone
* Planned cluster size and DataPod configuration
* Compute resource requirements and expected growth
* Network address ranges and connectivity requirements
* Service accounts and permissions

{% hint style="warning" %}
The cluster configuration file is specific to your environment. If key inputs like address ranges or cluster size change after Silk generates the file, you'll need to request a new one.
{% endhint %}
{% endstep %}

{% step %}

## Plan your Google Cloud project and location

Silk runs within a customer-managed Google Cloud project. Identify the project where you'll deploy Flex and create the Silk cluster and DataPods.

Confirm that the selected region and zone support the machine types required for Flex and your planned DataPod configurations. Availability varies by location and current Google Cloud capacity.

If the required resources aren't available, work with the Silk deployment team to identify another supported region or zone before proceeding.
{% endstep %}

{% step %}

## Plan compute capacity and quotas

Your project needs sufficient quota for the Flex virtual machine and the resources used by your planned DataPods. Account for both the initial deployment and expected production growth, including:

* Cluster size and number of DataPods
* Compute and storage resources required for the selected DataPod configurations
* Additional resources needed for future expansion

Review available quota for the required resources, including vCPUs, disks, and IP addresses. Check the applicable regional and global limits, along with current usage.

{% hint style="info" %}
**Quota and resource availability are separate considerations.**

A deployment can still fail if the selected zone has insufficient capacity for a required machine type, even when your project has enough quota. Validate both quota and resource availability before proceeding.
{% endhint %}

Request any quota increases ahead of the planned deployment. The Silk deployment team can help identify the resource requirements for your configuration.

For sizing guidance, see [Plan DataPod Capacity](/deploy/plan-your-deployment/plan-datapod-capacity.md) and [Cluster and DataPod Sizing](/deploy/plan-your-deployment/cluster-and-datapod-sizing.md).
{% endstep %}

{% step %}

## Plan your network

Silk creates its own VPC networks and subnets for Flex and the cluster. Your network planning focuses on the address ranges Silk will use, outbound access for Flex, and the peering connection between your host VPC and the Silk Data 1 VPC. Capture these decisions during the site survey.

For address ranges, cluster sizing, outbound destinations, and host connectivity, see [Plan Google Cloud Networking and Connectivity](/deploy/deploy-on-google-cloud/plan-google-cloud-networking-and-connectivity.md).
{% endstep %}

{% step %}

## Enable the required Google Cloud APIs

Ensure the following APIs are enabled in the deployment project:

<table><thead><tr><th width="215.9259033203125">API</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Compute Engine API</strong></td><td>Supports provisioning and management of the virtual machines and related resources used by Silk.</td></tr><tr><td><strong>Infrastructure Manager API</strong></td><td>Supports the initial Flex deployment from Google Cloud Marketplace.</td></tr><tr><td><strong>Cloud Logging API</strong></td><td>Supports logging for deployment and management operations.</td></tr></tbody></table>

Confirm that your organization's policies allow these services to be used in the target project.
{% endstep %}

{% step %}

## Plan service accounts and permissions

Silk uses service accounts for the initial Flex deployment and for subsequent management operations. Identify the accounts that will serve these purposes and verify their permissions before deployment.

### Identify the service accounts

Before deploying Flex, identify the service accounts you'll use for deployment and ongoing operations, and verify that each account has the required permissions.

<table><thead><tr><th width="162.22216796875">Service account</th><th>Purpose</th><th>Account options</th></tr></thead><tbody><tr><td><strong>Deployment service account</strong></td><td>Used by the Marketplace deployment to provision Flex through Infrastructure Manager.</td><td>Use an existing account with the required permissions or create a dedicated deployment account.</td></tr><tr><td><strong>Flex service account</strong></td><td>Used by Flex to create clusters, provision DataPods, perform regular operations, upgrade software, and delete Silk resources.</td><td>Flex uses the project's Compute Engine default service account unless a custom account is configured.</td></tr></tbody></table>

### Plan permissions across the Silk lifecycle

Validate the Deployment service account's permissions for the Google Cloud Marketplace deployment separately from the permissions Flex needs afterward.

The Flex service account requires permissions for the following lifecycle activities:

<table><thead><tr><th width="211.4814453125">Permission category</th><th>When it's needed</th></tr></thead><tbody><tr><td><strong>Initial configuration</strong></td><td>When creating the initial Silk cluster and its required cloud networking resources.</td></tr><tr><td><strong>Mandatory regular operation</strong></td><td>Throughout normal operation, including cluster management and DataPod provisioning. Retain these permissions.</td></tr><tr><td><strong>Upgrade configuration</strong></td><td>When performing Flex and DataPod software upgrades.</td></tr><tr><td><strong>Cluster deletion</strong></td><td>When deleting clusters or uninstalling Silk.</td></tr></tbody></table>

If your organization reduces permissions after initial configuration, review the full permission set before changing IAM roles. Some permissions support more than one lifecycle activity. Preserve the permissions required for ongoing operations and ensure that permissions for planned upgrades or deletion are available when needed.

Review organization policies and IAM restrictions with your Google Cloud administrator. These controls must allow Silk to create and manage the required resources.
{% endstep %}

{% step %}

## Prepare access to the Silk images

Silk provides the c.node and d.node images used to provision DataPods through the **Silk-Image-Repo** Google Cloud project.

Before cluster creation, confirm that:

* Silk has granted your Google Cloud account access to the image repository
* You have the current image names provided by Silk
* The account importing the images can create images in the deployment project

Both required images must be imported into the deployment project before creating the cluster. If an image is missing or its name doesn't match the Silk-provided name, DataPod creation fails. Contact [Silk Support](https://support.silk.us) if you can't access the image repository or need the current image names.
{% endstep %}

{% step %}

## Confirm Google Cloud Marketplace access

The Silk deployment package is available through Google Cloud Marketplace and is deployed with Infrastructure Manager. Before launching the deployment, confirm that:

* The deploying user can launch the Silk Platform listing from Google Cloud Marketplace in the target project
* The required APIs are enabled in the project
* The Deployment service account you plan to use has the required deployment roles
  {% 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-resources-and-permissions.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.
