From Zero to Hero - Onboarding with GitOps

With all hands on deck, we managed it surprisingly easily not only to onboard the new colleague within a couple of weeks, we onboard a developer to our team in parallel too! Today we are a real SRE-team, which I am proud of and this wouldn’t be possible at all without the GitOps idea. Join my talk and listen to a real-world story about team play, inclusion, change, and how you can achieve the same too!

Transcript

1. Mario Kleinsasser @m4r10k From Zero to Hero Onboarding with GitOps
2. Mario Kleinsasser @m4r10k 2018 - Quicksand Of Work 2
3. Mario Kleinsasser @m4r10k The Game - Beginner Level 3
4. Mario Kleinsasser @m4r10k The Game - Expert Level 4
5. Mario Kleinsasser @m4r10k The Game - Experience 5
6. Mario Kleinsasser @m4r10k The Game - Final 6
7. Mario Kleinsasser @m4r10k Abstraction - Back Then Dependency Hell 7 http://www.thebacklog.net/2011/04/04/a-nice-picture-of-dependency-hell/
8. Mario Kleinsasser @m4r10k Abstraction - Container 8
9. Mario Kleinsasser @m4r10k Abstraction - Now 9
10. Mario Kleinsasser @m4r10k Abstraction - This is fine. 10
11. Mario Kleinsasser @m4r10k The Bottom Line I Abstraction allows us to be much more efficient in dealing with all kinds of situations. It is also true that one can be effective without understanding what is below the abstraction as long as everything behaves nicely. So one should not pooh-pooh the notation of abstraction. On the contrary, one should celebrate it since allow us to be more efficient. 11 In fact, if we never have to combine a component with anything else into a larger system, and if nothing can go wrong with the component, then it is perfectly fine to understand this component only at the level of its abstraction. Introduction to Computing Systems: From Bits & Gates to C & Beyond, 2004 By Yale N. Patt, Sanjay J. Patel
12. Mario Kleinsasser @m4r10k The Bottom Line II But if we have to combine multiple components into a larges system, we should be careful not to allow their abstractions to be the deepest level of understanding. If we don’t know the components below the level of abstractions, then we are at the mercy of them working together without our intervention. 12 If they don’t work together, and we are unable to go below the level of abstraction, we are stuck. Introduction to Computing Systems: From Bits & Gates to C & Beyond, 2004 By Yale N. Patt, Sanjay J. Patel And that is the state we should take care not to find ourselves in.
13. Mario Kleinsasser @m4r10k Organization - Old School 13
14. Mario Kleinsasser @m4r10k Organization - what are you already doing? 14 People? On-Boarding?
15. Mario Kleinsasser @m4r10k Onboarding With GitOps 15 GitOps - Operations by Pull Request. GitOps = A Social Skill
16. Mario Kleinsasser @m4r10k From Zero To Hero! 16
17. Mario Kleinsasser @m4r10k From Zero To Hero! 17
18. Mario Kleinsasser @m4r10k From Zero To Hero! 18
19. Mario Kleinsasser @m4r10k From Zero To Hero! 19
20. Mario Kleinsasser @m4r10k From Zero To Hero! 20
21. Mario Kleinsasser @m4r10k From Zero To Hero! 21 Don’t fool yourself! Don’t cheat the system! Be transparent! START IT! Automate it! This is about GitOps! In any moment of decision, the best thing you can do is the right thing, the next best thing is the wrong thing, and the worst thing you can do is nothing. Theodore Roosevelt https://en.wikipedia.org/wiki/Richard_Feynman
22. Mario Kleinsasser @m4r10k 22 Thank you! The past is behind us, the future is ahead! STOP TALKING, START DOING!
23. Mario Kleinsasser @m4r10k 23 Credits Icons made by Freepik, Good Ware, surang from www.flaticon.com