Thomas Schütz

A Practitioners Guide to GitOps - Introduction, Principles and Implementation

Stop fighting configuration drift. This guide shows how GitOps treats infrastructure as code, using a declarative state in Git for automated, reliable delivery.

A Practitioners Guide to GitOps - Introduction, Principles and Implementation
#1about 3 minutes

The limitations of imperative configuration commands

Imperative commands are difficult to manage because they require correct execution order, are hard to script, and can become outdated.

#2about 2 minutes

Shifting from imperative to declarative configuration

Declarative configuration allows you to describe the desired state in a readable format like YAML, while controllers handle the implementation details.

#3about 4 minutes

Challenges of manually applying declarative configurations

Manually applying configurations with tools like kubectl apply can lead to configuration drift, security risks, and deploying untested changes.

#4about 4 minutes

Understanding the four core principles of GitOps

GitOps is built on four principles: a declaratively expressed desired state, automated pulling of configuration, immutable version history, and continuous reconciliation.

#5about 7 minutes

How the GitOps controller pattern works

A GitOps controller continuously compares the desired state in a Git repository with the current system state and applies changes to reconcile any differences.

#6about 5 minutes

Introducing Keptn for application lifecycle management

Keptn is a CNCF sandbox project that acts as a control plane for application delivery, quality gates, and remediation, making it a candidate for a GitOps approach.

#7about 7 minutes

A practical demonstration of GitOps with Keptn

A live demo shows how Keptn uses custom resource definitions (CRDs) and an operator to manage projects, services, and deployments from a Git repository.

#8about 3 minutes

Recap and call for community contributions

The GitOps implementation for Keptn is a work in progress, and community contributions for new ideas and code are welcome.

#9about 9 minutes

Q&A on career, Dynatrace, and Keptn specifics

The speaker discusses their career path from systems administrator to cloud automation, working at Dynatrace, and how Keptn compares to tools like Argo CD.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

Related Videos

GitOps: The past, present and future47:42

GitOps: The past, present and future

Roberth Strand

Practical tips and tricks for CI/CD success50:28

Practical tips and tricks for CI/CD success

Zan Markan

Get ready for operations by pull requests50:02

Get ready for operations by pull requests

Liviu Costea

Improving Developer Happiness with GitOps42:29

Improving Developer Happiness with GitOps

Lars Hesel Christensen & Basil Brunner

Building Applications with Infrastructure as Code28:34

Building Applications with Infrastructure as Code

Talia Nassi

Integrating backups into your GitOps Pipeline25:24

Integrating backups into your GitOps Pipeline

Florian Trieloff

Git for Code Reviews24:19

Git for Code Reviews

Johannes Haux

How to GitOps your cluster with Flux58:44

How to GitOps your cluster with Flux

Davide Imola

From learning to earning

Jobs that call for the skills explored in this talk.