@errordeveloper
GitOps:
Operations by Pull-request
Slide 2
Slide 2 text
outline:
– our story
– gitops theory
– live demo
Slide 3
Slide 3 text
– our story
what do we do?
Slide 4
Slide 4 text
– our story
what we offer?
Slide 5
Slide 5 text
– our story
how I benefit?
Slide 6
Slide 6 text
– gitops theory
Slide 7
Slide 7 text
– gitops theory
• any developer can use git
• anyone can join team and ship a new app or make changes easily
• all changes can be stored, audited and validated in git
and we didn’t have to do anything very new or clever =)
Slide 8
Slide 8 text
– gitops theory
• config is code & everything is config (‘declarative infra’)
• code (& config!) must be version controlled
• CD tools that do not record changes in git are harmful
Slide 9
Slide 9 text
– gitops theory
Continuous Delivery/Deployment
Image
Repo
Orchestrator
Deploy
Synchronizer
Config change
Manual deployment
Git
Code change
Git
Update Hint
Continuous Integration
Deploy
Automator
CI
Pipeline
Slide 10
Slide 10 text
– kube pitfalls
Slide 11
Slide 11 text
I just go and kubectl
all the things; great!
Slide 12
Slide 12 text
Maybe, I should get
my CI to do kubectl!
Slide 13
Slide 13 text
Now, I need some
templates…
Slide 14
Slide 14 text
Now, I need some
templates…
$ man sed
Slide 15
Slide 15 text
Helm is a thing.
I should use it.
Slide 16
Slide 16 text
– more gitops
Slide 17
Slide 17 text
– more gitops
•everything is checked in git
•easy to deploy the entire stack locally
•easy to fork a cluster
•easy to detect ad-hoc changes, alert/undo
Slide 18
Slide 18 text
– more gitops
•git is the source of truth
•review process is the same as for code
•infra changes go through review process
•you are free to use whatever tools