Sign in

we deploy with a script and ssh. should i be embarrassed? lol

Solvedci-cddeploymentgitops13 replies · 206 views · started
Reply
Accepted solution by Ivan Ortiz — The biggest practical win of pull based GitOps is drift correction: the controller keeps reconciling, so manual hotfixes on the cluster…
  1. Yara
    @tensordeck-2sw

    help!! starting fresh with on-prem servers. I can either do classic CI/CD where teh pipeline deploys, or set up a GitOps controller watching a config repo.. 😂 two ops people, limited time, what would you choose today?

    I have about two weeks to set this up before the first real customer goes live, id rather pick something boring that I can debug at 3am than something elegant that I barely understand... real-world experiences very welcome, including teh bad ones. im about to throw this thing out the window lol

    6
  2. Noor A.
    @thread_tinker-12y

    How many environments are we talking about?

    2 14 helpful
  4. Gabe L.
    @shaderbench
    in reply to @tensordeck-2sw

    The security argument is real: with pull-based, CI only needs write access to a git repo, and only teh in-cluster agent has cluster credentials. With push, a compromised CI system has direct prod access. lmk how it goes

    6 0 helpful
  5. Quinn Ferreira
    @daemonfiddler-252
    in reply to @shaderbench

    hmmm for VMs and non-Kubernetes targets, GitOps tooilng is much thinner. A CI pipeline plus a config management tool (Ansible, for example) is often the pragmatic answer there. lmk how it goes

    4 0 helpful
  7. Quinn Ferreira
    @daemonfiddler-252

    oh ive been there lol gitOps adds a second repo or folder to maintain, plus image update automation. For a solo maintainer that overhead is noticaeble; for a team with several clusters it pays off quickly.

    0 1 helpful
  8. Zane Lopez
    @zlopez

    Whatever you choose, make rollbacks boring: with GitOps its a git revert, with push deploys keep the previous artifact and a one-command redeploy.

    0 1 helpful
  9. Quinn Ferreira
    @daemonfiddler-252

    spent 20 minutes on on-prem and im still not done thx in advance!!

    1 0 helpful
  10. Ivan Ortiz
    @threadfiddler
    Accepted solution

    The biggest practical win of pull-based GitOps is drift correction: the controller keeps reconciling, so manual hotfixes on the cluster get reverted or at least flagged. With push deploys, drift is invisible until something breaks.

    lol

    4 6 helpful
  12. Wren
    @wreno446

    ehh counterpoint to CI push is fine: once you have more than one cluster, push-based pipelines become a tangle of credentials. better to start pull-based early. but hey ymmv

    2 0 helpful
  14. Yara
    @tensordeck-2sw
    in reply to @threadfiddler

    @threadfiddler we'll keep push deploys for now but add drift detection and lock down manual changes. revisit GitOps when we add a second cluster.

    40 0 helpful

Reply to this topic

Sign in or create an account to reply.