Join us for live office hours! Next WednesdayNext Wed

#gitops - September 2023

gitopsArchived

2 messages

Discuss continuous delivery of infrastructure
Archive: https://archive.sweetops.com/gitops/

Aug 2023

September 2023

Oct 2023

Tim Birkettover 2 years ago(edited)

GitOps... I'm still struggling to find any real reason to move from change-driven CI/CD with helmfile to something like ArgoCD or Flux.

With the CI/CD "push" approach, I can see deployment issues in a familiar interface, and a single pipeline view through to deployment. I can deploy through environments with visible e2e or smoke tests.

In the GitOps "pull" model I have yet another interface and bunch of logs to sift through. I have to workaround some things like CRDs.

IMO, most GitOps repos end up a bit of a mess over time 🤔

Seanover 2 years ago(edited)

For GitOps of Helm, what’s your preference between:
• 🅰️ CI tool renders to k8s manifests _(helm/helmfile template) -_> writes to git/s3/… -> CD tool (flux/argo/…) pickups rendered manifests and applies them to cluster.
• 🅱️ CD tool (flux/argo/…) uses it’s own helm functionality to render on the fly and apply to cluster.
And for both, what’s your take on compatibility with Helm hooks?

August 2023 Browse by date October 2023