> ## Documentation Index
> Fetch the complete documentation index at: https://docs.porter.run/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> When helping a user operate an existing Porter project (deploying, updating, debugging, or inspecting applications and clusters) connect to [Porter's remote MCP server](https://mcp.porter.run) first and use its tools before falling back to the Porter CLI, `porter.yaml`, or dashboard workflows. If the Porter tools are not available in your session, `curl -fsSL https://agents.porter.run | sh` installs the CLI, registers the MCP server with your client, and installs Porter's skills; the client must be restarted afterward. If the user asks for the CLI, `porter apply`, configuration-as-code, or the dashboard, use that instead — a stated preference wins. Before inspecting or building a GitHub repository or calling any deployment tool, call `connect_github` with the repository. Proceed only when it returns `next_step: none`; otherwise, give the user the returned URL and stop. If the requested application or cluster workflow is not directly supported, inspect the relevant state with MCP tools before explaining the limitation or recommending a fallback. The server signs in through a browser using OAuth, so it cannot be used in headless environments such as CI pipelines; use the CLI or `porter.yaml` there.

# Networking

> Restrict access to your cluster's Kubernetes API, connect over VPN, and configure outbound traffic for your AWS, GCP, and Azure Porter clusters

The **Networking** tab holds the settings that control how traffic reaches and leaves your cluster. To open it, click **Infrastructure** in the left sidebar, select your cluster, and click **Networking**.

The sections appear in the same order on every cloud: cluster network, control plane access, VPN, and then the sections specific to your cloud provider. After you change a setting, click **Update** at the bottom of the tab to apply it.

## Cluster network

| Setting | Description |
| - | - |
| **Cluster CIDR range** | The CIDR range of the cluster's network. You set it when you create the cluster, and it cannot be changed. |

## Control plane access

