Kong Service Mesh 101, 15 Dec 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: How to Use Istio Ingress Gateway

Description

In this video, @ViktorGamov explains how @Istio Ingress Gateway works and demos how to use it.

▬▬▬▬▬▬ TIMECODES ▬▬▬▬▬▬

0:00 Cold Open
0:22 Intro
0:33 What Is Ingress?
1:48 Demo: Istio Ingress Gateway
2:03 Install Istio
2:45 Deploy Quotes Services
3:50 Enable Istio Ingress Gateway
5:25 Enable Virtual Services
7:30 About a New Gateway Spec

▬▬▬▬▬▬ LINKS ▬▬▬▬▬▬
- Demo: https://github.com/Kong/demo-scene/tree/main/kong-builders/12-01-2021
- Kong Builders: https://youtu.be/l5YdWrLlpDA
- Gateway spec https://github.com/Kong/kubernetes-ingress-controller/blob/main/keps/0002-kong-gateway-api.md
- Follow Kong's progress implementing Gateway spec https://github.com/Kong/kubernetes-ingress-controller/milestone/21

▬▬▬▬▬▬ CONTACTS ▬▬▬▬▬▬

🐦 https://gamov.dev/twitter
📧 https://gamov.dev/telegram
🔴 https://gamov.dev/youtube

▬▬▬▬▬▬ COMMUNITY ▬▬▬▬▬▬

⭐ https://github.com/Kong/kong
🐦 https://twitter.com/thekonginc
🌎 https://konghq.com/community/
🍻 https://www.meetup.com/pro/kong
❓ ️https://discuss.konghq.com/
💯 https://konghq.com/kong-champions/

#Istio #IstioIngress #IstioGateway #ServiceMesh #APIGateway #IngressController #Kubernetes

A

Hi, I'm victor graham of developer, vacation with conch, and today I'm standing in front of tham's barrier, which is sort of gateway to talk to you about istio ingress gateway and how you can use it to provide external access to your applications that runs inside istio mesh. Let's get to.

A

Ingress usually refers as something that allows your traffic into your cluster, and many of us already use kubernetes ingress in order to provide access to your applications. However, standard ingress controller doesn't allow you to do some of the complex things like advanced traffic routing, and it's only designed to be used with based protocol and imagine if you want to get access to services like apache kafka, for example that runs and serves clients using tcp. You want to be able to do this with standard ingress. Think about the standard regress as your in-store brand.

A

It does the job, but it's not perfect. So that's why, in the previous videos, I show you how you can use the qual and kingras controller to provide external access to your application today, we're going to be use, gateway, object to open port 80 and provide access to our application to the host called proxy.me, and the next thing we will enable virtual host that provide the routing from this ingress to our service that runs inside microbenetics cluster.

A

So let me show you how we can do this, and for this we will switch to my computer in this quick demonstration. I will show you how you can use istio and istio ingress gateway to expose your services to outside world. I have my cluster of kubernetes deployed in google cloud platform, it's five nodes and I'm using this command to install istio into this cluster.

A

First, we will download istio archive extract easter control, command, save it locally and use istio control precheck to check if our cluster ready to for istio and we use istio ctl installed to install istio and gateway. You also might notice that I'm using a set profile default in this case, istio control command, will install ec operator and istio ingress gateway to my kubernetes cluster.

A

So now I have a two parts, one istio operator in another word: istio, ingress gateway next thing: we're gonna, install two applications: one's gonna be my back to future, quote application that you probably seen previously and another one is quote service or fact service that generates random facts about chuck norris. It has deployment and has service it's just a simple web service that will be spinning up some random quote from back to future or fact about chuck norris. Let's deploy those.

A

We're creating namespace kong builders, we creating a label in this namespace says: istio injection enabled allows to istio inject sidecar proxies to every part in this namespace. Let's take a look. How it looks like we do have a labeled, istio injection enabled let's take a look on our pods. My back to future pod has few more containers, one container with my application and another container with proxy same thing for chuck. Norris quote: there is a chuck noise service with my application running and there's istio proxy, which is container with envoy istio ingress gateway service.

A

It has a type of load balancer and it has external ip address. So this ip address we're going to be using to access our application or access our kubernetes cluster. So let's put this ip address into insomnia and see what kind of response we will get.

A

When I send this request, I'm getting could not connect to server, meaning that this ip address was provided. Service was created, but no one inside the cluster listens to this ap address are serves in your request. Let's fix that by applying resource named gateway, gateway, resource comes from istio, and it has a couple things that we're going to configure.

A

We configure two things, obviously name of this resource and two servers, because we want to expose two servers for chuck norris and for back to future for check notice, we're using chuck.def as a host and for back to future we're using back to future.dev as a host, and we will use this in a few seconds.

A

So, let's create this resource inside our kubernetes cluster once this was created, let's see if we had different response here, it's indeed different. We have a 404, but let's instigate headers. What we can see here so istio envoy is serving this uh response. So let's configure this to expose this application and in order to configure those in istio world, we need to create their virtual servers that will connect or map or bound the gateway to a particular host with underlying service that runs inside our cluster. So back to future is the name of the service.

A

It runs inside calling builders, namespace and svc cluster local. It is a convention how this service will be available outside of its net space. Similar thing, we need to create a virtual service for chuck norris with the chuck.dev host name.

A

So let's deploy those virtual services.

A

Those virtual services were deployed. Let's investigate what we see in the cluster, go into nem space, column builders and see virtual services. We have a virtual service back to future that points to back to future host and there's another service for dev host and also connected to this gateway. Let's switch back to insomnia and see what kind of responses we can get from here so, first time we're calling we still get 404.

A

Obviously we didn't tell how gateway needs to figure out, and the second thing that we need to add additional headers in this particular case host header that will point to particular backtofuture.dev url and now our gateway successfully routes, our request to underlying service inside kubernetes. Let's do the same for chuck norris, we add in host as a header with hostname as chunk.dev and voila. We're getting response from chuck.

A

Norris quote service based on the header gateway will able to figure out that needs to extract this host from the header and after that, a route to virtual service based on the host and virtual service will route to actual underlying service implementation.

A

At the time of this, recording kubernetes community is actively working on improving existing ingress object by creating new gateway specifications, don't be confused with this gateway sophistication. The things that we talk about this today, even though istio community also contributing to this specification.

A

We at kong also actively working to contribute to this specification and support this as soon as it will be available inside calling ingress controller. I hope you found this video useful, or at least entertaining if you do consider, subscribing and with this. My name is victor gamophone, as always have a nice day.

A