Enterprises have been migrating from purely private cloud infrastructures toward hybrid cloud models for several years. The flexibility of hybrid cloud is well established, but CTOs quickly discovered that most hybrid cloud solutions fall short when it comes to complete infrastructure management across distributed networks. Tools like VMware and OpenStack have attempted to address these gaps, but a new generation of open-source tooling — Docker and Kubernetes — is redefining how application deployment works at scale.
What Docker Brought to Enterprise Deployment
Docker, introduced in 2013, fundamentally changed how developers and operations teams think about packaging and shipping software. Before containers, applications were tightly coupled to the environment they were built in, making portability across cloud, on-premises, and hybrid environments a constant source of friction.
Gahl Levy, Product Manager at DataStax, responsible for the company’s container and Kubernetes product development, described the shift this way:
“Docker in itself was a game-changer when it was released — it made it simpler and easier to deploy applications in a platform-agnostic way across an enterprise’s infrastructure. Rather than tending to individual server needs, DevOps personnel can focus on containerising their applications. They then know their applications will work in the same manner across cloud, on-premise and hybrid cloud environments.”
Gahl Levy, Product Manager, DataStax
A Docker container bundles all runtime assets — application code, system tools, libraries, and configuration — into a single portable unit. Unlike virtual machines, containers share the host operating system kernel, making them significantly lighter and faster to start. This portability makes them a natural fit for hybrid cloud architectures where workloads span multiple platforms.
CIO Awareness of Docker: Where Things Stand
To understand how CIOs are approaching Docker and container architectures, Silicon spoke with Marco Palladino, Co-founder and CTO of Kong, described as a widely adopted open-source API platform.
“Docker, a technology born in 2013, is now popular enough to be recognised by the large majority of CIOs, especially within the technology, banking and financial sectors. What varies is the depth of expertise and understanding of the technology. However, after more than half a decade, it’s safe to say that the awareness of Docker has been established.”
Marco Palladino, Co-founder and CTO, Kong
Awareness, however, does not always translate into deep adoption. Many organisations are still evaluating how to integrate containerised workloads alongside their existing infrastructure.
How Kubernetes Enables Hybrid Cloud Deployments
Kubernetes extends what Docker started by providing orchestration — automated scheduling, scaling, self-healing, and management of containerised workloads across clusters of machines. Crucially, it abstracts away vendor-specific cloud APIs, making it a strong enabler of hybrid and multi-cloud strategies.
“Kubernetes breaks down the dependency on vendor-specific APIs — like the AWS API, the Azure API and so on — and replaces it with a portable, platform-agnostic API, therefore making the technology a perfect fit in hybrid environments. Kubernetes is by no means a simple technology, and it shouldn’t be seen as a panacea for existing infrastructural or architectural problems. The organisation must invest resources to build a capable R&D team to benefit the most from new, modern tooling.”
Marco Palladino, Co-founder and CTO, Kong
This vendor-neutrality is one of Kubernetes’ most strategically important properties. Organisations that build on Kubernetes gain the flexibility to move workloads between AWS, Azure, Google Cloud, and on-premises data centres without rewriting their deployment configuration.
Key Pressure Points for CIOs Managing Docker at Scale
Adopting containers does not eliminate operational complexity — it shifts it. Palladino identified fragmentation as the primary challenge organisations face when containerising at scale:
“While some workloads may be running well in Docker and modern container orchestration platforms like Kubernetes, it may still be hard to run legacy applications in these environments, effectively creating a two-speed highway within the organisation that can cause fragmentation over time. It’s important that there is a plan in place to reconcile this fragmentation by having a strategy that allows CTOs to connect, secure, monitor and deploy both modern applications and legacy applications across traditional environments and simultaneously on containers.”
Marco Palladino, Co-founder and CTO, Kong
Common pressure points organisations report when scaling Docker deployments include:
- Legacy application compatibility: Not every existing workload is straightforward to containerise, particularly stateful applications and those with complex dependencies.
- Security and secrets management: Containers introduce new attack surfaces that require dedicated tooling and practices.
- Networking complexity: Service-to-service communication across container clusters adds latency and demands careful architecture.
- Vendor lock-in risk: Relying heavily on a specific cloud provider’s managed Kubernetes service can reintroduce the lock-in that containers were meant to avoid.
- Team capability gaps: Kubernetes has a steep learning curve. Organisations that underinvest in training and tooling often struggle to extract its full value.
Are Virtual Machines Obsolete?
A common misconception is that containers replace virtual machines. Palladino clarified the relationship:
“Virtual machines are still required to run Docker containers because that’s where container orchestration platforms like Kubernetes ultimately run. I wouldn’t consider Docker a replacement for VMs. Docker is an additional abstraction layer that sits above virtual machines and allows them to more efficiently manage resources while providing a standardised distribution for any workload across any cloud and data centre. Because of this, I see Docker as the future of the hybrid cloud.”
Marco Palladino, Co-founder and CTO, Kong
In practice, Kubernetes cluster nodes are typically VMs (or bare-metal servers). Docker adds a layer on top, enabling fine-grained workload isolation and portability without replacing the underlying compute infrastructure. The two technologies are complementary, not competing.
Docker, Kubernetes, and Microservices Architecture
One of the most significant architectural impacts of Docker and Kubernetes is the acceleration of microservices adoption. By making it straightforward to package, deploy, and independently scale individual services, containers lower the operational barrier to breaking apart monolithic applications.
“By allowing applications to be quickly packaged, distributed and deployed across hybrid and multi-cloud environments, Docker and Kubernetes make it easier to build decoupled and distributed applications that can run anywhere. However, as we decouple our systems into microservices, we enable more API communication over a network across our applications. Performance and security become even more critical to encrypt, secure and accelerate the flow of information across our services.”
Marco Palladino, Co-founder and CTO, Kong
Palladino also warned against depending too heavily on cloud-native vendor tooling for security and traffic management within containerised environments:
“While Docker and Kubernetes allow us to deploy our workloads across multiple clouds and platforms, it’s important that we do not rely too much on cloud vendor solutions to secure and monitor our traffic. In the long term, that creates inconsistencies and fragmentation. Instead, we want to adopt platform-agnostic technology that can be deployed within our Kubernetes cluster that consolidates how we manage and operate our services across every environment, across every cloud.”
Marco Palladino, Co-founder and CTO, Kong
A New DevOps Development Model
For DevOps teams, Docker and Kubernetes are not just deployment technologies — they represent a shift in how software is conceived and built. The container model encourages platform-agnostic, distributed thinking from the earliest stages of development.
“Docker and its ecosystem provide a platform-agnostic, distributed way of thinking about our applications. By doing so, they make it easier to build decoupled systems that move away from legacy monolithic architectures. While adopting modern architectures will increase team productivity by lowering the friction to create, package and distribute software, it’s essential also to address new challenges — including data security, reducing performance latency, and being comfortable running large-scale, decoupled and distributed systems across multiple platforms.”
Marco Palladino, Co-founder and CTO, Kong
The Future of Containerised Applications
Looking ahead, containers are expected to become smaller, more standardised, and more deeply integrated with emerging paradigms such as serverless computing and Functions-as-a-Service (FaaS).
“Containers will get smaller and nimbler. There will be more of a focus on standardised base images. These can make containers lighter weight and allow underlying operating systems to focus on optimisations for those base image types.”
Lee Atchison, Senior Director, Cloud Architecture, New Relic
Palladino offered a longer-term perspective on where containerisation is heading:
“We will be able to take full advantage of containerised applications when we also provide an enabling path for legacy application and brownfield use cases to transition to these modern architectures. Containerised applications will become the foundation — the primitive — that we work with to build more complex, self-healing systems over time. Serverless and FaaS are also interesting technology trends because they paint a vision of the future where we will not need containers at all.”
Marco Palladino, Co-founder and CTO, Kong
Scott McCarty, Principal Product Manager for Containers at Red Hat, noted the trajectory of enterprise adoption:
“We’ve seen a real expansion in awareness around containers since 2014. The adoption of containers was a bottom-up movement, similar to Linux. It started with pioneering developers and systems administrators looking for better management of deployments. In the last 18–24 months, it has become the strategic direction for large institutions, and many more CIOs are paying attention.”
Scott McCarty, Principal Product Manager, Containers, Red Hat
Key Takeaways for DevOps and Engineering Leaders
- Containers complement VMs — they do not replace them. Kubernetes runs on top of virtual machines or bare-metal nodes. Plan your infrastructure accordingly.
- Kubernetes abstracts cloud vendor APIs, making it a strong foundation for genuine hybrid and multi-cloud portability.
- Fragmentation between legacy and containerised workloads is the most common operational pain point at enterprise scale. A deliberate migration strategy is essential.
- Microservices bring new API and security challenges. Invest in platform-agnostic tooling for traffic management, observability, and security rather than relying solely on cloud-provider native solutions.
- Team investment is non-negotiable. Kubernetes is complex. Organisations that build strong internal R&D capability extract significantly more value from the ecosystem.
- Serverless and FaaS are the next frontier, potentially abstracting containers away from developers entirely in specific workload categories.
Docker and Kubernetes are no longer emerging technologies — they are the operational backbone of modern application deployment. For CIOs and CTOs navigating hybrid cloud strategy, understanding how to leverage them effectively, while managing the complexity they introduce, is now a core competency.