Docker Swarm or Kubernetes or both?

[codeliner]

Should we rely on Docker Swarm or Kubernetes for container orchestration.

Also see #3

A showcase of both would be good. We could use https://github.com/prooph/micro-do as example project and see how it would be effected by using Swarm or Kubernetes.

Also we should compare integration possibilities with prooph/micro-cli

• service set up
• service registration
• orchestration
• ...

[codeliner]

@bweston92 can you take over the Kubernetes showcase?

@sandrokeil same question but for Docker Swarm?

Let me know what you need to get started.
Fight! :D

[bweston92]

On Fri, 17 Feb 2017 at 17:17, Alexander Miertsch ***@***.***> wrote: @bweston92 <https://github.com/bweston92> can you take over the Kubernetes showcase? @sandrokeil <https://github.com/sandrokeil> same question but for Docker Swarm? Let me know what you need to get started. Fight! :D — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABrq2bIICJkuQTll0ZB2T_QYistQJPOQks5rddYegaJpZM4MEhcD> .

Kubernetes is the biggest project on GitHub, support more container engines then just Docker need I say more.

[codeliner]

With Docker Swarm you can use the same docker commands like you already know. It is easier to learn for new developers/DevOps and that is still a good argument for Docker Swarm I think.

Anyway, a small showcase would be great. I need something to play with. I'm familiar with docker and docker-compose for development environments and we run Docker on AWS in production but neither Docker Swarm nor Kubernetes

I really enjoy working with docker-compose. How is that different when working with Kubernetes @bweston92 ?

[bweston92]

Kubernetes is difficult to get started with normally. On your local machine I recommend using minikube which will provision it for you.

…

On Fri, 17 Feb 2017 at 18:20, Alexander Miertsch ***@***.***> wrote: With Docker Swarm you can use the same docker commands like you already know. It is easier to learn for new developers/DevOps and that is still a good argument for Docker Swarm I think. Anyway, a small showcase would be great. I need something to play with. I'm familiar with docker and docker-compose for development environments and we run Docker on AWS in production but neither Docker Swarm nor Kubernetes I really enjoy working with docker-compose. How is that different when working with Kubernetes @bweston92 <https://github.com/bweston92> ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABrq2TkWlcBFPDa_6F8dyFHEUGhfMzSoks5rdeTrgaJpZM4MEhcD> .

[bweston92]

Also I don't know how Docker swarm does it's bin packing. But kubernetes is good and when using GKE it will even tell you you can spend less. On Fri, 17 Feb 2017 at 18:23, Bradley Weston <bradwestonwigston@gmail.com> wrote:

…

Kubernetes is difficult to get started with normally. On your local machine I recommend using minikube which will provision it for you. On Fri, 17 Feb 2017 at 18:20, Alexander Miertsch ***@***.***> wrote: With Docker Swarm you can use the same docker commands like you already know. It is easier to learn for new developers/DevOps and that is still a good argument for Docker Swarm I think. Anyway, a small showcase would be great. I need something to play with. I'm familiar with docker and docker-compose for development environments and we run Docker on AWS in production but neither Docker Swarm nor Kubernetes I really enjoy working with docker-compose. How is that different when working with Kubernetes @bweston92 <https://github.com/bweston92> ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABrq2TkWlcBFPDa_6F8dyFHEUGhfMzSoks5rdeTrgaJpZM4MEhcD> .

[codeliner]

Kubernetes is difficult to get started with normally. On your local machine

damn, that is a problem. Docker (Swarm) also makes trouble at least on OSX and M$ but sounds like Kubernetes is even more difficult. We need to take that into account, because we want to provide an easy way to get started with prooph/micro and the overall concept.

Not sure if we can provide a production-ready and secure set up, that is also easy to use for new devs.

Let's take mongoDB as an example. When you want to try mongo you install it and just use it. No auth, no schema creation, just install it and play with it. But of course, before you use it in production, you need to set up auth, mongo cluster/Replicatset and backup.

I'd like to have a similar thing for prooph/micro:

• Install it
• run it with a few commands
• get used to it
• take the next steps to put it to production

[bweston92]

Minikube is easy. Plus kubernetes has a nice dashboard you can validate and see all logging etc in. I'm not aware of the tooling around Docker swarm but kubernetes is minted.

…

On Fri, 17 Feb 2017 at 18:35, Alexander Miertsch ***@***.***> wrote: Kubernetes is difficult to get started with normally. On your local machine damn, that is a problem. Docker (Swarm) also makes trouble at least on OSX and M$ but sounds like Kubernetes is even more difficult. We need to take that into account, because we want to provide an easy way to get started with prooph/micro and the overall concept. Not sure if we can provide a production-ready and secure set up, that is also easy to use for new devs. Let's take mongoDB as an example. When you want to try mongo you install it and just use it. No auth, no schema creation, just install it and play with it. But of course, before you use it in production, you need to set up auth, mongo cluster/Replicatset and backup. I'd like to have a similar thing for prooph/micro: - Install it - run it with a few commands - get used to it - take the next steps to put it to production — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABrq2Yvo7VPykC0Yib7Fx_ucLlZoDu2bks5rdehtgaJpZM4MEhcD> .

[codeliner]

sounds good @bweston92