Skip to main content
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

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 plus any CIDR ranges you add. This configuration is SOC2 / HIPAA compliant.
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.
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 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 for that.

Outbound traffic

This section is available for GCP and Azure clusters. AWS clusters send outbound traffic through a NAT gateway that Porter manages.
Changes to these settings affect the cluster’s outbound connectivity. Make sure you understand the effect of a change before you apply it.
Outbound traffic from a GKE cluster leaves through Cloud NAT.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 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.

Environment group secrets

This section is available for Azure clusters only.
Porter stores your environment group secrets in an Azure Key Vault.
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.