Imperative commands are difficult to manage because they require correct execution order, are hard to script, and can become outdated.
Declarative configuration allows you to describe the desired state in a readable format like YAML, while controllers handle the implementation details.
Manually applying configurations with tools like kubectl apply can lead to configuration drift, security risks, and deploying untested changes.
GitOps is built on four principles: a declaratively expressed desired state, automated pulling of configuration, immutable version history, and continuous reconciliation.
A GitOps controller continuously compares the desired state in a Git repository with the current system state and applies changes to reconcile any differences.
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.
A live demo shows how Keptn uses custom resource definitions (CRDs) and an operator to manage projects, services, and deployments from a Git repository.
The GitOps implementation for Keptn is a work in progress, and community contributions for new ideas and code are welcome.
The speaker discusses their career path from systems administrator to cloud automation, working at Dynatrace, and how Keptn compares to tools like Argo CD.
47:42Roberth Strand
50:28Zan Markan
50:02Liviu Costea
42:29Lars Hesel Christensen & Basil Brunner
25:24Florian Trieloff
58:44Davide Imola
29:49Lian Li
24:19Johannes Haux
Jobs that call for the skills explored in this talk.
smartclip Europe GmbH
Hamburg, Germany
Atruvia AG
Berlin, Germany
iits-consulting GmbH
München, Germany
