Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I can imagine a lot of people moving to OCI instead of GitOps
 help



OCI layering on top of running systems a la bootc? or OCI as the desired state storage for CM?

SRE here, OCI for storing deployment config information, most of time, Kubernetes manifest files/Helm Charts.

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.

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.

I think so, Argo CD appsets are even getting an OCI generator in the next release (3.6)

ECR just seems to work really well for most people and IAM is nice compared to Github Apps + rate limits




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: