At Container Solutions, we often develop advanced Cloud Native solutions and cutting-edge technologies with our customers. There are many challenges with this work. One of them we encounter often is getting everyone on the team on the same level of understanding and engagement.

There are a lot of cases where developers are using Windows. Often times it is used as a development platform, either simply through developer preference, or due to company policy or a tooling dependency. As more frameworks and services become available on the Linux platform, such as Microsoft’s .NET Core, Linux becomes more attractive as a target environment for running and testing projects—especially with the abundance of tooling and.

In the past few weeks, I have been doing a lot of different tests and deployments on Kubernetes. Therefore, I had to create and destroy Kubernetes clusters many times (some days, even a few times an hour). I needed a fresh cluster due to specific things I was testing, so simply deleting all the pods, services, deployment, etc., to make the cluster ‘like new’ wouldn’t help.

In its Aristotle project, Google tried to define the success of effective teams. The researchers’ main finding was that what really mattered was less about who is on the team, and more about how the team worked together. Most important in teamwork was the presence of psychological safety.

When designing your microservice architecture in a Cloud Native system, setting up the Istio service mesh on your Kubernetes cluster(s) can give you more control and observability over network traffic. But, it can also help you break things, which will be the focus of this blog post.