Adding Kubernetes support to the Docker platform • Hacker News Board

Re: Adding Kubernetes support to the Docker platform

#21

Post by organsnyder » Tue, Oct 17, 2017, 10:53 AM UTC

mrmondo wrote: post #10

sz4kerto wrote: post #7

Seems that people think Docker has gave in, but I am not that sure. If you can switch between Swarm/Kubernetes transparently, then why wouldn't you start with Swarm? (I'm talking about small companies who're just starting with containers.)

Why wouldn’t you start with Kubes? Less vendor lock in and a much bigger community.

If "Docker == containers" continues to hold true in many people's minds, then it's possible that Docker Swarm could feel like the "vanilla" orchestration platform. Of course those of us familiar with the platforms know better, but that mindset could persist, especially with pseudo-technical decision-makers.

Re: Adding Kubernetes support to the Docker platform

#22

Post by freeman478 » Tue, Oct 17, 2017, 10:59 AM UTC

oblio wrote: post #18

hijinks wrote: post #17

Earlier quoted context omitted.

Amazon did join the CNCF

Yes, but it will be a while, I think, before they actually offer something based on it. I don't see any service based on it at this point. AWS ECS is based on Docker.

AWS Re:invent is in the end of november. I'd guess there will be some annoucements there ...

Re: Adding Kubernetes support to the Docker platform

#23

Post by sandGorgon » Tue, Oct 17, 2017, 11:01 AM UTC

How are they doing this? The big difference in swarm and kubernetes is the ingress. If this is seamless, then it has to be a batteries-included version of kubernetes with ingress, overlay network choice, etc already mapped out.

What are the details here?

Docker Swarm is beyond awesome and a great path for someone to scale up at the lower end of the scale spectrum (two containers). I really hope that this brings more people into Swarm.

I'm also keen to see what it means for the Kompose project.

Re: Adding Kubernetes support to the Docker platform

#24

Post by monsieurbanana » Tue, Oct 17, 2017, 11:09 AM UTC

organsnyder wrote: post #21

mrmondo wrote: post #10

Earlier quoted context omitted.

Why wouldn’t you start with Kubes? Less vendor lock in and a much bigger community.

If "Docker == containers" continues to hold true in many people's minds, then it's possible that Docker Swarm could feel like the "vanilla" orchestration platform. Of course those of us familiar with the platforms know better, but that mindset could persist, especially with pseudo-technical decision-makers.

Could you elaborate what alternatives to docker are worth checking out? I'm unfamiliar with containers and out of my head I can't name anything besides docker.

Re: Adding Kubernetes support to the Docker platform

#25

Post by nailer » Tue, Oct 17, 2017, 11:10 AM UTC

organsnyder wrote: post #21

mrmondo wrote: post #10

Earlier quoted context omitted.

Why wouldn’t you start with Kubes? Less vendor lock in and a much bigger community.

If "Docker == containers" continues to hold true in many people's minds, then it's possible that Docker Swarm could feel like the "vanilla" orchestration platform. Of course those of us familiar with the platforms know better, but that mindset could persist, especially with pseudo-technical decision-makers.

'docker == containers' is true in that people often use the terms interchangeably. I've heard many people say 'you should get into Docker' and then talk about Kubernetes.

Re: Adding Kubernetes support to the Docker platform

#26

Post by eggie5 » Tue, Oct 17, 2017, 11:14 AM UTC

amouat wrote: post #12

This really helps with the dev-to-production story for containers. When people first started using Docker containers, we were promised things would run identically in dev and production - no more "but it worked on my laptop" issues. Then the rise of orchestrators meant that there again became a significant difference between running an app locally (in compose) and in production (on Kubernetes). Docker for Mac/Windows…

summarised my sentiment perfectly

Re: Adding Kubernetes support to the Docker platform

#27

Post by bonsai80 » Tue, Oct 17, 2017, 11:28 AM UTC

I see them stating "...for developers using Windows and macOS" but not mentioning Linux. I feel like I'm missing something in how I'm reading that page. How can I make use of this on Linux?

Re: Adding Kubernetes support to the Docker platform

#28

Post by pmezard » Tue, Oct 17, 2017, 11:29 AM UTC

grabcocque wrote: post #16

amouat wrote: post #12

This really helps with the dev-to-production story for containers. When people first started using Docker containers, we were promised things would run identically in dev and production - no more "but it worked on my laptop" issues. Then the rise of orchestrators meant that there again became a significant difference between running an app locally (in compose) and in production (on Kubernetes). Docker for Mac/Windows…

There's minikube. There's been minikube for a long while.

Is there an easy way to build an image locally and start it in minikube without an external registry or running a local one?

Re: Adding Kubernetes support to the Docker platform

#29

Post by organsnyder » Tue, Oct 17, 2017, 11:30 AM UTC

monsieurbanana wrote: post #24

organsnyder wrote: post #21

Earlier quoted context omitted.

If "Docker == containers" continues to hold true in many people's minds, then it's possible that Docker Swarm could feel like the "vanilla" orchestration platform. Of course those of us familiar with the platforms know better, but that mindset could persist, especially with pseudo-technical decision-makers.

Could you elaborate what alternatives to docker are worth checking out? I'm unfamiliar with containers and out of my head I can't name anything besides docker.

rkt is likely going to be replacing Docker for the default engine in Kubernetes and/or OpenShift (I vaguely recall hearing that it was coming, but can't find a source to cite): https://coreos.com/rkt/

(edit: or maybe I'm thinking of CRI-O)

Re: Adding Kubernetes support to the Docker platform

#30

Post by user15128 » Tue, Oct 17, 2017, 11:31 AM UTC

amouat wrote: post #12

This really helps with the dev-to-production story for containers. When people first started using Docker containers, we were promised things would run identically in dev and production - no more "but it worked on my laptop" issues. Then the rise of orchestrators meant that there again became a significant difference between running an app locally (in compose) and in production (on Kubernetes). Docker for Mac/Windows…

in order to test your app in prod-like env you need to run prod-like env locally. ie. a k8s-cluster that is close enough to prod. for that you will have to at least simulate multi-node-setup and run all cluster-addons like in production.

i am excited about this move from docker but i don't think it will solve all the problems. i think once you have a bigger team it is worthwhile to run a second k8s-cluster besides prod where people can just test things on it. otherwise it is actually not that hard to run a local k8s-cluster with vagrant, not sure how docker wants to top that - i think there is no need to top vagrant.