Networking
The platform uses specific network ports to enable communication between Kubernetes clusters, the platform API, and external services. These ports support API requests, webhook execution, and DNS resolution.
If these ports are blocked by firewall rules, some platform features such as role-based access control (RBAC) enforcement or webhook validation might fail. Ensure these ports are open to prevent connectivity issues.
Required open portsβ
Connect Kubernetes to the platformβ
Kubernetes must connect to the platformβs API extensions and webhooks to process requests, enforce policies, and perform management operations related to the platform. The following ports must be open to allow for communication:
| Port | Description | Purpose |
|---|---|---|
8080 | Legacy metrics endpoint | Enables scraping metrics when serviceMonitor.enabled=true |
8443 | API service extension (v1.cluster.loft.sh) | Enables Kubernetes API integration with the platform |
9443 | Webhook validation (loft webhook) | Validates requests and enforces policies |
9444 | Management API (v1.management.loft.sh) | Handles platform-wide administration and cluster management |
In private GKE clusters, Kubernetes control plane and worker nodes might reside in separate subnetworks. You might need to explicitly allow traffic on these ports using a firewall rule.
Connect vCluster to the platformβ
When a cluster and the platform are in the same control plane cluster, the platform exposes an in-cluster Service that targets port 10443 on the platform pods.
Clusters in the same control plane cluster talk to the platform through that ClusterIP Service. Allow egress from the cluster's namespace to platform pods on TCP port 10443.
When a cluster and the platform are in different control plane clusters, the cluster uses the loftHost value (your platform's load balancer or Ingress DNS) to establish a Tailscale-backed tunnel for API traffic.
Allow egress traffic from the cluster's pods to the loftHost domain. If the platform agent participates in the handshake in your setup, also allow egress from the agent to loftHost.
Enable DNS resolution in clustersβ
vCluster runs a CoreDNS component inside each cluster to handle internal DNS queries. To avoid conflicts with the control plane cluster's DNS, CoreDNS in vCluster listens on port 1053 instead of the default port 53.
If this port is blocked, DNS queries from cluster pods might not work, especially when the querying pod and the CoreDNS pod are on different nodes. This issue commonly affects EKS clusters created with Terraform, which set up separate security groups for the control plane and worker nodes. By default, the node security group does not allow inbound traffic on port 1053.
To enable proper DNS resolution within clusters, allow inbound traffic on port 1053 between nodes.
| Port | Description | Purpose |
|---|---|---|
1053 | CoreDNS for vCluster | Enables internal DNS resolution across nodes in clusters |
If you're using EKS with Terraform, check the default node security group and manually allow inbound traffic on TCP and UDP port 1053. This ensures DNS queries between pods and CoreDNS can succeed even when scheduled on different nodes.
Firewall rules configurationβ
If your firewall blocks ports, you must create rules to allow required traffic. You can configure access using network security settings such as VPC firewall rules or AWS Security Groups.
Allow Kubernetes to connect to the platformβ
Run the following command to allow Kubernetes to communicate with the platform:
gcloud compute firewall-rules create allow-k8s-api-to-vcluster-platform \
--allow tcp:8080,tcp:8443,tcp:9443,tcp:9444 \
--source-ranges=<KUBERNETES_API_IP_RANGE> \
--target-tags=vcluster-platform
- Replace
<KUBERNETES_API_IP_RANGE>with the actual IP range of the Kubernetes API server.
In private GKE clusters, the Kubernetes control plane and nodes are not in the same subnetwork. Without this rule, Kubernetes cannot communicate with platform components.
Verify firewall rulesβ
After setting up firewall rules, test the connection from the Kubernetes API server's network to a platform pod on each required port. For example, for port 9443:
nc -zv <PLATFORM_POD_IP> 9443
If the port is open, the output looks like the following:
Connection to <PLATFORM_POD_IP> 9443 port [tcp/*] succeeded!