Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Adding Kubernetes support to the Docker platform

docker.com

Post reply on HN
Print view View original

11–20 of 144 posts

Re: Adding Kubernetes support to the Docker platform

#11

Post by sz4kerto »

grabcocque wrote: post #9
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 the one with the strongest mindshare and reputation? Even a cursory amount of googling shows there's a strong sentiment bias towards K8S over Swarm, it's not surprising that's what most people pick.

But the thing is that as a developer, it doesn't matter what you start with - you have both and you're using compose files, etc. So Docker is trying to make the orchestrator less relevant now, and says that 'don't worry about the orchestrator'. You, as a developer, are using Docker and Compose. (Or at least that's what Docker is trying to do here, I think.)

Re: Adding Kubernetes support to the Docker platform

#12

Post by amouat »

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 will now bridge that gap, giving me a k8s node to run against in dev.

Whilst Kubernetes has provided a great production orchestration solution, it never provided a great solution for development, meaning most users kept developing with Docker and Compose. It's great to see these worlds now coming together and hopefully leading to a first-class solution all the way from dev to prod.

Re: Adding Kubernetes support to the Docker platform

#14

Post by grabcocque »

sz4kerto wrote: post #11
grabcocque wrote: post #9

Earlier quoted context omitted.

Why wouldn't you start with the one with the strongest mindshare and reputation? Even a cursory amount of googling shows there's a strong sentiment bias towards K8S over Swarm, it's not surprising that's what most people pick.

But the thing is that as a developer, it doesn't matter what you start with - you have both and you're using compose files, etc. So Docker is trying to make the orchestrator less relevant now, and says that 'don't worry about the orchestrator'. You, as a developer, are using Docker and Compose. (Or at least that's what Docker is trying to do here, I think.)

I don't think having support for multiple orchestrators is valuable except as a transitional thing. In this case, presumably, transitioning from Swarm to K8S. Nobody is gonna want the hassle of supporting both outside a transition.

Re: Adding Kubernetes support to the Docker platform

#16

Post by grabcocque »

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.

Re: Adding Kubernetes support to the Docker platform

#18

Post by oblio »

hijinks wrote: post #17
malaporte wrote: post #15

Earlier quoted context omitted.

Any special insight here?

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.

Re: Adding Kubernetes support to the Docker platform

#20

Post by organsnyder »

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.

Minikube (and its derivative, MiniShift) have been very helpful for my team in bridging the gap between local development and production for Kubernetes and OpenShift.
Post reply on HN