GitOps Patterns team 🙂 Who wants to collaborate?

[scottrigby]

Update 2024

Please comment if you want to collaborate on compiling GitOps Patterns.

The need for official GitOps patterns has been discussed many times, but has been bikeshedded because we couldn't agree what to call it (there were some good suggestions! But ultimately each had nits that prevented us from moving forward). We've decided what to call it, we just need to create the team and begin collaborating on compiling the content.

For history, see plenty of mentions in the Historic: GitOps Working Group meetings doc (Dec 2020 – March 2024) (search for "patterns" and "blueprints").

Tasks

• Create GitOps patterns team #197 PR in TEAMS.md
• Begin collaboration with the team (schedule a repeating day/time?)

Original discussion topic

Per OpenGitOps meeting today, we decided to put a stronger effort into writing up GitOps patterns to help the community, because people definitely keep asking for this.

[christianh814]

+1 for this. Lots of great content by us individually that we can incorporate so we don't have to start from 0

[dtzar]

I am definitely interested to collaborate on this

[PrateekKumar1709]

I'm interested in contributing to this and would love to collaborate

[priyanka-ravi]

I’d love to help as well!

[schnatterer]

I've invested quite some time collection references to patterns and identifying them myself for articles and a book (published in German only, for now).
You can find the gist of it https://github.com/cloudogu/gitops-patterns.
I'd be honored if my work could be of use and am also open for contribution to this effort here, though I don't have a lot of time on my hands due to family and work 😇

[mbaykara]

+1 I'd love to contribute too!

[nishadmehendale]

+1

[carolili]

Hi, I use GitOps tools daily (not an expert though 😅) and I like documenting and writing. If that could be of value, I'd be happy to contribute!

[cwstrommer]

Interested in participating, specially when it comes to versioning and artifact promotion patterns.

[alonsomoya]

I'm in ☝

[dtzar]

One of the topics I'd like to try and establish is a standardized code/folder structure that handles the "80% use case". I believe this will help people not be as overwhelmed to all the choices and opinions and tooling could be evolved to make the E2E scenarios easier.

Relevant content:

• https://github.com/christianh814/example-kubernetes-go-repo
• https://github.com/gnunn-gitops/standards/blob/master/folders.md
• https://fluxcd.io/flux/guides/repository-structure/
• https://developers.redhat.com/articles/2022/09/07/how-set-your-gitops-directory-structure
• https://www.youtube.com/watch?v=vLNZA_2Na_s
• https://github.com/gitops-bridge-dev
• https://github.com/Azure-Samples/aks-platform-engineering
• https://github.com/microsoft/multicluster-gitops

[aholbreich]

I'm in if still possible

[jonathanagustin]

Unsure if this is still open, but I would love to participate!

[blueskyjunkie]

I'm interested.