3 ms·

We have Docker. On top of it, we have docker-compose. On top of it, we have Kubernetes. On top of it, we have Spread. And it all goes on top of AWS or Google Cl

We have Docker. On top of it, we have docker-compose. On top of it, we have Kubernetes. On top of it, we have Spread. And it all goes on top of AWS or Google Cloud instances. "Every problem in computer science can be solved by adding one more layer of indirection — except for too many layers of indirection".

nzoschke 11y ago
I understand the concern with too many layers but you have it wrong in this case. The low level platform is Kubernetes. This is a managed service on Google Cloud, or you can run the open source project on other substrates. What you are seeing here from Redspread is a super easy way to run kube locally. Redspread represents a growing suite of tools to make managing stuff on Kubernetes easy anywhere. The best analogy I've seen for the pattern is "porcelain" and "plumbing", which I learned from Git. We certainly need pipes and valves everywhere. But we really want a toilet and sink, simple specialized interfaces to the holes in the ground. Kube is low level plumbing for managing raw compute and network resources. Kube itself has some higher level tools. But it's great that Redspread is making some too. There are plenty of unique use cases and workflows we all want
deleted 11y ago
[deleted]
andrewstuart2 11y ago
Not sure what makes you think Kubernetes is on top of docker-compose. It's a fundamentally different model for deployment. Pods, scheduling, DNS vs. links, autoscaling, etc. Additionally, kubernetes will soon be able to use both docker and rkt containers.
- agelast 11y ago
  > Additionally, kubernetes will soon be able to use both docker and rkt containers http://kubernetes.io/docs/getting-started-guides/rkt/ http://kubernetes.io/docs/getting-started-guides/rkt/