The moment it dawned on me how simple swarm was, was when I realised that all I had to do to expose an nginx service publicly was to publish the ports in my compose file. Weave scope for Kube admin (admittedly not as pretty) and I could easily setup my own ELK to monitor my containers. No mission-critical feature, or incredibly convenient really nice to have feature in Kubernetes that I'm going to miss except perhaps the Kube admin dashboard, and heapster but even those have ready replacements. I in all honesty see no reason to not use Swarm. It has been the hammer with which I have approached almost all my deployments, and the one tool I have mentioned (shoved down clients throats) in almost all my foremost communications with clients, and it was my go to choice when I was mocking my first startup ().Ī few weeks ago Docker 1.13 was released and I was tasked with replicating a client's Kubernetes deployment on Swarm, more specifically testing running compose on Swarm.Īll our apps were already dockerised and all I had to do was make a few modificatons to an existing compose file that I had used for testing before prior said deployment on Kubernetes.Īnd, with the ease with which I was able to expose our endpoints, manage volumes, handle networking, deploy and tear down the setup. I have been an aggressive Kubernetes evangelist over the last few years.
0 kommentar(er)
