3 ms·

Kubernetes is never maturing. It keeps moving. An installation just a year ago would have things that would require significant planning to upgrade. What is mi

• throwaway838112 11mo ago
  hear hear!
• lemontheme 11mo ago
  Just out of curiosity, what's wrong with either of those two?
  • j0057 11mo ago
    Docker is not for production. Nomad at scale in practice needs a lot of load-bearing Bash scripts around it: for managing certs, for external DNS, you need Consul for service discovery, Vault for secrets. At that point, is Nomad still simple? If you're going to take on all of the essential complexity of deploying software at scale, just do it right and use Kubernetes. Source: running thousands of containers in production.
    • steeleduncan 11mo ago
      > you need Consul for service discovery Kubernetes uses etcd for service discovery. It isn't that Nomad does things differently or less simply, it is just that they are more explicit about it. The real difference is that Kubernetes has a wide array of cloud hosts that hide the complexity from users, whereas Nomad can realistically be self hosted
      • deleted 11mo ago
        [deleted]
      • j0057 11mo ago
        I'm not saying that Kubernetes isn't complex, I'm saying it's a fallacy to claim that the Hashicorp stack in any way manages to be less complex in practice. All of these moving parts are unavoidable if you want to run software at scale, Kubernetes is just way better engineered than the Hashicorp stack, if only for not depending on dockerd.
• PunchyHamster 11mo ago
  That entirely depends which version change you hit. But I'd love LTS release chain that keeps config same for at least 2-3 years.
• blue_cookeh 11mo ago
  I don't really get this mentality targing K8s specifically nowadays - perhaps that was true in the early days but I'm managing several clusters that are all a few years old at this point. Cluster services like Cilium, Traefik, etc are all managed through ArgoCD the same as our applications... every so often I go through the automated PRs for infra services, check for breaking changes and hit merge. They go to dev/staging/prod as tests pass. I think services take me literally half an hour a month or so to deal with unless something major has changed, and a major K8s version upgrade where I roll all nodes is a few hours. If people are deploying clusters and not touching them for a year+ then like any system you're going to end up with endless tech debt that takes "significant planning" to upgrade. I wouldn't do a distro upgrade between Ubuntu LTS releases without expecting a lot of work, in fact I'd probably just rebuild the server(s) using tool of choice.
• deleted 11mo ago
  [deleted]
• KronisLV 11mo ago
  > What is missing is an open source orchestrator that has a feature freeze and isn't Nomad or docker swarm. Running Docker Swarm in production, can't really complain, at least for scales where you need a few steps up from a single node with Docker Compose, but not to the point where you'd need triple digits of nodes. I reckon that's most of the companies out there. The Compose specification is really simple and your ingress can be whatever web server you prefer configured as a reverse proxy.
• jitl 11mo ago
  wat, i did an upgrade of my year-old clusters in september and all i did was bump the version number and run terraform apply