Gateway installation

With the data plane running, the gateway is the component that answers on the hostnames the data plane declares in its chart (see Declare the hostnames a data plane serves). Installation wires the gateway into the cluster, then connects DNS and TLS so the endpoint answers over HTTPS. A generic guide covers the common path; cloud-specific variants cover GCP, Azure, and AWS particulars. On AWS the certificate is customer-supplied rather than installer-provisioned.

---

Gateway installation overview

The common installation path: deploy the gateway and wire DNS and TLS.

Gateway installation on GCP

GCP-specific steps for load balancing, DNS, and certificates.

Gateway installation on Azure

Azure-specific steps for load balancing, DNS, and certificates.

Gateway installation on EKS

Expose the data plane on EKS as a Network Load Balancer, optionally terminating TLS with an ACM certificate.

Expose the gateway on a generic cluster

Self-managed clusters (k3s, kubeadm, on-premises) through an existing Ingress controller: Service pinning, namespaces, and the NetworkPolicy rule.