> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview-1/gcp-systems-settings/gcp-infrastructure-settings.md).

# GCP Infrastructure Settings

Configure Infrastructure settings in the DuploCloud UI for GCP users

## Configuring Infrastructure settings:

1. Navigate to **Administrator** -> **Infrastructure**.
2. In the **NAME** column, select the name of the Infrastructure you want to configure settings for.
3. Select the **Settings** tab, and click **Add**. The **Infra - Set Custom Data** pane displays.
4. From the **Setting Name** list box, select the setting (see list of settings below).
5. Click **Enable**, or enter an appropriate value.
6. Click **Set**. The setting is applied to the Infrastructure.

### Infrastructure Settings

| **GKE Endpoint Visibility**        | Configures GKE endpoint visibility to public, private, or both.      |
| ---------------------------------- | -------------------------------------------------------------------- |
| **Cluster Autoscaler**             | Enables Cluster Autoscaler for the Infrastructure.                   |
| **GKE Minimum Ports Per VM**       | Specifies the minimum number of ports that must be available per VM. |
| **Enable Dynamic Port Allocation** | Enables dynamic port allocation.                                     |
| **Enable K8s Windows Workload**    | Enables Kubernetes support for Windows workloads.                    |
| **Other**                          | Allows configuring a custom or unlisted setting.                     |


---

# 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.duplocloud.com/docs/automation-platform/overview-1/gcp-systems-settings/gcp-infrastructure-settings.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.