4 ms·
I literally have no idea what this does. It doesn't make any sense. Even guessing, adding hidden complexity on top of k8s doesn't seem a good idea.
by jnardiello 10y ago
I literally have no idea what this does. It doesn't make any sense. Even guessing, adding hidden complexity on top of k8s doesn't seem a good idea.
- markbnj 10y agoThe docs are a little sparse but reading between the lines it's a set of tools for configuring k8s clusters at a higher level of abstraction than gcloud and kubectl. If you've built out automation to deploy k8s services then you know that there is still quite a bit of manual configuration needed to define the clusters, repl controllers, services, ingress, persistent disks, etc. If you wanted to build a PAAS on top of k8s then you'd begin pretty much as these guys have, I think.
- jnardiello 10y agoI'm very heavily working with k8s and while what you say is definitely true, I'm not too bothered by what I have to configure (aka stuff I can control directly). What I really dislike is stuff on which I have no direct control and that's the main problem with k8s. Lot of stuff "just works", with little-to-no documentation on what are the pieces concurring to make it work nor how it is configured. The 'it just works' approach might be great with simple scenarios, but it's horrible for complex use cases where you need to have detailed control over the pieces that will run in production and - once they are properly setup -, you would anyway automate accordingly your specific usecase. Hence my: "Additional hidden complexity doesn't seem to be a good thing in this case". Beside that, I really have no idea about what they specifically mean with "Kubernetes-based PaaS". What is it? Abstracting kubernetes cluster setup? If this is the case, i remark that I need more fine-grained access on the internals rather than additional abstractions that internally do "god-knows-what".