4 ms·
Swarm is still supported and works. I have it running on my home server and love it. Kubernetes is fine, but setting it up kind of feels like I'm trying to ea
by tombert 6y ago
Swarm is still supported and works. I have it running on my home server and love it.
Kubernetes is fine, but setting it up kind of feels like I'm trying to earn a PhD thesis. Swarm is dog-simple to get working and I've really had no issues in the three years that I've been running it.
The configs aren't as elaborate or as modular as Kubernetes, and that's a blessing as well as a curse; it's easy to set up and administer, but you have less control. Still, for small-to-mid-sized systems, I would still recommend Swarm.
- theptip 6y ago> setting it up kind of feels like I'm trying to earn a PhD thesis. Are you following "k8s the hard way"? I've never had this problem; either: `gcloud container clusters create` Or `install docker-for-mac` And you have a k8s cluster up and running. Maybe it's more work on AWS?
- kronin 6y agoEkscli (if you want managed) and kops (if you want to manage it yourself) are just as straightforward.
- ithkuil 6y ago> setting it up kind of feels like I'm trying to earn a PhD thesis. The kind of people who has to both set the cluster up and keep it up and also has to develop the application and deploy it and keep it up etc is not the target audience. K8s shines when the roles of managing the cluster and running workloads on it are separated. It defines a good contract between infrastructure and workload. It lets different people focus on different aspects. Yes it still has rough edges, things that are either not there yet, or vestigial complexity of wrong turns that happened through it's history. But if you look at it through the lense of this corporate scenario it starts making more sense than when you just think of what a full-stack dev in a two person startup would rather use and fully own/understand.
- DelightOne 6y agoWhat are Kubernetes' rough edges?
- dirtydroog 6y agoThere are elements of our company that want to move to Kubernetes for no real reason other than it's Kubernetes. I can't wait to see the look on their faces when they realise we'll have to employ someone full-time to manage our stack.
- themacguffinman 6y agoI'm not sure you have to, that seems like the whole point of managed services like GKE.
- bulldoa 6y agoDo you have a recommended tutorial for engineer with backend background to setup a simple k8 infra in ec2, I am interested in understanding devops role better
- hnarayanan 6y agohttps://github.com/kelseyhightower/kubernetes-the-hard-way https://github.com/kelseyhightower/kubernetes-the-hard-way
- hinkley 6y agoOne of the things nobody liked to talk about in public when test automation was slowly "replacing" testers is that if you had the testers write automation, they brought none of the engineering discipline we tend to take as a given to the problem. It's hard to make tests maintainable. Doubly so if you aren't already versed in techniques to make code maintainable. I wonder sometimes if we aren't repeating the same experiment with ops right now.