Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Kubernetes Challenges for Enterprises

Containers

(Image: Unsplash)

Kubernetes has evolved with capabilities that are suitable for enterprise IT workloads. Now that Kubernetes is ready for the enterprise, let’s learn about the challenges of implementing Kubernetes into your IT infrastructure.

Investment in Modern Technologies

In 2018, we saw a significant rise in the adoption of Kubernetes for modernization data centers by enterprises that want to leverage digital transformation. This year, we have seen more investment made by enterprise CXOs and leaders. According to the Diamanti survey for container adoption, enterprises investing $100K or more in containerization of workloads increased to 38 percent in 2019 as compared to 31 percent in 2018. But the challenge is that, despite a big hype of Kubernetes in the last 24 months, the ratio of investment in Kubernetes is quite slow. The reason for this: most leaders are assigning less IT budget, or they are still in confusion about whether to go for a single standalone framework to manage application workloads.

Deployment Types

Kubernetes can be implemented in IT infrastructure in three ways.

One is to bring on the Kubernetes framework directly into the infrastructure and re-structure and re-design the infrastructure according to architecture. The second is to hire a managed Kubernetes solution vendors to implement, deploy, and manage Kubernetes for enterprises. And the third is to turn to production solutions like Red Hat OpenShift to implement Kubernetes.

There are pros and cons to each of the solutions. Enterprise leaders must select a solution that fits their business strategy and results in an increase in service delivery and agility. The time required for this is hampering the adoption of Kubernetes in data centers. Some of the issues that must be addressed include:

DevOps: Kubernetes solves challenges to manage the container in an efficient way and provide many benefits. But Kubernetes is known to be a complex platform itself for implementation and managing DevOps aspects.

There are challenges related to automating operations like configuration of the load balancer. One can deploy an application with kubectl, but for automation, you must configure the load balancer.  

Kubernetes also is well known for the ability to efficiently utilize computing power for deployed container clusters. But to achieve this, admins have to understand that there is a manual process involved in making configurations on each pod that is hosting containers to computing resources.

Security: Kubernetes has emerged as a de facto standard tool for managing all application workloads in enterprises. Enterprises IT teams are keen to get Kubernetes in production, but on the other side, attackers are also finding new ways to breach the infrastructure powered with Kubernetes. We can say, as Kubernetes adoption has grown, so too has the attacks surface and security risks grown.

As per Dimanti container adoption survey in 2019, security has become major challenges for containers in production for enterprises.

With this, a Kubernetes platform and container security have become a major concern this year. In the last three months, Kubernetes announced major platform releases, disclosed several incidents and released several patches to fix the security holes in the Kubernetes framework. You can refer to this link to get more information.

Reason for breaches of Kubernetes based infrastructure can be:

  • Flaws in the design and architecture of Kubernetes for large or medium scales deployment.

  • If a flaw is left or overlooked by the developer in the application within the container, it can result in the compromise of containers, and further, a hacker can gain unauthorized access into clusters to make a false impact.

  • The connection of Kubernetes pods can be left unauthorized. This can result in malicious attacks on the pod itself.

  • Kubernetes infrastructure components also can be exploited, compromised, and get affected by external or internal breaches.

Such security concerns raised a new stream in the Kubernetes ecosystem in the form of securing the Kubernetes platform. Many vendors have started to offer managed solutions and services for enterprise Kubernetes platforms.

Lack of Kubernetes skills: Enterprises expect a standard and a shared platform that can be useful in multi-cloud implementation, keeping on-premises data center in place. Workloads in Kubernetes should run on any connected cloud without any problem in an agile way. For that level of output from Kubernetes, resources need to be managed by a staff with the right skills around the Kubernetes platform.

The core issue that can be raised with Kubernetes skills deficit is in performing day 2 operations for Kubernetes implementation in infrastructures like upgrades, patches, and more. Kubernetes skilled experts know how to perform backup, recovery, and applying upgrades and patches to a vast set of Kubernetes components.

Another hurdle can come up when performing a set of operations or defining a particular state from a central pane of glass. Kubernetes allows you to declare a configuration or set up instructions for the target part and set up the desired state for pods or interconnection of pods. During this process, if any error occurs, a skilled resource is required to understand the problem and the location of the error.

Conclusion

Kubernetes launched in 2014. In 5 years, it has slowly evolved to be adopted in mainstream IT infrastructure. As enterprises are taking Kubernetes into production, infrastructure integration and security are identified as major bottlenecks to implementation and deployment. While introducing Kubernetes as a key platform for digital transformation, enterprise leaders need to set up a good plan initially and build a properly-knowledgeable pool of resources for managing day 1 and day 2 operations. For larger Kubernetes deployment within enterprises, it is highly recommended to use an opt-out solution that will not result in wastage of the amount of time and cost.