Test yourself: Are you really following GitOps patterns?

Introduction

Whether you take pride in your GitOps strategy, or wish to validate yourself for compliance, there’s a easy and fairly simple way to check if any manual actions / modification had been made to your kubernetes environments. Today, I’ll introduce a neat little plugin and walk you through the installation process as well as demonstrate its ability.

Reminder: What is GitOps ?

GitOps is a DevOps approach in which the Git repository where your infrastructure and application configuration are stored as code serves as a single source of truth. -Credit

Get to know "blame"

Similarly to the git-blame command, which show what revision and author last modified each line of a file, there’s a new and upcoming Kubernetes plugin named kubectl-blame. This neat little plugin can tell us whether or not we are following GitOps currently, and who / what had previously tempered with our resources on kubernetes.

Taken from github, generated with agg

Getting started

In a similar manner to my previous article, named *Kubernetes — Kubectl debug*, the kubectl blame plugin can also be found in the krew plugin registry. Let’s go ahead and install it:

kubectl krew install blame

That’s it! you are all done and ready to go. All that is left is for you to tinker with it, create a new resource, such as a pod or a deployment, and “blame” it 👈

GitOps ❤

Summary

Put your team and yourself to the test! If you really are following best practices and all is deployed automatically via controllers, kubectl blame report should be clean — And if you’re not, we are watching you! 👊👊😆