4 min • read

Edge Stack Quick Start


1. Installation

We'll start by installing Edge Stack into your cluster.

We recommend using Helm but there are other options below to choose from.

2. Routing Traffic from the Edge

Like any other Kubernetes object, Custom Resource Definitions (CRDs) are used to declaratively define Edge Stack’s desired state. The workflow you are going to build uses a simple demo app and the Mapping CRD, which is the core resource that you will use with Edge Stack. It lets you route requests by host and URL path from the edge of your cluster to Kubernetes services.

  1. First, apply the YAML for the “Quote of the Moment" service.

  2. Copy the configuration below and save it to a file called quote-backend.yaml so that you can create a Mapping on your cluster. This Mapping tells Edge Stack to route all traffic inbound to the /backend/ path to the quote Service.

  3. Apply the configuration to the cluster:

    With our Mapping created, now we need to access it!

  4. Store the Edge Stack load balancer IP address to a local environment variable. You will use this variable to test accessing your service.

  5. Test the configuration by accessing the service through the Ambassador load balancer:

    curl -Lk https://$AMBASSADOR_LB_ENDPOINT/backend/

3. Connect your Cluster to Ambassador Cloud

The Service Catalog is a web-based interface that lists all of your cluster's Services. You can view, add, and update metadata associated with each Service, such as the owner, version control repository, and associated Slack channel.

  1. Log in to Ambassador Cloud with your GitHub account.

  2. At the top, click Add Services then click Connection Instructions in the Edge Stack installation section.

  3. Follow the prompts to name the cluster and click Generate a Cloud Token.

  4. Follow the prompts to install the cloud token into your cluster.

  5. When the token installation completes, refresh the Service Catalog page.

What's Next?

Explore some of the popular tutorials on 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

The Ambassador Edge Stack has a comprehensive range of features to support the requirements of any edge microservice.

To learn more about how Edge Stack works, read the Ambassador Story.