\n
![](\"https:\/\/i0.wp.com\/rsoftsolution.com\/blog\/wp-content\/plugins\/RSSPoster_PRO\/cache\/f3565_30253951384_c484ac85c7_o-1.jpg?w=640&ssl=1\")
<\/p>\n
\n<\/p>\n
The Cloud Native Computing Foundation<\/a> (CNCF) announced today that 36 members have agreed to a set of certification standards for Kubernetes<\/a>, the immensely popular open source container orchestration tool. This should make it easy for users to move from one version to another without worry, while ensuring that containers under Kubernetes management will behave in a predictable way.<\/p>\n The group of 36 is agreeing to a base set of APIs that have to underly any version of Kubernetes a member creates to guarantee portability. Dan Kohn, executive director at CNCF, says that they took a subset of existing Kubernetes project APIs, which are treated as a conformance test that the members who have signed on, are guaranteeing to support. In practice this means that when you spin up a new container, regardless of who creates the version of Kubernetes, it will behave in a consistent way, he said.<\/p>\n Kohn said that the organization has been able to bring together many of the industry\u2019s biggest names onboard. \u201cWe are thrilled with the list of members. We are confident that this will remain a single product going forward and not fork,\u201d he said.<\/p>\n Forking is the act where some companies break off on their own in an open source project, creating a new and possibly incompatible version of the software. The CNCF wanted to ensure this didn\u2019t happen, and so apparently did many of its powerful members including Microsoft, Red Hat, Alibaba, Oracle, Google and IBM along with many others.<\/p>\n AWS, the biggest force in public cloud computing<\/a>\u00a0was not among the companies signing, but the CNCF says this is simply because the company has yet to create its own version of Kubernetes (although it supports Kubernetes clusters running on AWS). When AWS\u00a0joined the CNCF in August<\/a>, it was a major proof point that the CNCF and Kubernetes had arrived.<\/p>\n Make no mistake, this a huge and somewhat miraculous occurrence to have this many diverse technology companies agree to anything, but Kohn says most of the organization came together fairly quickly around the forking concern.<\/p>\n \u201cKubernetes is skyrocketing and everyone is adopting it. When you have a high level of engagement and adoption, there is a concern whether the project is going to fork. If I have an app that works on one version, will it work on another one,\u201d Kohn told TechCrunch.<\/p>\n Kubernetes has indeed become a defacto standard in the last year with just about every big name in tech joining the CNCF<\/a>. Today\u2019s announcement is about bringing some level of discipline to a growing project and it\u2019s a significant step forward in the maturation of Kubernetes as an open source project.<\/p>\n <\/p>\n