Regarding Kubo, it’s not immediately obvious to me how useful it is in the long term (although I must stress that I’m definitely not a Cloud Foundry expert).
Reading the Kubo docs it seems that it is, in essence, two pieces:
1. A TCP routing system (load balancer) to get client traffic to Kubernetes-hosted services.
2. A VM monitoring and management system (BOSH) to keep the VM’s (that Kubernetes is running on top of) deployed, healthy and scaled correctly.
In practice #1 is typically provided by a combination of the IaaS load balancers (e.g. AWS ELB, GCE LB, OpenStack LBaaS and associated plugins, etc), and Kubernetes integration with those.
#2 is usually provided by a combination of native IaaS VM auto-scaling (e.g. AWS Auto-scaling Groups, GCE Managed Instance Groups, OpenStack Autoscaling etc), and again, Kubernetes integration with those.
Hence my above question around Kubo’s long-term usefulness.
What I did find interesting however is that Pivotal and CloudFoundry are explicitly and publicly supporting Kubernetes, so hopefully that means that porting CloudFoundry apps and tools to Kubernetes will become easier and more mainstream over time (through, for example, Cloud Foundry to Kubernetes API adaptors).
Technical Vice President
America Research Center
2330 Central Expressway, Santa Clara, CA 95050
Tel: 408-330-4721 Cell: 408-320-8917 Office # E2-9
Email: quinton.hoole@... ID#Q00403160
<cncf-toc-bounces@...> on behalf of "Afra, Ziad via cncf-toc" <cncf-toc@...>