Emissary-ingress quick start

1. Installation

We'll start by installing Emissary-ingress 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 Emissary-ingress’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 Emissary-ingress. 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 Emissary-ingress 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 Emissary-ingress 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 Emissary-ingress load balancer:

   curl -Lk http://$EMISSARY_LB_ENDPOINT/backend/

What's next?

Explore some of the popular tutorials on Emissary-ingress:

• 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

Emissary-ingress has a comprehensive range of features to support the requirements of any edge microservice.

To learn more about how Emissary-ingress works, read the Emissary-ingress Story.