docs(ADOPTION-JOURNEY.md): considerations

Co-authored-by: Mike Calizo <[email protected]> Co-authored-by: Nem Stefanovic <[email protected]> Co-authored-by: Simon Delord <[email protected]> Co-authored-by: Wayne Dovey <[email protected]> Co-authored-by: djoo <[email protected]> Signed-off-by: lloydchang <[email protected]>
open-gitops · Oct 26, 2021 · cb1ddc4 · cb1ddc4
1 parent 570b28f
commit cb1ddc4
Showing 1 changed file with 14 additions and 0 deletions.
diff --git a/ADOPTION-JOURNEY.md b/ADOPTION-JOURNEY.md
@@ -0,0 +1,14 @@
+# Adoption Journey {{version}}
+
+What are the considerations before adopting GitOps? (to avoid disaster or bad taste)
+
+1. Start small
+2. Consider the right skill set at the start of the journey (i.e. Basic understanding of software development lifecycle (SDLC) because GitOps is a software driven target operating model (TOM))
+3. Container orchestration (e.g. Kubernetes (K8s)) has to be on the roadmap - how do we get ready for that (i.e. Start with infrastructure, then network)
+4. Matrix view of crawl / walk / run (i.e. Independent deployability, Rapid application deployment)
+5. Enablement strategy - Git enablement, Configuration Management (e.g. Kustomize) enablement, DevSecOps enablement
+6. Standardisation (i.e. Choose a standard from the options in Argo CD and Flux CD to structure your repositories)
+7. Champions / Community of Practice (CoP) - a team that can 'go first'
+8. Executive sponsor
+9. Automation maturity - Infrastructure as Code at the minimum
+10. Communication strategy (Why are we doing this, how does it fit our context, how will we manage risks?)