Gitless GitOps: Using OCI Registries as a Secure, Trusted Hub for Multi-Zone Replication of Signed Artifacts

Gitless GitOps: Using OCI Registries as a Secure, Trusted Hub for Multi-Zone Replication of Signed Artifacts In traditional GitOps workflows, a Git repository serves as the single source of truth for application manifests, Helm charts, and other deployment artifacts. While this model works well for many teams, it can become a bottleneck when you need to replicate container images and related artifacts across multiple geographic zones or edge locations. Frequent pull-through syndication and cross-region pulls can introduce latency, complexity, and operational overhead.