Thanos is gaining lot of popularity in the prometheus community. It’s easy to do deploy prometheus using operator but while running prometheus in HA setup, we have limited options like running two instances of prometheus which are scraping the same targets. Since they are scraping the same targets hence they are generating the same alert twice. Other issues with prometheus was with downsampling and long term storage retention. To overcome these challenges, thanos is introduced.

In previous post introduction was provided to istio telemetry part. In this article, I am using the examples [1] from official documentation to dig more on logging and metric part of istio-mixer.

In this article, I am showing the steps to integrate the existing EFK stack with Istio for logging.

Istio Mixer component is responsible for telemetry. While generating the HTTP GET request for helloworld service from curl POD I kept an eye on mixer logs, I found number of logs reported.

Citadel is the component of Istio repsonsible for for key and certificate management. In this article, I am showing basic information about the usage of policy and destinationrule in context of TLS.

In the previous post, I have run through the basic exercise with minimal installation of Istio. In this article, I am going to share information on architecture of Istio.

If you are working in kubernetes world then you should have heard the word Istio, if not Istio then at-least service mesh. I heard about istio couple of times, I tried it sometime back in my lab environment but didn’t get the chance to look into it more closely. Today, I found sometime to dig deep into it and try out some example. In this post, I am sharing the basic exercise which I completed on my minikube setup. In future posts, we will dig more on istio topic.

I was trying to make consul sync working on minikube setup for a long time. I found this link for deployment of consul on minikube. I have followed the exact steps from the link only change which I made was values.yaml file.

This article is bit different than the previous articles, in this case we have deployed the consul cluster on docker-machine, you may refer this blog post for it.

From the previous article, we already have consul setup consists of 3 consul servers and 1 consul agent running on minikube kubernetes. I thought of adding the external consul client to the consul setup. For that I created one docker-machine and start consul in agent mode on it but it didn’t join with consul k8 setup.