I'm looking for public repositories that package GitOps configuration as versioned OCI artifacts instead of—or alongside—using Git as the primary source of truth. Multi-cluster, multi-environment monorepos would be especially useful. Examples using either Argo CD or Flux are welcome. I'm mainly interested in seeing practical repository layouts, artifact versioning, environment promotion, and how the overall workflow operates in real deployments.
3 Answers
The main benefit is treating configuration like a releasable artifact. You can build, validate, sign, and promote an immutable bundle from development to staging and production without relying on a branch or a moving Git revision. That can simplify multi-cluster rollouts and make it easier to reproduce exactly what each cluster is running, although it adds registry and artifact-lifecycle management to the platform.
A good starting point is the Gitless GitOps material built around Flux and OCI artifacts. It walks through storing configuration in an OCI registry and having Flux consume specific versions, which should give you ideas for promotion and release workflows even if you adapt the layout to your own multi-cluster setup.
The Flux D2 architecture reference is probably the most useful deep dive here. It includes architectural diagrams and example repository structures, so it’s helpful for understanding how artifacts, environments, clusters, and promotion boundaries can fit together. The examples are especially useful if you’re trying to keep one repository manageable across several clusters.
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