AI Weekly Newsletter, Kala. Curated AI news, tutorials, tools and more - Join thousands of other readers, 100% free, unsubscribe anytime.

On a chilly November morning in 2020, it's GitOps Days, and we heard Alexis Richardson via Video Conferencing speak. Git allowed us to do Cloud-native development. It gave us the tooling for a distributed source control, continuous integration, container image distribution, and others.

It's a sunny May afternoon in a Barcelona KubeCon. Liz Rice is on the stage discussing penetration testing in Kubernetes.

It's 2018 in Kubecon North America, a loud echo in the microphone, and then Ben Sigelman is on the stage.

There is conventional wisdom that observing microservice is hard. Google and Facebook solved this problem, right? They solved it in a way that allowed Observability to scale to multiple orders of magnitude to suit their use cases.

The prevailing assumption that we needed to sacrifice features in order to scale is wrong. In other words, the notion that people need to solve scalability problems as a tradeoff for having a powerful set of features is incorrect.

People assume that you need these three pillars of Observability: metrics, logging, and tracing, and all of a sudden, everything is solved. However, more often than not, this is not the case.

Today we are going to discuss Observability and why this is a critical day-2 operation in Kubernetes. Next, we will discuss the problems with Observability and leverage its three pillars to dive deep into some concepts like service level objectives, service level indicators, and finally, service level agreements.

In November 2017, The Register published an article, 'Lambda and serverless is one of the worst forms of proprietary lock-in we've ever seen in the history of humanity.'

It is the year 2017 Kelsey Hightower is on the KubeCon stage. The sound of the microphone starts echoing... Raise your hands if you think installing kubernetes is easy. This is how a well known Kubernetes advocate started his presentation.

It is 2016, Karl Isenberg is on the center stage, "Container Orchestration Wars," he said.

The stage was set for the orchestration race.

Armed to the teeth, the warriors at this time were DCOS Mesos, Kubernetes, Nomad, and Docker Swarm, among others.

We live in a world built by our collective ingenuity and imagination. We see further and more than our predecessors, not because of keener vision or greater heights but because we are standing on the shoulders of giants that came before us.
The Japanese word "sensei" literally means the person who came before.

Cloud computing made building infrastructure as code easier, it allowed us to automate most of the manual tasks and enabled collaboration between the teams building the application and the teams maintaining the infrastructure.The automation made reviewing, testing and bug hunting happens at an earli..

We made a march towards continuous development, and we changed the way we develop, build, deploy, secure, and monitor software. Do you think you missed this march? The good news is that it's actually happening continuously. Join us! We're part of it too. We observe it, we document it, and we tell it.