Kubernetes Ingress
ngrok’s Kubernetes Ingress works differently than the anything else out there. It’s more than just a basic traffic router - it offloads traffic management, performance and security to our global network. This means you get true environment independence and built-in security, performance, high availability and more - all with the exact same native Ingress and Gateway API objects that you’re already familiar with.
How it works
Set your ngrok authentication keys and helm install the Kubernetes Operator.
Use kubectl apply with your manifest to configure policies such as authentication.
Each of your services gets a URL endpoint.
Traffic from the client is routed through the ngrok cloud to the operator and then to your service.
- No networking know-how required
- Focus on Your Code, Not the Network
- You shouldn’t have to become a networking expert to set up ingress for your k8s cluster. Unlike other controllers, when you use ngrok you don’t need to configure any low-level networking primitives like DNS, IPs, VPC routing, egress gateways and network interfaces. Just
helm installthe ngrok k8s operator and you're online.
- One manifest for any distribution, any platform, any environment
- True Environment Independence
- Eliminate toil by maintaining a single Kubernetes manifest that runs identically on EKS, GKE, OpenShift, K3s, or Minikube, at the edge, development and production environments. No need to maintain environment-specific manifests.
- Type-safe CRD config, no more error-prone annotation strings
- Modernize configuration
- ngrok Kubernetes Operator’s modern, type-safe CRD configuration offers a more structured approach enabling frictionless portability across environments. No need to struggle with string annotations.
- Gateway API ready
- Frictionless transition to Gateway API
- In addition to support for Ingress objects, ngrok already supports its successor, the Gateway API that is role-oriented and expressive. We’re ready for you when you’re ready to migrate and we’re here to make the switch effortless.
ngrok Kubernetes Ingress Controller
ngrok Kubernetes Gateway API
In this episode of our Developer Roundtable series, we highlight our updated ngrok Kubernetes Operator that now supports the Kubernetes Gateway API spec.
Batteries included
No need to install and manage cert-manager, as certificates are automatically provisioned and managed by ngrok.
Deliver your APIs hosted outside Kubernetes with just one command or one function call. Configure policies such as JWT authentication, rate limiting, and other configs the same way as Kubernetes ingress, with our flexible, idiomatic JSON and CEL-based traffic policy engine making migrating to Kubernetes a breeze.
Troubleshoot issues in real-time by getting visibility into traffic flows and other events right the dashboard. Or forward traffic logs to your favorite observability tool and audit logs of configuration changes to your SIEM.
Minimize latency for your apps and APIs by relying on ngrok’s intelligent routing that steers traffic to the nearest Point of Presence (PoP). Ensure high availability for your services with geo-aware load balancing and failover.
Your customers will enjoy a speed boost as ngrok executes traffic policies that you configure to its global network. So authentication, transformations, load balancing, and more happen as close to your customers as possible.
ngrok cloud enforces authentication and authorization, preventing unauthorized traffic from ever reaching your cluster and rogue webhooks from looping and spamming your service.
Live demos of ngrok features, and chat with the ngrok team to get your questions answered.
