Kubernetes Documentary Part 1: A Critical Review
First, Thank you for taking the time to review the video. As someone who is betting a startup&#x2F;living on kubernetes I have more clarification&#x2F;opinions:<p>1. Of course kubernetes was developed to get customers to GKE and for profit reasons. 99% of the open source developers are paid programmers. Hence there is an alternative cost to their time. I am not sure why this is wrong. At least they did not fork an open source project and offered it without credit to the original companies, like other cloud providers.<p>2. The way google develop open source products is community first &#x2F; tech later. But this is stated. For example, kubeflow - it was started as a community project, got the requirements&#x2F;community in place first, and than was redesigned I think 2-3 times. The one thing about google &#x2F; GCP is that they are doing the initial R&amp;D, but fail to follow - I.e. they expect the community to pick up. I assume that this can be attributed to the internal promotion cycle inside google (where engineers are expected to rotate), vs tech reason.<p>3. Of course kubernetes will be maintained by on perm companies (e.g. VMWARE&#x2F;IBM). The predecessor to kubernetes was open stack, which was also developed by on perm hardware companies (e.g. CISCO &#x2F; HP). You still need money to pay engineers.<p>Moreover, I think that you are missing the key attributes of kubernetes, which morphed from its original goals. Kubernetes is about 3 things:<p>1. Scalability - you can run it on you laptop or IOT device up to the cloud (e.g. k3s).<p>2) Distribution - Kubernetes as a platform is permission-less and widely spread. I.e. If you want to extend it or develop on it, you do not need anyone permission, and you can assume that it would exist on your customer cluster. It is my belief that AWS have about 5% of IT workload, and is hitting a wall (see the latest sessions on AWS conference, which is catering to more legacy companies).<p>3) Automatic operation - Kubernetes control loop allow machines to manage machines (both software and hardware). I.e the carrot of the cloud is offloading management of your infra. The stick is that you pay 20x more on your hardware. Kubernetes give you another way - which is encapsulate the IT knowledge in a automatic robots - called operators, and let those manage your application.  The problem is that this feature is not widely known. (and it is my goal to change that).