4 ms·

Or kind. And use Skaffold or Tilt to manage it all. This setup makes Docker Compose look like a toy. Developers should stop with this impedence mismatch of u

• polski-g 3y ago
  It's not about just running the containers. It's that applications are distributed with a docker compose file as the setup medium.
  • LeBit 3y ago
    What do you mean by that? You use Docker Compose to distribute to production? Into what?
    • polski-g 3y ago
      Here is netbox's compose file: https://github.com/netbox-community/netbox-docker/blob/release/docker-compose.yml https://github.com/netbox-community/netbox-docker/blob/relea... -- there is no way I am going to spend the time to translate that into whatever k8s wants. If it isn't broken don't fix it.
      • ofrzeta 3y ago
        You could use Kompose https://kompose.io https://kompose.io, just sayin :)
        • LeBit 3y ago
          With 8.7k stars, plus the last commit was made 4 days ago and the last release was 3 weeks ago. That's a pretty strong option!
          • quickthrower2 3y ago
            Yeah it is a pity people think this way. If you create something that just works and don't need bugfixes for a year then you are punished! Probably those people should add empty commit "nothing to do!" and do release "release notes: nothing more to add or remove"
            • LeBit 3y ago
              I partially agree with you. Docker Compose is still a moving project. Look at the version of the schema. It evolves. Kubernetes is also a platform that is moving. And it is moving fast. If Kompose was considered `done` by its authors in 2020, I don't think I would even bother trying it out. It probably wouldn't be able to parse recent Docker Compose schemas and it would probably output outdated Kubernetes manifests. But, see, yesterday I was looking for a Time Boxing application and stumbled on that one: https://github.com/khrykin/StrategrDesktop/ https://github.com/khrykin/StrategrDesktop/. I dismissed it because the last release was in 2020. But that is an example of an app that could be considered `done` and still useful 3 years later. Hence why I partially agree with you. :)
              • ofrzeta 3y ago
                StrategrDesktop still has three unticked boxes for platform support, though :-)
      • LeBit 3y ago
        okay, but that only allows you to deploy to a docker engine. at best, you can deploy that app to a Docker Swarm. Docker Swarm is not reasonably comparable to K8s. there are tools (and colleagues ! :) ) to transform docker compose files to K8s manifests.
• hahn-kev 3y ago
  Man, compose can be so much simpler for local dev though, you can easily bind local files and you don't need a fancy setup for local dev. We just switched from docker compose to k8s so that it was closer to prod, but I think if we had to do it again I'm not sure I'd bother.
  • LeBit 3y ago
    With Skaffold, you can bind (or rather transparently sync) local files to a Pod. I agree the initial setup is more difficult with a K8s local dev than with a Docker Compose local dev. But the impedance mismatch makes using Docker Compose a bad idea when you deploy to a K8s cluster. The secrets management is different. The way pods talk to each other is different. App-level configuration and updates are different. There is so much that diverges, that you end up with two independent systems. One for dev and one for prod. This is not good.