What CTOs need to know about containers and Kubernetes

Cloud native applications and microservices are crucial for the smooth operation of any modern business. However, tech executives cannot simply purchase ready-made solutions or migrate legacy infrastructure into cloud native architectures without careful planning.Engineers require appropriate tools, effective teams, and specialized skills, though determining which tools to acquire, implement, and how to evaluate their ROI can be challenging.

According to the Gartner report titled “Gartner® Report: A CTO’s Guide to Navigating the Cloud-native Container Ecosystem,” containers and Kubernetes have become key technologies for modernization and for developing cloud native applications. By 2027, over 90% of worldwide organizations will deploy containerized applications in production, a steep rise from less than 40% in 2021.

The report further notes, “enterprises face challenges in accurately measuring the ROI of their cloud native investments and in creating the right organizational structure for it to flourish.”

Here’s what enterprises should understand about the primary functions of containers and Kubernetes, and how they facilitate the operation of cloud native structures.

Containers are a technology that enables developers to bundle an application with all its dependencies into a single package, ensuring it runs consistently across any system supporting containerization. They provide isolation, enhance portability, and are more efficient than traditional virtual machines because they share the host system’s kernel while operating in a separate environment.

This makes containers ideal for scalable microservices architectures and simplifies the development, testing, and deployment pipeline, reducing compatibility issues across different environments.

Kubernetes is an open-source platform designed to automate the deployment, scaling, and operation of containerized applications. It handles scheduling and manages workloads based on user-defined parameters, thus enhancing resource utilization and maintaining availability.

These technologies are primarily utilized for microservices, application portability, and minimizing lock-in risks. They facilitate DevOps workflows and the modernization of legacy applications. Any business opting to adopt cloud native methods or upgrade its infrastructure needs to incorporate both containers and Kubernetes.

Gartner outlines the optimal uses for containers and Kubernetes, which include:

• Minimal external application dependencies.
• Container images for the underlying application’s infrastructure and platforms.
• Needs for rapid elasticity and frequent code changes.
• A vendor-supported image for any commercial off-the-shelf (COTS) software deployments.

The majority of container images are derived from open source projects. A container image comprises the static file containing all executable code needed to generate a container within a computing system.

“While some COTS ISVs [independent software vendors] strategically provide strong support for Kubernetes, such as IBM, many COTS ISVs haven’t supported yet — especially in Windows-based or enterprise business applications. You should review container support strategy and roadmaps of their strategic COTS ISVs,” the authors write.

Moreover, Gartner observes an increase in vendors developing container support and “more ISVs are enabling deeper integrations with containers/Kubernetes than just providing container images.”

The report highlights that AWS Marketplace for Containers has 524 container-related entries as of February 2022, 64% up from 320 in February 2020.

The industry trends surrounding Kubernetes and containers include support for stateful applications, VM convergence, edge computing, serverless technologies, and automating application workflows.

The synergy of open source and commercial applications for Kubernetes and containers offers several deployment choices for organizations:

Containers provide numerous benefits for firms adopting cloud native architectures. They enable quick application development and deployment, consistent environments, and immutability.

Since Kubernetes operates atop container technology, it provides extensive flexibility.

According to Gartner, “Kubernetes is supported by a huge ecosystem of cloud providers, ISVs and IHVs [independent hardware vendors]. This API and cross-platform consistency, open-source innovation and industry support offers a great degree of flexibility for CTOs.”

The complexity of the platform is a crucial consideration for CTOs and IT managers, especially since containers and Kubernetes may not be suitable for all scenarios. These technologies are most effective in dynamic, scalable settings and may introduce complexity when used to manage static, COTS applications.

Two key elements of successful container and Kubernetes deployment is ensuring the availability of competent teams and the necessary skills to manage and operate the technology. Organizations should invest in various primary and supportive roles that encompass security, platform operations, reliability engineering, and build and release engineering. These roles are vital for securing, reliably managing, and consistently developing Kubernetes deployments across the organization.

The development team is responsible for coding, designing applications, implementation, testing, and managing the source code.

A platform engineering team is tasked with selecting, installing, configuring, and administering platforms. They should also maintain base images, integrate the DevOps pipeline, enable self-service for developers, automate container provisioning, and handle capacity planning and workload isolation.

Reliability engineers focus on security, monitoring, and performance to ensure application resiliency. They are tasked with debugging, documenting production issues, and managing incidents and responses.

Finally, the build and release engineering team is responsible for selecting the CI/CD deployment pipeline, developing templates for new services, training development teams, and creating dashboards to track efficiency and productivity.

“Ensuring ROI by building a thorough business case is important to validate that you aren’t investing in containers and Kubernetes purely because it is a shiny new technology. Organizations need to take a realistic view of the costs incurred and potential benefits,” the report authors write.

The measurable cost benefits of using containers include:

1. Developer productivity: Containers streamline the development process, enabling developers to focus more efficiently on coding rather than dealing with environment inconsistencies.
2. Agile CI/CD environment: Containers facilitate continuous integration and deployment, ensuring consistent environments across development, testing, and production phases, which enhances agility.
3. Infrastructure efficiency gain: Containers help optimize resource usage, which can lead to significant savings on infrastructure costs.
4. Reduced operational overhead: By standardizing operations across various development and production environments, containers simplify management tasks and reduce the cost of operations.

However, there are potential costs associated with containers that could offset these benefits:

1. CaaS/PaaS license fees: Ongoing expenses for using container-as-a-service or platform-as-a-service offerings.
2. Additional software licenses: Costs for necessary security, automation, and monitoring tools to maintain and enhance container environments.
3. Infrastructure investment costs: Initial expenditures required for setting up infrastructure capable of supporting containers.
4. Hiring new staff: The expenses related to recruiting and training personnel specialized in managing containerized environments.
5. Professional implementation services: Costs for expert services to ensure the container setup is optimized and functioning correctly.

Organizations must carefully weigh these costs against the benefits to assess the overall ROI of adopting container technology.

The Gartner authors recommend that technology leaders should:

• Establish a strong business case: Before scaling Kubernetes environments, ensure there is a solid business case. This involves identifying relevant use cases and fostering a DevOps culture within the organization, which supports rapid development and deployment practices.
• Form a dedicated platform team: Create a team responsible for curating platform selection, standardizing and automating DevOps functions. This team should work closely with developers to promote and support cloud native architectures, ensuring that the infrastructure aligns with the organizational goals and software development practices.
• Opt for packaged solutions or managed services: Instead of a DIY approach, choose packaged software distributions or cloud-managed services for production deployments. These solutions should integrate various technology components, streamline lifecycle management, and provide capabilities for managing services across multiple clouds. This approach can reduce complexity and enhance scalability and reliability.
• Measure and communicate benefits accurately: It is crucial to quantify and communicate the benefits of Kubernetes and container adoption effectively. This should include technical metrics such as software development velocity, release success rate, and operational efficiency improvements. Additionally, business metrics like revenue growth and customer satisfaction should also be monitored and reported to demonstrate the value and impact of the technology implementations.

Containers and Kubernetes provide a solid foundation for organizations and IT leaders to adopt cloud native architectures and update legacy systems. For successful deployment and optimal ROI, ensure the right applications and skilled teams are in place.