News for hackers. Stuff that matters.

A comment on Container orchestration: Moving from fleet to Kubernetes.

Re:Container orchestration: Moving from fleet to Kubernetes by chad-autry on Tuesday February 07, 2017 @06:18PM (#13593951)
I've been telling friends and co-workers I think kubernetes has won the orchestration war. But even as I did so I wanted something simpler for my own purposes, and so was using fleet.

Luckily for me, I'd stuck with making all my units global and driving their deployment off of metadata. I think I'll just strip off the [X-fleet] section, and start deploying them straight to systemd with ansible.

[ Parent | on HN ]
Re:Container orchestration: Moving from fleet to Kubernetes by mrkurt on Tuesday February 07, 2017 @07:17PM (#13594397)
This is roughly what we're doing. Ansible to manage specific containers on hosts. It works quite well, and with some IP tables shenanigans we have a lot of power over how we roll new containers out.
[ Parent | on HN ]
Re:Container orchestration: Moving from fleet to Kubernetes by tvaughan on Tuesday February 07, 2017 @07:19PM (#13594406)
Or just copy them? https://gitlab.com/tvaughan/docker-flask-starterkit/blob/mas...
[ Parent | on HN ]
Re:Container orchestration: Moving from fleet to Kubernetes by chad-autry on Wednesday February 08, 2017 @10:12AM (#13598772)
Ansible brings inventory management to the table. I can have an inventory with my backend and frontend instances tagged, run my playbook, and it will copy/start the appropriate systemd units.
[ Parent | on HN ]