Canary and Dark Release Using an Istio Service Mesh on Kubernetes

Istio Service Mesh on Kubernetes (k8s) cluster brings in quite a few architectural patterns off the shelf. In this article , I want to show you how we can quickly implement Canary Releases and Dark Releases using Istio service mesh

As a developer, it is imperative that you are able to install a k8s cluster and try out. With the latest release of Kops, it is pretty straightforward to fire up a new K8s cluster on AWS. I have created a series of steps and commands in my repo here - Kubernetes-AWS-Istio, which you can follow to create it on AWS. I have also kept istio installation file that you can apply using kubectl to start Istio pods on cluster. You do not need to install Istioctl to install Istio if you use the file provided by me. The Istio installation file on my repo is a standard K8s YAML.

Kops vs. EKS: A Comparison Guide

It is fairly safe to say that Kubernetes is now the go-to solution when it comes to deploying containerized apps. EKS simplifies the creation of a secure and capable K8s environment on the Amazon Web Services platform and makes deploying clusters there that much easier. We’ve covered EKS on several occasions previously here and here to read more. As discussed previously, EKS does have its limitations, but the service is very easy to use, even when you are not a server administrator.

However, EKS and similar services are not the only way you can set up a production-grade K8s environment. Kops, or Kubernetes Operations, has been around for a while, offering CLI tools that make creating and managing Kubernetes installations easy. Kops is designed for those who want complete control over their Kubernetes environment but without the usual headaches.