- The Mapping Object
- Automatic Retries
- Canary Releases
- Circuit Breakers
- Cross-Origin Resource Sharing
- Method-based Routing
- Prefix Regex
- Traffic Shadowing
- Developer Portal
- Edge Policy Console
- The Ambassador Module
- Gzip Compression
- Host CRD, ACME Support, and External Load Balancer Configuration
- Ingress Controller
- Troubleshooting Ambassador
- Custom Filters
- Knative Serverless Framework
- Prometheus monitoring
- Frequently Asked Questions
The Ambassador Edge Stack can be installed in a variety of ways:
Kubernetes via YAML is the most common approach to install with our default, customizable manifest. The Ambassador Edge Stack is designed to run in Kubernetes for production. If you're new to Kubernetes and/or Ambassador, we recommend using this method.
See the Quick Start installation guide to get started in just a few minutes.
You can also install the Ambassador Edge Stack using Helm, Docker, Bare Metal, the Operator, or installing manually.
|Kubernetes Bare Metal||AES Operator||YAML Install|
|Helm is a package manager for Kubernetes. The Ambassador Edge Stack comes pre-packaged as a Helm chart. Install via Helm.||The Docker install will let you try the Ambassador Edge Stack locally in seconds, but is not supported for production. Try with Docker.||Bare Metal can expose the Ambassador Edge Stack if you don't have a load balancer in place. Install on Bare Metal.||The Ambassador Edge Stack Operator automates install and updates, among other actions. Install with the Operator||If you want to configure specific parameters of your installation, use the YAML installation method.|
Looking for just the API Gateway? Install the Ambassador API Gateway.
If you already have the Ambassador Edge Stack, here are a few different ways you can upgrade your instance: