cluster-api

I can’t think of a worse way to manage Kubernetes than Terraform. After years of running into issues, I think it’s really only suitable for small clusters. ClusterAPI has been the way my company has been doing things lately and I can honestly tell you it’s been transformative. https://github.com/kubernetes-sigs/cluster-api There’s nothing more amazing that updating a kubelet version in a git repo and watching ClusterAPI carefully cordoning off nodes and moving our workloads to new machines while I sit back and watch via ArgoCD.

It's actually the recommended approach from K8s upstream - https://github.com/kubernetes-sigs/cluster-api

Take a look at SIG Cluster API for Kubernetes-native ways to spin up and down new nodes. https://github.com/kubernetes-sigs/cluster-api Also see https://github.com/kubernetes-incubator/external-dns.

> What happens if new customer wants his tenant - is automating of provisioning of an entire new cluster feasible? This is doable through various provider/vendor-specific APIs. Pivotal's PKS has an API. GKE has one, EKS, AKS and so on have them too. In the longer run there's meant to be a full Cluster API, which I presume will take over for that role: https://github.com/kubernetes-sigs/cluster-api

I'm not the original poster, but I think they were suggesting that K8s supports better bin packing than you get with virtual machines, so you can run the same applications on fewer (or smaller) servers. In terms of the cutting edge of bringing "declarative, Kubernetes-style APIs to cluster creation, configuration, and management" see https://github.com/kubernetes-sigs/cluster-api

That's all nice. The issue though is that BOSH has been completely leapfrogged by Kubernetes with its extensible API. Nowhere will BOSH ever get to the community reach and acceptance of the level of Kubernetes. That Boat has sailed. And with implementations of the machine specs [0,1,2,3] you get rid of the "media break" that you deem BOSH is filling (it is not). Maybe you could implement BOSH as implementation of the machine spec and integrate into K8s, the other way round than KuBo? As for the bunch of data services, I guess it's only a matter of time until you see a cambrian explosion of productive operators. I mean this non-comprehensive list [4] is already impressive. SAP works in many projects where obligations with long term commitments have to be kept. And that is ok. BOSH CPI is one experiment to get CF on K8s. Have a look at the

Actually it is already possible to create persistent disks through Kubernetes by creating a persistent volume claim (pvc) which triggers an actual persistent volume to be created. Cloud provider controllers take care of this, just like they create load balancers for services. Also there’s already work being done on supporting cluster management from Kubernetes itself: https://github.com/kubernetes-sigs/cluster-api