Exposing Service Mesh applications with Consul Ingress Gateways

In this video I show you how to configure HashiCorp Consul's Ingress Gateways.

Ingress Gateways are a new feature of Consul in version 1.8 and allow you to expose services running in Consul Service Mesh to non service mesh users or applications. In this demo we see how to configure host header redirect from a public TLS endpoint to two upstream applications.

Everything raised from adverts in this, and all content on the channel is donated to charity. This month I will be donating everything to charities related to #BlackLivesMatter.

Running the demo (Mac and Linux):

Source Code:

Ingress Gateways:

Shipyard Install:

Consul Service Mesh Deep Dive:

Chapters:
0:00 Intro
1:37 Running the demo
3:24 Consul configuration
5:37 Ingress Gateway setup
7:25 Configuring Ingress Gateway to expose services
12:48 Examining Envoy configuration generated by Consul
14:55 Fetching the root CA for the public TLS endpoint
15:40 Testing the setup

[FernandoMiguel]

Nic you mentioned an alternative just in the end but I couldnt hear it. Which one is it?

[nicoflaig]

In our current consul cluster we use nginx together with envoy and consul in the same docker image to route traffic into our cluster. What do you think about that approach and whats the current best practice?