Re:Incident with Pull Requests, Git Operations and Issues
by c0rruptbytes on Wednesday November 04, 2026 @10:30AM
(#50366997)
I can imagine a lot of people moving to OCI instead of GitOps
[ Parent
| on HN ]
Re:Incident with Pull Requests, Git Operations and Issues
by stryan on Wednesday November 04, 2026 @10:35AM
(#50367071)
OCI layering on top of running systems a la bootc? or OCI as the desired state storage for CM?
Re:Incident with Pull Requests, Git Operations and Issues
by stackskipton on Wednesday November 04, 2026 @11:02AM
(#50367511)
SRE here, OCI for storing deployment config information, most of time, Kubernetes manifest files/Helm Charts.
Re:Incident with Pull Requests, Git Operations and Issues
by stryan on Wednesday November 04, 2026 @11:56AM
(#50368367)
Gotcha, that's what I figured but I was still curious. I've got a side-project that was originally designed for traditional GitOps but got OCI support as a feature submission from a user. I've been seeing more usage of the OCI backend these days and originally figured it was a side-effect of the project domain (Podman Quadlets) but maybe it is an over all field shift.
Re:Incident with Pull Requests, Git Operations and Issues
by bdsa on Wednesday November 04, 2026 @12:21PM
(#50368668)
In the last couple of weeks, I've been moving a deployment stack off ArgoCD pointing at Git, and ended up settling on Flux fetching OCI artifacts from ECR. The artifacts are built and pushed by GitHub Actions. It seems like a nice way to "have GitOps" without needing GitHub to be up all the time.
Re:Incident with Pull Requests, Git Operations and Issues
by c0rruptbytes on Thursday November 05, 2026 @01:39AM
(#50375927)
I think so, Argo CD appsets are even getting an OCI generator in the next release (3.6)