From 5e84ad19c6a0c06a92b0c7d71261c4222a2b27d1 Mon Sep 17 00:00:00 2001 From: Tom Murphy Date: Tue, 9 Feb 2021 09:18:57 +1100 Subject: [PATCH] Added doc note FW rule for GKE private clusters --- .../v2.x/en/installation/requirements/ports/_index.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/rancher/v2.x/en/installation/requirements/ports/_index.md b/content/rancher/v2.x/en/installation/requirements/ports/_index.md index 10d08d6349a..e6966253d21 100644 --- a/content/rancher/v2.x/en/installation/requirements/ports/_index.md +++ b/content/rancher/v2.x/en/installation/requirements/ports/_index.md @@ -168,6 +168,14 @@ The following tables break down the port requirements for Rancher nodes, for inb {{% /accordion %}} +### Ports for Rancher Server in GCP GKE + +When deploying Rancher into a Google Kubernetes Engine [private cluster](https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters), the nodes where Rancher runs must be accessible from the control plane: + +| Protocol | Port | Source | Description | +|-----|-----|----------------|---| +| TCP | 9443 | The GKE master `/28` range | Rancher webhooks | + # Downstream Kubernetes Cluster Nodes Downstream Kubernetes clusters run your apps and services. This section describes what ports need to be opened on the nodes in downstream clusters so that Rancher can communicate with them.