WhitePaper Kubernete
WhitePaper Kubernete
[1]
Cloud Native Computing Foundation (CNCF), 2019 CNCF Survey results are here: Deployments are growing in size and speed as cloud native
adoption becomes mainstream, March 4, 2020
[2]
CoreOS Blog, 451 Research study reveals rapid adoption of Kubernetes for hybrid cloud infrastructure, June 16, 2017
[3]
451 Research, 451 Research Says Application Containers Market Will Grow to Reach $4.3bn by 2022, December 5, 2018
[4]
RedMonk, The Kubernetes Lesson, March 2, 2018
[5]
CNCF, 2019 CNCF Survey results are here
Arun Chandrasekaran wrote in a report[6], citing the steep Kubernetes learning curve.
By 2024, 70% of new applications[7] will rely on containers for improved development speed, application
consistency, and portability. But with teams spending too much time on the infrastructure side of
Kubernetes, they can miss out on the acceleration potential[8]. The Cloud Native Computing Foundation
(CNCF) found[9] that setting up the security infrastructure was a top challenge for 40% of users, while
32% said monitoring was the toughest component. Roughly 25% of users also found establishing
[6]
Gartner, Best Practices for Running Containers and Kubernetes in Production, February 25, 2019
[7]
IDC, DC releases Top Ten Developer and DevOps Predictions for 2020: DevOps to Gain Wide Recognition, February 20, 2020
[8]
The New Stack, The New Stack Context: Is Kubernetes the New App Server?, May 15, 2020
[9]
CNCF, 2019 CNCF Survey results are here
[10]
Replex, The Ultimate Kubernetes Cost Guide: AWS vs GCP vs Azure vs
Digital Ocean, September 19, 2018
The orchestration engine should ensure that Kubernetes automatically distributes containers across the
cluster to provide the most efficient use of resources, and should also automate backup and recovery
so data are never lost when errors occur. Scalability should be automated too; 70% of Kubernetes[11]
users look to it for autoscaling, which ensures that resources grow in real-time as workloads increase.
The significance of security goes without saying that developers must be able to trust that the
Kubernetes engine they choose is committed to consistently protecting their data. “Security can’t be an
afterthought,” Gartner’s Chandrasekaran warns[12].
[11]
CNCF, 2019 CNCF Survey results are here
[12]
Gartner, Best Practices
Meanwhile, infrastructure that enables developers “We prefer a simpler Kubernetes experience that
to build their apps on multiple clouds through delivers on all the key requirements, and then
shared development and operations approaches gets out of the way,” Lazu said. “We also prefer
is a truer reflection of the promise of cloud fewer options and better defaults, because we
technology. That’s also why open APIs to manage don’t have all day to spend on Kubernetes.”
and modify clusters, and flexible integrations with
Lastly, the pricing structure also has to be
popular Kubernetes tools such as Rancher, Helm,
adaptable. Management engines with a simple,
and Operator, are important.
flat, and predictable price model are more
attainable for most companies. While Amazon
EKS and GKE charge a per cluster management
fee of $.10 per hour or $73 per month, alternative
cloud providers offer customers a more cost-
efficient option for running Kubernetes. For
example, Linode doesn’t charge per cluster so
that developers can save up to 50% with full-time
usage.
[13]
Threat Stack, 20 Developers and Kubernetes Experts Reveal the Biggest
Mistakes People Make During the Transition to Kubernetes, December 20,
2018
For companies to build environments that truly speed up application development, they need
Kubernetes management engines that are affordable, adaptable, and simple. Only then will they be able
to leverage Kubernetes’ fullest potential as data infrastructures get more complex.