Intro to Ingress Gateway A best practice for allowing traffic into your cluster is through Istio’s Ingress Gateway which positions itself at the edge of the cluster and on incoming traffic enables Istio’s features like routing, security, monitoring. During Istio’s installation, the Ingress Gateway component and a service that exposes it externally were installed into
To set up Istio you need a Kubernetes Cluster with at least 4 vCPU and 8 GB of RAM. This guide is tested with the following Kubernetes Implementations: Google Container Engine (GKE) Azure Kubernetes Service (AKS) Digital Ocean (20 days free Kubernetes link) After creating the cluster and configuring access with the Kubernetes command line
Foreword In the projects that we use Kubernetes, as the number of Services increased we started to lose observability and control. So I explored Istio, and before just jumping into it and having everything in production, I updated my sample application from the series Kubernetes and everything else and tested Istio out, and then got it
A simple, digestible and enjoyable introduction to Kubernetes Volumes, by using the already familiar Sentiment Analysis microservice application.
Problem Azure Search sounds nice and everything, but I need an Azure Search quick setup so that I can play around with it. For those new to Azure Search, read up in the official documentation, there is also a great video. Solution Azure Search enables indexing of a Database, be it SQL or NoSQL, and then enables
The last article of the series “Kubernetes and everything else”, here we tie everything together once and for all, we cover everything from code and up to the deployment in Kubernetes. And some closing words for going together through the series.
Kubernetes Deployments help us with one constant in the life of every application, and that is change. Moreover, the only applications that do not change are the ones that are already dead, and while not, new requirements will come in, more code will be shipped, it will be packaged, and deployed. And on each step
In the last article Kubernetes in Practice – Pods, we started two pods (sa-frontend and sa-frontend2) and we were left with two requirements, which will be the topic of this article: Exposing the services (running in the pods) externally, and Load balancing between them. The Kubernetes Service resource acts as the entry point to a set of
We covered how to run the Microservices in separate containers in these two articles Container-ization of the Services and Container-ization of everything else, and it was a cumbersome process, but it worked (see fig. 1.). Additionally, we mentioned that this solution is not scalable or resilient and that Kubernetes will resolve these issues. So in this article
What is Kubernetes, what are the features it has and as always explained simply. This part is a continuation of the Series “Kubernetes and everything else” that builds an microservice application up, containerizes it and then deploys it to Kubernetes. Best source to learn Kubernetes and the context it is in.
Let’s continue where we left off, creating the Images for the Java and Python Applications. And then we will verify that everything works together. Then we are ready to continue with the most important part Kubernetes.
Learn Docker basics and how to define, build and push your docker container that serves static files using the Nginx WebServer. This article is from the “Kubernetes and everything else” series and will be of prime importance to understand how Kubernetes works.