envoy-consul-sds

envoy-consul-sds - Envoy Consul Service Discovery Service

[!NOTE] Segment has paused maintenance on this project, but may return it to an active status in the future. Issues and pull requests from external contributors are not being considered, although internal contributions may appear from time to time. The project remains available under its open source license for anyone to use.

This tutorial is based on Kelsey Hightower's kubernetes-envoy-sds tutorial but using Consul and Nomad.

envoy-consul-sds service implements the Envoy SDS API on top of Consul Health Endpoint API. envoy-consul-sds service returns a list of healthy endpoints for Envoy to use as upstream backends for a cluster. Each Consul service can be referenced in the Envoy config file by its DNS name.

NOTE: This project uses Envoy API v1. It doesn't use Envoy xDS for configuration. Please read Envoy API v2 for more information.

Goal

In this tutorial we will run Nginx on Nomad and register it in Consul. Then we will use Envoy to access Nginx using Consul DNS interface.

The idea is to explore ways Envoy can integrate with applications running on Nomad using Consul.

Tutorial

• Bootstrap the Nomad Infrastructure on Google Compute Engine
• Deploy Envoy Consul Service Discovery Service
• Deploy Envoy System Job
• Deploy Nginx Service
• Clean up