Why the Kubernetes Kids can't hurt Bezos' Amazon beast

Kinda misses the point...

I agree with the article, and its take on some spin... I also agree with AndyPiper to a point.

Its not about developer convenience but more on lowering the cost of development and time to value.

You can build and test in small dev environments and then deploy anywhere. I can give developers a decent MacBook Pro, and then a small cluster to test local, cluster deployment. Then I can move to production either on prem or at cloud provider.

The thing about lock in... its the high cost of moving data out of the cloud or around the globe w your cloud provider.

Funny thing... IBM's new mainframe... X14 could be a game changer depending on costs.

It's all about Docker

The article somehow maanges to avoid almost all mention of Docker.

Kubernetes is a platform for deploying Docker containers, and the "consistent developer deployment model" comes entirely from Docker.

You can package up your applications in Docker, and then you can deploy the same images in a bunch of different environments (Docker Swarm, Rancher, Kubernetes, Amazon ECS, Mesos, ...)

So really it doesn't matter too much if Kubernetes dies or not: you can just move your applications on to another platform. This has already happened: CoreOS used to have a Docker deployment platform called "fleet", but they recently decided to abandon it (in favour of Kubernetes as it happens)

the concern is a waxing Amazon Web Services

Amazon does Brazilians now???

Kubernetes not comparable with OpenStack

I do not agree with the article that Kubernetes competes with AWS. Kubernetes is about containers and AWS is about fat Virtual Machines. Kubernetes in an application that floats on top of AWS or any other IaaS operator.

Kubernetes work very well on top of AWS and it would not surprise me if Amazon offers an Kuberntes-as-a-Service in the future.

Companies are gyrating towards Kubernetes because it enables true hybrid-cloud where work-loads can float freely between cloud operators.

k8s is the best way to get people to gcp. azure has it right. ecs will give way too

Kubernetes was the best way google, at #3, could blow up cloud. Google has awesome infra and global scale and presense AND they know how to write original software. From android, to app store, to youtube, to search, to adwords, to docs/sheets, drive, you name it, they do this eventually get it right and take over model well.

When kubernetes was born this was not brokenstack/openstack. It was a glimpse on how google does things that work. And when you start doing stuff that matters going from kubernetes to gcp is rational. Now azure has a bill by the second container service that makes sense and I think we will see AWS abandon ecs/blox and go the kubernetes route. It was called borg for a reason. Resistance is futile. While docker ruins itself by closing up and becoming anti-standard and meso/DCOS languishes kubernetes isnt the next brokenstack for a good reason:

The production version of kubernetes is gcp! Brokenstack OPenstack had no public cloud for itself. One could argue rackspace but they couldnt keep up in public cloud with amazon and friends and died out. With brokenstack, there is no public / production cloud version of it. You own it.

But with kubernetes, get sick of it all and want to push the help me button? You dont call pivotal, IBM, you dont wait for dummies like Vmware to "help" you, you dont care - you go with gcp or with azure container service with by the second billing and be done with it.

Google's best long term troll ever was to release borg onto the world so people would use it, get tired of trying to do what gcp does and just use gcp and move on.

This is one where even amazon let it get away from them.

And frankly, anyone but scamazon. IF YOU USE AMAZON YOU WILL FACE COMPETITION FROM AMAZON ITSELF IF YOUR BUSINESS MODEL WORKS.

Did anybody actaully try to deploy and run Kubernetes on google cloud? With google's native offering. They supposed to have an amazing offering and tight integration with all their services, right?

Well, not so much.

Upgrading of the cluster works great, an engineer can do full cycle upgrade to a next k8s version in half an hour. However, the master node will go down for 1-2 minutes (!) when a manually issued cli command applied. Yup, that's right - there is no way to version-control this process. Nothing like CloudFormation.

Now, running services is a breeze. Except passing traffic in (so-called "ingress"). Sure, you can create a load-balancer for each service, that's pretty easy. But there is no DNS integration, no logs, no metrics out of that loadbalancer. And for each little micro-service running you'll need a new loadbalancer provisioned.

But that's not all that bad. There is Cloud Endpoints ("API Gateway") - where services from kubernetes can be integrated with managed API. But look up the docs of that integration for kubernetes and compare it with AWS API gateway integration for pretty much anything.

And these are just a few issues you'll run into immediately. Sure, if you're a startup - not a big deal. Each team can manage own kubernetes cluster. But if you're an enterprise that requires proper configuration management, version control of changes, availability, documentation, integration with all other systems, support - then kubernetes will be a very hard to sell.

It like openstack - but for containers.