From the course: Automating Kubernetes with GitOps

Unlock this course with a free trial

Join today to access over 24,900 courses taught by industry experts.

GitOps observability

GitOps observability - Kubernetes Tutorial

From the course: Automating Kubernetes with GitOps

Start my 1-month free trial Buy for my team

GitOps observability

“

- All right, last part in observability that we need to talk about is GitOps observability. So in GitOps, specific parameters should be observed, and these are to start with the performance of the GitOps operator itself, the latency, the amount of traffic, the saturation, and the errors. Also, in general, you want to observe application sync status, configuration drift, as well as Git changes. So how do we do that? Well, let's talk about application sync status. In a GitOps environment, the running applications should be in sync with the application sources in Git. That's the essential work of the GitOps operator and you can use different tools to verify the sync status. There is git diff, which will show you details about uncommitted changes to the Git repository. So that's definitely playing at the Git level only. And there's kubectl diff, which will verify if the content of manifest files meets the current state of the Kubernetes application. Then there is configuration drift. So…

Contents