Docs
Edge Stack2.0Ambassador Edge Stack quick start
Ambassador Edge Stack quick start
1. Installation
We'll start by installing Ambassador Edge Stack into your cluster.
We recommend using Helm but there are other options below to choose from.
2. Routing traffic from the edge
Ambassador Edge Stack uses Kubernetes Custom Resource Definitions (CRDs) to declaratively define its desired state. The workflow you are going to build uses a simple demo app, a Listener CRD, and a Mapping CRD. The Listener CRD tells Ambassador Edge Stack what port to listen on, and the Mapping CRD tells Ambassador Edge Stack how to route incoming requests by host and URL path from the edge of your cluster to Kubernetes services.
- Start by creating a
Listenerresource for HTTP on port 8080:
Apply the YAML for the “Quote of the Moment" service.
Copy the configuration below and save it to a file called
quote-backend.yamlso that you can create a Mapping on your cluster. This Mapping tells Ambassador Edge Stack to route all traffic inbound to the/backend/path to thequoteService.Apply the configuration to the cluster:
With our Mapping created, now we need to access it!
Store the Ambassador Edge Stack load balancer IP address to a local environment variable. You will use this variable to test access to your service.
Test the configuration by accessing the service through the Ambassador Edge Stack load balancer:
What's next?
Explore some of the popular tutorials on Ambassador Edge Stack:
- Intro to Mappings: declaratively routes traffic from the edge of your cluster to a Kubernetes service
- Host resource: configure a hostname and TLS options for your ingress.
- Rate Limiting: create policies to control sustained traffic loads
Ambassador Edge Stack has a comprehensive range of features to support the requirements of any edge microservice.
To learn more about how Ambassador Edge Stack works, read the Ambassador Edge Stack Story.