Nico Vibert is a Senior Technical Marketing Engineer at Isovalent – the company behind the open-source cloud native solution Cilium. Nico has worked in many different roles – operations and support, design and architecture, technical pre-sales – at companies such as HashiCorp, VMware and Cisco. Nico’s focus is primarily on network, cloud and automation and he loves creating content and writing books. Nico regularly speaks at events, whether on a large scale such as VMworld, Cisco Live or at smaller forums such as VMware and AWS User Groups or virtual events such as HashiCorp HashiTalks. Outside of Isovalent, Nico’s passionate about intentional diversity & inclusion initiatives and is Chief DEI Officer at the Open Technology organization OpenUK.
Cilium Gateway API – Mini Demo
[03:23] In this brief demo, we introduce a new Cilium 1.13 feature: support for Kubernetes Gateway API !
Welcome to this mini demo of Cilium Gateway API. Gateway API is a way to route traffic into your Kubernetes cluster and it’s a successor to the Ingress API. So, in this quick demo, what we’re going to do is use the Bookinfo sample application. Depending on the prefix path, we’re going to route traffic to either the product page or to the details page. The application is typically used for Istio, but obviously, we can use it in this example.
So, we’re going to start by first checking that we’ve got Gateway API enabled. It is, and then we’re going to deploy the Bookinfo application. A number of microservices are deployed, the Pods are up and running, so now we just need to route traffic into them.
Now let’s use the Gateway API resources to route the traffic into our application. So, we’ve got the Cilium Gateway API, and we’re using HTTP Routes CRDs to route traffic depending on the paths. For “/details,” we’ll send it to the Details Service of our port 9080, and then for a specific header of “magic equals Foo,” we’ll send it to the product page over port 9080.
So, let’s go and deploy the Cilium Gateway API first. Here we go. It usually just takes a couple of seconds to deployed. The Loadbalancer service has been automatically deployed, and you can see the IP address is 172.18.255.201. We’re going to save that IP address, and now we’re going to do a curl, and you can see the curl is successful. So, we’ve been able to get the details of a specific book.
And now, let’s look with Termshark. We can see that an HTTP query over port 80 has been translated over to port 9080, and a query with the headers that we specified before (“magic” was “Foo” and with a query of “great=example”) is also successful. Again, if you look at Termshark, we can see that the traffic was successfully routed over and was sent over to port 9080.
And that’s it! So, that was just a really quick demo of the Cilium Gateway API feature. If you’d like to know more, you can go and try it yourself using the Cilium Gateway API lab on isovalent.com. Thanks for watching.