• ToxicWaste@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      10 hours ago

      k8s has amazing features and can be quite nice to work with. but it also comes with quite some overhead and added complexity. ask yourself what you want from your pipelines.

      we have a bit of k8s and standalone docker. hell some of our customers even have full on laptops in a basement as jenkins slave. it highly depends, what your needs are. but (if in a corpo environment) don’t just go with one solution, because you already know it. the employer literally pays you to learn something new.

      • Marx2k@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        7 hours ago

        This is my take as well

        Truth be told, we have kubernetes running in our fleet for some deployments and we also run openshift for a lot of enterprise deployments, but for almost all of the things for which we deploy via docker, it’s overkill.

        I always push back on people that push k8s as the default deploy for all the things. It’s complex, it’s a lot of maintenance and ots going to be overkill for most of the things you’re deploying.

        It has its use case, but it isn’t everything. Sometimes, a simple docker container or, in the case of something like AWS, a server less fargate container, is going to be enough

    • nanometer1625@thelemmy.club
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      edit-2
      16 hours ago

      Are you asking because you’re in enterprise? If you are, you should probably do your own research on this subject rather than asking social media.