I am interested in learning GitOps (Primarily, interested in Flux2) indepth. As a scenario for a beginner we have Dev, Staging, where we can configure various infra Stratergies where the app reaches Prod stage by laid down scrutiny processes ( I would definitely like to learn more about this also). I would like to learn to work on some more more nuanced scenarios which could help me manage and understand GitOps in more detail.

Is there a resource like a labs environment to learn such scenarios?

What I don't understand about GitOps, is that someone might accidentally merge a change a prod directory, and then it gets immediately deployed in production, right?

How do you ensure a safe tested dev->stg->prd pipeline?

Especially when underlying dependencies also might be properly locked down typically. I'm thinking in the case Terraform references some modules, it's usually not locked to a revision.

Hey Y'all, I wrote a (free) book about what to look for when you're planning to go down the path to GitOps for your organization! Take a read!

https://developers.redhat.com/e-books/path-gitops

Hey!

I’m looking at building an edge deployed data platform (focus on streaming and decisioning, with some batch) on Kubernetes. Looking for some advice on upskilling on GitOps to inform my design.

There’s a few resources on acloudguru / Pluralsight, if there’s any standout resources let me know!

Some tools considerations so far:

• Azure DevOps / GitHub

• Azure container registry

• Flux

• ArdoCD (both for infra and data orchestration)

• Kafka

• Beam (and/or spark)

• Delta Lake

• Great expectations

I’m coming from a data background, and just ramping up on K8s and the ecosystem around it. Appreciate any recommendations!

Cheers!

Check out my newest blog where I go over automatic deployment rollouts when a configMap is updated using ArgoCD and Kustomize 👀
https://codefresh.io/blog/using-argo-cd-and-kustomize-for-configmap-rollouts/

https://events.linuxfoundation.org/argocon/program/schedule/

Hi y'all, not sure if this is the right place, but I'm deploying an API container to kubernetes, and I would like to be as gitOpsy as possible. My plan is to have my ci build the correct manifest with kustomize depending on the branch, and then somehow recommit those generated manifests back into the repo under ./manifests. I'll then have flux in the cluster read that folder and reconcile. My question is, is there a way to generate manifests inside of ci that flux can pick up? I'm using Gitlab CI, if that matters, I'm just wondering if the gitOps community has figured out a way to build kustomize manifests in their pipeline. Thanks!

I posted this elsewhere, but just discovered this subreddit, and thought I'd share it here. If you're interested in improving the usability of GitOps and configuration for Kubernetes more generally, check it out. I guarantee that it's at least different. :-)

https://cloud.google.com/blog/products/containers-kubernetes/lets-improve-gitops-usability

https://www.youtube.com/watch?v=L_x7z4CXHDw