Sign in

What made you switch away from push deploys, if anything??

ci-cddeploymentgitops5 replies 路 371 views 路 started
Reply
  1. Uma Duarte
    @uma_pixel

    help!! starting fresh with on-prem servers. I can either do classic CI/CD where the pipeline deploys, or set up a GitOps controller watching a config repo. a small agency, limited time. What would u 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.

    thinking

    2
  2. Zane Fischer
    @zane.fischer

    How many environments are we talking about?? ??

    6 2 helpful
  4. Zora Gill
    @tensor_den-zl

    GitOps adds a second repo or folder to maintain, plus image update automation. For a solo maintainer that overhead is noticeable; for a team with several clusters it pays off quickly.

    0 2 helpful
  5. Yara Celik
    @yarac30

    oof the security argument is real: with pull-based, CI only needs write access to a git repo, and only the in-cluster agent has clusetr credentials 馃檹 With push, a compromised CI system has direct prod access. hope that helps :)

    1 2 helpful
  6. Lina
    @lina.larsen

    ehh i'd push back on GitOps for on-prem servers if it's not Kubernetes; you'll spend more time fighting the tooling than shipping.

    6 0 helpful
Read next 路 Automation & DevOps
Bind for 0.0.0.0:3000 failed: port is already allocated. By WHAT?
Solved 路 14 replies
Read

Reply to this topic

Sign in or create an account to reply.