ngrok, the API-first ingress-as-a-service platform, is launching the ngrok Ingress Controller for Kubernetes, enabling developers to leverage ngrok’s ease-of-use and security to produce ingress for production workloads operating on Kubernetes clusters.
Kubernetes workloads are notorious for requiring specific, and often complex, infrastructure and tooling to support it; seeking to close the gap between Kubernetes workloads and optimized operation, ngrok’s Ingress Controller for Kubernetes unites Kubernetes workloads with ngrok’s streamlined, highly-performant ingress platform.
“Other ingress controllers require operators to perform complex networking setup bespoke to each underlying environment,” said Alan Shreve, founder and CEO of ngrok. “ngrok, by contrast, delivers a plug-and-play experience to any Kubernetes cluster. It eliminates operational burden by leveraging ngrok's global network to deliver ingress without requiring you to configure the underlying environment's hardware and network.”
Powered by Ingress Controller’s unique architecture, the solution protects and expedites workloads within Kubernetes clusters through ingress production. ngrok Ingress Controller drives ingestion and middleware behaviors—such as OAuth, mutual TLS, and load balancing to ngrok’s global network—to prevent unauthenticated user access and network threats before they reach origin networks, according to the company.
“The ngrok Kubernetes Ingress Controller provides a great alternative to the Consul API Gateway for providing ingress traffic into Consul service mesh, whether the mesh is powered by HashiCorp Cloud Platform or by servers on self-managed infrastructure,” said David Yu, senior product manager at HashiCorp. “We’re excited to see the capabilities they bring to Consul and the ecosystem as a whole.”
To learn more about ngrok Ingress Controller for Kubernetes, please visit https://ngrok.com/.