Emissary-ingress Tutorial

In this article, you will explore some of the key features of Emissary-ingress by walking through an example workflow and exploring the Edge Policy Console.

Prerequisites

You must have Emissary-ingress installed in your Kubernetes cluster.

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 sample deployment and the Mapping CRD, which is the core resource that you will use with Emissary-ingress to manage your edge. It enables you to route requests by host and URL path from the edge of your cluster to Kubernetes services.

1. Copy the configuration below and save it to a file named quote.yaml so that you can deploy these resources to your cluster. This basic configuration creates the quote deployment and a service to expose that deployment on port 80.

2. Apply the configuration to the cluster with the command kubectl apply -f quote.yaml.

3. 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, on any host that can be used to reach Emissary-ingress, to the quote service.

4. Apply the configuration to the cluster with the command kubectl apply -f quote-backend.yaml

5. Store the Emissary-ingress LoadBalancer address to a local environment variable. You will use this variable to test accessing your pod.

6. Test the configuration by accessing the service through the Emissary-ingress load balancer.

Success, you have created your first Emissary-ingress Mapping, routing a request from your cluster's edge to a service!

Since the Mapping you just created controls how requests are routed, changing the Mapping will immediately change the routing. To see this in action, use kubectl to edit the Mapping:

1. Run kubectl edit Mapping quote-backend.

2. Change prefix: /backend/ to prefix: /quoteme/.

3. Save the file and let kubectl update your Mapping.

4. Run kubectl get Mappings --namespace ambassador. You will see the quote-backend Mapping has the updated prefix listed. Try to access the endpoint again via curl with the updated prefix.

5. Change the prefix back to /backend/ so that you can later use the Mapping with other tutorials.

Developer API Documentation

The quote service you just deployed publishes its API as an OpenAPI (formerly Swagger) document. Emissary-ingress automatically detects and publishes this documentation. This can help with internal and external developer onboarding by serving as a single point of reference for of all your microservice APIs.

1. In the Edge Policy Console, navigate to the APIs tab. You'll see the OpenAPI documentation there for the "Quote Service API." Click GET to expand out the documentation.

2. Navigate to https://<load-balancer-endpoint>/docs/ to see the publicly visible Developer Portal. Make sure you include the trailing /. This is a fully customizable portal that you can share with third parties who need information about your APIs.

Next Steps

Further explore some of the concepts you learned about in this article:

• Mapping resource: routes traffic from the edge of your cluster to a Kubernetes service
• Host resource: sets the hostname by which Emissary-ingress will be accessed and secured with TLS certificates
• Developer Portal: publishes an API catalog and OpenAPI documentation

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

Learn more about how developers use Emissary-ingress to manage edge policies.

Learn more about how site reliability engineers and operators run Emissary-ingress in production environments.

To learn how Emissary-ingress works, use cases, best practices, and more, check out the Quick Start or read the Emissary-ingress Story.

For a custom configuration, you can install Emissary-ingress manually.