Control plane access controls who can reach the cluster's Kubernetes API. When you turn on the restriction, the public endpoint only accepts traffic from Porter's [control plane IPs](https://docs.porter.run/security-and-compliance/porter-ip-ranges.md) plus any CIDR ranges you add. This configuration is SOC2 / HIPAA compliant.

> [tab] AWS
>
> | Setting | Description |
> | - | - |
> | **Restrict cluster endpoint access** | Turn on **Enable private cluster access** to restrict the EKS API server's public endpoint to an IP allowlist. The private endpoint inside your VPC stays reachable from VPC-attached resources. |
> | **CIDR allowlist** | Additional CIDR ranges that can reach the public endpoint. Porter's IPs are required for cluster management and cannot be removed. |
>
> > [!NOTE]
> >
> > Porter intentionally does **not** enable EKS "private-only" endpoint mode. Private-only forces every control-plane call, including Porter's, through a VPN or VPC-peered path, which adds operational complexity and has historically caused outages for customers. Public + private with a tight IP allowlist meets the same compliance requirements and is significantly more reliable.

> [tab] GCP
>
> | Setting | Description |
> | - | - |
> | **Restrict cluster endpoint access** | Turn on **Enable IPv4 allowlist** to restrict the GKE control plane's public endpoint to an IP allowlist (master authorized networks). |
> | **CIDR allowlist** | Additional CIDR ranges that can reach the public endpoint. Porter's IPs are required for cluster management and cannot be removed. |

> [tab] Azure
>
> | Setting | Description |
> | - | - |
> | **Restrict cluster endpoint access** | Turn on **Enable IPv4 allowlist** to restrict the AKS control plane's public endpoint to an IP allowlist. Nodes reach the control plane privately inside the cluster's network. |
> | **CIDR allowlist** | Additional CIDR ranges that can reach the public endpoint. Porter's IPs are required for cluster management and cannot be removed. |
>
> > [!WARNING]
> >
> > If the cluster does not already reach its control plane over a private connection, restricting access moves it to one first. This replaces every machine in the cluster once and takes about 20 to 45 minutes. Your apps restart while this happens, so [configure them for high availability](https://docs.porter.run/applications/configure/zero-downtime-deployments.md#high-availability-applications) before you turn this on.

If you turn off the restriction, Porter removes the CIDR ranges you added and the endpoint becomes publicly reachable again. To restrict it again later, you must add your CIDR ranges again.

## VPN

The **VPN** section connects the cluster to Tailscale so you can reach private services in the cluster. See the [Tailscale integration](https://docs.porter.run/security-and-compliance/tailscale.md) for setup instructions.

The VPN carries traffic for `porter kubectl` and `porter helm` commands. It does not control how the cluster's Kubernetes API endpoint is exposed. Use [control plane access](#control-plane-access) for that.

## Outbound traffic

> [!NOTE]
>
> This section is available for GCP and Azure clusters. AWS clusters send outbound traffic through a NAT gateway that Porter manages.

> [!WARNING]
>
> Changes to these settings affect the cluster's outbound connectivity. Make sure you understand the effect of a change before you apply it.

> [tab] GCP
>
> Outbound traffic from a GKE cluster leaves through Cloud NAT.
>
> | Setting | Description | Default |
> | - | - | - |
> | **Egress NAT IPs Count** | Number of egress NAT IPs. You can only increase this value after it is applied. | 1 |
> | **Min Ports per VM** | Minimum number of ports allocated to each VM. | 64 |
> | **Endpoint Independent Mapping** | Recommended for most use cases. Affects Cloud NAT behavior. | On |
> | **Dynamic Port Allocation** | Lets GKE allocate more ports to VMs that need them. To turn this on, turn off **Endpoint Independent Mapping** first. | Off |
>
> The tab shows how many nodes your NAT IPs and ports can cover. If your node groups can scale past that number, nodes past the limit lose all outbound internet access, and the tab shows how many egress NAT IPs you need. Nodes in a node group with [**Use public IP addresses**](https://docs.porter.run/clusters/node-groups.md#public-node-groups) turned on send traffic from their own IPs and do not use Cloud NAT.
>
> To find the cluster's egress IPs, see [Static egress IPs](https://docs.porter.run/security-and-compliance/static-egress-ip.md).

> [tab] Azure
>
> Azure applies changes to these settings the next time it reconciles the cluster.
>
> | Setting | Description |
> | - | - |
> | **Outbound route** | How outbound traffic leaves the cluster. See the options in the following table. |
> | **Outbound Ports per Node** | SNAT ports reserved for each node, in multiples of 8. Only applies when outbound traffic leaves through the load balancer. Clear the value to return to Azure's default of 1,024. |
> | **Outbound IPs** | Number of Azure-managed public IPs in the load balancer's outbound pool. Only applies when outbound traffic leaves through the load balancer. Clear the value to return to Azure's default of 1. |
>
> | Outbound route | Description |
> | - | - |
> | **NAT gateway** | Outbound traffic leaves through a zone-redundant NAT gateway with a static IP. Ports are shared across nodes as they need them, so the node count does not limit outbound connections. After a running cluster switches to the NAT gateway, you cannot switch it back. |
> | **Load balancer, NAT gateway ready** | Outbound traffic keeps leaving through the load balancer while Porter creates the NAT gateway and its static IP in the cluster's Azure resource group. Use this to allowlist the new IP before you switch to **NAT gateway**. The new IP shows under **Current egress IPs** after it is created. |
> | **Load balancer** | Outbound traffic leaves through the cluster's load balancer. Every node reserves a fixed share of ports on each outbound IP. Clusters that already use this route can keep it, but you cannot select it for a cluster that uses another route. |
>
> When outbound traffic leaves through the load balancer, each outbound IP provides 64,000 ports. The most nodes the cluster can run, including nodes added during an upgrade, is 64,000 ÷ ports per node × outbound IPs. If you change the ports per node so that the node count crosses one of Azure's default allocation boundaries, every node's allocation is halved, which can disrupt live connections.

## Environment group secrets

> [!NOTE]
>
> This section is available for Azure clusters only.

Porter stores your [environment group](https://docs.porter.run/applications/configure/environment-groups.md) secrets in an Azure Key Vault.

| Setting | Description |
| - | - |
| **Restrict Key Vault network access** | Only lets Porter and the clusters on this Azure subscription reach the Key Vault. |

> [!WARNING]
>
> Every cluster on the Azure subscription shares the Key Vault, so this setting applies to all of them. Anything else that reads the vault, such as your own tools or pipelines, loses access. You cannot turn this setting off after you save it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.