I'm looking for public repositories that package the GitOps configuration itself as versioned OCI artifacts rather than treating a Git repository as the only source of truth. The most useful examples would show multi-cluster and multi-environment deployments, ideally using a monorepo, along with repository structure, artifact versioning, promotion between environments, and how the workflow operates in practice. Examples using either Flux or Argo CD are welcome.
3 Answers
The Gitless GitOps material from iximiuz Labs is a good place to start. It demonstrates storing and consuming configuration through OCI artifacts with Flux, and the related Flux documentation explains the mechanics more directly. It may not cover every multi-environment promotion pattern, but it should provide useful ideas for structuring the experiment.
The main benefit is that OCI registries can act as a versioned, immutable distribution point for deployment configuration. That can simplify promotion, give each environment an explicit artifact version, and avoid requiring the reconciler to read directly from a Git host. The trade-off is that teams need to design their own source structure, release process, and environment-promotion conventions carefully.
Flux’s D2 Architecture Reference is probably the strongest architectural example mentioned here. It includes a detailed document and example repositories that show how the pieces fit together, so it’s useful for studying artifact layout and reconciliation flows rather than just reading a brief getting-started guide.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures