Rethink platform engineering and developer impact in the age of AI. Tune in to our webinar on Thursday, May 22.

Kubernetes Ingress Controller

Routing traffic into your Kubernetes cluster requires modern traffic management. Edge Stack API Gateway contains a modern Kubernetes ingress controller that supports a broad range of protocols including gRPC and gRPC-Web, supports TLS termination, and provides traffic management controls for resource availability.

Edge Stack API Gateway Ingress Controller Features

Protocol support

Microservices today communicate using a wide variety of protocols. The Ambassador Edge Stack supports a broad range of protocols.

Read the Docs:

TCP →

HTTP/1.0, HTTP/1.1, HTTP/2 →

gRPC, gRPC-Web →

WebSockets →

Cross-origin resource sharing

Ambassador lets users request resources (e.g., images, fonts, videos) from domains outside the original domain.

Read the Docs:

Cross-Origin Resource Sharing (CORS) →

TLS

Provide a crucial layer of privacy and security protection for end users with HTTPS.

Read the Docs:

TLS Termination →

Kubernetes integration

Edge Stack api gateway supports the Kubernetes Ingress specification and can therefore act as a Kubernetes ingress controller. Ambassador's declarative configuration model extends the Kubernetes workflow and minimizes the learning curve for new users.

Read the Docs:

Ingress support →

RBAC support →

CRD-based configuration →

Explore more API Gateway features

Next steps

Edge Stack API Gateway delivers the scalability, security, and simplicity for some of the world's largest Kubernetes installations.