Comparing GitOps implementation notes
===

:::info
- **Location:** https://www.youtube.com/watch?v=Mf393t8y0Os&feature=youtu.be
- **Date:** May 22, 2020 1:00 PM (CET)
- **Agenda**
1. Recap how this meeting came about `3min`
> [name=Laszlo]
2. What do you want to get out of this meeting? `5min`
> [name=Round]
3. Comparing GitOps implementation notes `40mins`
4. Agreeing on next steps - if any `5 mins`

- **Participants:**
- Laszlo Fogas (Laszlo)
- Valer Orlovsky (Valer)
- Bjorn Hald Sorensen (Bjorn)
- Kasper Nissen (Kasper)
- Kris Nova (Kris)
- Jeppe Johansen (Jeppe)
- Anders
:::

### :book: Comparing GitOps implementation notes

#### Performance concerns
git in general is slow
at 40000 commits
clone, and pushing is challenging

go-git becoming a burden
shell out to git makes it faster, things are simpler with git

up to 10-45 seconds in release manager

remedy plan in release manager is to spin out artifact manager to S3

#### Plans with release manager
- Put out as reference, not as a real OSS project
- Not discouraging engagement

#### One way flow, two way flow
- Fluxctl is it used by anyone?
- flagger ambiguity of state

#### Status quo
- Seems everybody is figuring this out now. Google's product is uninspiring here
- Reinventing release engineering for Gitops
- Why not put gitops repo as storage in existing tools?

### Next steps
- preparation of spinning out bits of release manager.
- file munching is a good candidate
- also the slack interaction parts

### References
[1] Google Application Manager https://cloud.google.com/blog/products/containers-kubernetes/announcing-application-manager-for-google-kubernetes-engine
[2] Release Manager https://github.com/lunarway/release-manager/
[3] GitOps by Lunar, the author of Release Manager https://tech.lunar.app/blog/2020-03-10-gitops-operations-by-pull-request/
[4] Gimlet https://gimlet.io
[5] GitOpsDays https://www.gitopsdays.com/
[6] Config Sync + Indsutry banter https://twitter.com/resouer/status/1263579810560831488