Geekly Articles each Day
⬆️ ⬇️

The New Stack statistics about the difficulties of implementing Kubernetes





In May 2017, the online publication The New Stack conducted a survey of 470 representatives of organizations that characterized themselves as container users. The collected data were published in a special e-book on Kubernetes, and key findings were published as separate news on the resource. The last of them was devoted to the introduction of Kubernetes, and this is what the numbers say ...



Barriers to implementation



It is unlikely that anyone will be surprised by the fact that the main obstacle slowing the start of Kubernetes application is the complexity of the configuration and product support - 36% of the respondents clearly (not using K8s in production) unequivocally agree, 39% agree to some extent that in total gives 75% .

')

However, it should be noted and the closest pursuer among the answers to this question - the presence of other projects with high priority - which in total was supported by 60%. Apparently, the need for these respondents to implement K8s is not yet so high due to the specific infrastructure or lack of confidence about the applicability, the available capabilities and / or the proven reliability of Kubernetes.



Of the other results that Kubernetes still hinders adaptation, almost half of the respondents (43%) use other solutions to one degree or another, and 27% think that manual orchestration is more or less sufficient. However, both of these arguments are no longer very significant for the vast majority of respondents.







Implementation deadlines



The time spent on implementing Kubernetes was in line with expectations (or even less) in 56% of cases , but more than a third of respondents (38%) had this process delayed.







The initial phase of implementation is the most time-consuming: only 50% of users surveyed at this stage had a time out prediction. At the same time, the full implementation met the deadline for 63% of respondents.



One of the representatives of small businesses noted that the implementation took longer because of poor documentation on Kubernetes as of a year ago, but "today everything is much simpler." Similar criticism of the project has been heard from other companies that implemented Kubernetes a year or two ago - for example, Concur (later absorbed by SAP). According to the results of their project on putting K8s into production in 2016, Concur experts called the insufficiently detailed / detailed documentation the main problem of the young Open Source-project. And by 2017, they fell in love with CoreOS products, explaining their choice as “the best documentation for Kubernetes”.



78% of respondents were involved in the implementation of their own, 12% assigned this task to another team within the company, and 9% - to third-party professionals involved in Kubernetes and DevOps. For cases of Kubernetes implementation with the help of contractors, 20% of the respondents did not meet the deadlines, which is almost twice as good as the general indicator, when the implementation was mainly carried out on its own.



Results of implementation and conclusions



According to data from 173 users of Kubernetes in production, this system fully or partially meets their needs in 99% of cases . At the same time, users of large-scale Kubernetes implementations are more fully satisfied with the system - they have this indicator one third higher than those who are at the initial stage of operation.







As noted in The New Stack, “though a little less than half of the users who have implemented Kubernetes on a large scale, are completely satisfied with the result, remember that at its 2-year-old Kubernetes ecosystem (or market) for another year before some analytical firms could consider its as a developed, established market. "



Another conclusion is that at the implementation stage of Kubernetes it requires significant human resources, but over time they pay for themselves (due to the fact that the deployment is accelerated, the management of the infrastructure is simplified, its scaling, etc.).



What conclusions are made regarding the market? With a high probability, many companies will look for orchestration solutions integrated into larger platforms that are already used by them one way or another (for which they have gained sufficient expertise, experience, and confidence). In addition, the complexity and duration of the implementation of Kubernetes means good opportunities for new companies able to solve these problems for their customers (using their products and services).



Other information about the respondents



You can get a better idea of ​​the users surveyed in The New Stack using the additional statistics published in the mentioned e-book :





And below is attached a poll , which aims to find out how many Habra users have already implemented Kubernetes or are just going to do it. Comments to your answers, of course, welcome!



PS



Read also in our blog:



Source: https://habr.com/ru/post/340270/

More articles:



All Articles