Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(ADOPTION-JOURNEY.md): considerations #43

Closed
wants to merge 2 commits into from
Closed

docs(ADOPTION-JOURNEY.md): considerations #43

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cb1ddc4
docs(ADOPTION-JOURNEY.md): considerations
lloydchang Oct 26, 2021
d497e91
docs(ADOPTION-JOURNEY.md): Flux CD → Flux
lloydchang Dec 16, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions ADOPTION-JOURNEY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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 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?)