Cluster Guides

Kubernetes Cluster Compatibility & Deployment Overview

Connect Gefyra to any Kubernetes cluster. Compatibility guides for local engines (k3d, kind, minikube, Docker Desktop, Colima) and remote clouds (EKS, GKE, AKS).

Gefyra is engineered to run against any standard Kubernetes cluster (v1.24+), whether running locally on your laptop or hosted in enterprise cloud environments.

Because Gefyra operates purely at the container network and user-space operator level, it requires no proprietary kernel modules or invasive cluster-wide service meshes (like Istio or Linkerd).


Compatibility Matrix

Local Development Clusters

PlatformDriver / RuntimeStatusKey Characteristics
k3dDocker / PodmanRecommendedBlazingly fast startup; automated port exposure via Docker bridge network.
kindDocker / PodmanFullStandard CNCF conformance engine; NodePort mapping via extraPortMappings.
minikubeDocker, Hyperkit, KVMFullClassic local cluster; requires minikube ip or minikube service for endpoint reachability.
ColimaQEMU / Lima (macOS)FullLightweight, Docker Desktop-free container runtime with native Kubernetes.
Docker DesktopVirtual MachineFullBuilt-in single-node Kubernetes; supports native Docker Desktop Extension.

Managed Cloud Kubernetes Providers

Cloud ProviderServiceStatusConnection Method
Amazon Web ServicesElastic Kubernetes Service (EKS)FullNLB (Network Load Balancer) or NodePort with Security Group opening on UDP 31820.
Google Cloud PlatformGoogle Kubernetes Engine (GKE)FullStandard or Autopilot with Cloud Firewall rule allowing UDP 31820.
SysEleven MetaKubeEuropean Managed K8sFullOpenStack / Octavia LoadBalancer endpoint.
Microsoft AzureAzure Kubernetes Service (AKS)FullAzure Public IP LoadBalancer on port 31820.
Self-Hosted / On-PremiseRKE2, kubeadm, TalosFullStandard NodePort or MetalLB BGP configuration.

Network Prerequisites: The Stowaway WireGuard Port

When Gefyra installs its operator (gefyra up or gefyra install), it deploys the Stowaway gateway component. Stowaway establishes the encrypted WireGuard link with local developer machines.

  • Protocol: UDP
  • Default Port: 31820
  • Service Type: NodePort (default for local clusters) or LoadBalancer (common for cloud providers)
# Example: Install Gefyra with LoadBalancer service type for Cloud EKS/GKE
gefyra install --service-type LoadBalancer

If your cluster sits behind a corporate firewall or cloud security group (e.g., AWS Security Group or GCP VPC Firewall), ensure that inbound UDP traffic on port 31820 is permitted to worker nodes.


Choosing the Right Cluster for Your Workflow

Solo Local Fast-Feedback

Use k3d or kind. Both spin up in seconds and allow you to test Gefyra bridges offline without an active internet connection.

Team Shared Staging

Use a shared AWS EKS or GCP GKE staging cluster. Deploy Gefyra once with an external LoadBalancer service, and issue isolated client credentials to team members.