- Features and Benefits
- Using Ambassador Edge Stack in Your Organization
- Ambassador Edge Stack vs. Other Software
- Certified Builds
- Ambassador Edge Stack Architecture
- Ambassador Edge Stack Deployment Architecture
- Continuous Delivery, Declarative Config, and GitOps
- Microservices API Gateways
- Rate Limiting Concepts
- Self-Service Routing and Deployment Control
- Safely Testing in Production
- OAuth & OIDC Overview
- Why Ambassador Edge Stack Uses Envoy Proxy (External Link)
- Configuring Ambassador Edge Stack
- Mapping Services
- Canary Releases
- Circuit Breakers
- Cross Origin Resource Sharing
- Header-based routing
- Host Header
- Host CRD
- Prefix Regex
- Rate Limits
- Remove Request Headers
- Remove Response Headers
- Add Request Headers
- Add Response Headers
- Automatic Retries
- Routing TCP Connections
- Traffic Shadowing
- Developer Portal
- Filter Reference
- Statistics and Monitoring
Knative is a popular Kubernetes-based platform for managing serverless workloads with two main components:
- Eventing: Management and delivery of events
- Serving: Request-driven compute that can scale to zero
We will be focusing on Knative Serving, which builds on Kubernetes to support deploying and serving of serverless applications and functions.
Ambassador can watch for changes in Knative configuration in your Kubernetes cluster and set up routing accordingly.
Note: Knative was originally built with Istio handling cluster networking. This integration lets us replace Istio with Ambassador, which will dramatically reduce the operational overhead of running Knative.
- Knative now requires Kubernetes v1.14, as well as a compatible kubectl
kubectlv1.10 is also required. This guide assumes that you’ve already created a Kubernetes cluster that you’re comfortable installing alpha software on.
Install the latest Knative Serving with Ambassador to handle traffic to your serverless applications by following the instructions here.
See the Knative documentation for more information.