From Docker to Serverless Kubernetes: Tracing the Cloud‑Native Evolution

“伴随着云原生的发展，从早先的单机版 Docker 到 Kubernetes 的编排领域的一统江湖，再到云上托管 Kubernetes，技术风雨变化。今天我们就沿着历史的脉络，一起看一下 Serverless Kubernetes 的发展史。”

Story Starts with Docker

The narrative begins with Docker, but we must also acknowledge the pioneering IaaS efforts and early cloud computing roadmaps.

Over a decade ago, cloud services were categorized into three layers:

IaaS: Infrastructure as a Service, providing virtual machines and basic resources.

PaaS: Platform as a Service, offering middleware and runtime services on demand.

SaaS: Software as a Service, delivering applications such as email.

As the stack moved from IaaS to PaaS, developers and operators focused less on raw infrastructure and more on business logic.

Specialists handle specialized tasks, allowing startups to avoid building data centers and instead concentrate on product development.

After years of growth, IaaS matured (ECS, VPC, EBS), while PaaS lagged. In 2008, Google App Engine attempted to abstract away infrastructure, but adoption was limited. Open‑source PaaS platforms like Cloud Foundry and OpenShift also struggled with compatibility.

Docker’s 2013 debut changed the game: a single command could launch a service, packaging code and dependencies into portable images that run consistently across environments.

Docker’s success stemmed from simplicity rather than novel technology—kernel features like cgroups and namespaces already existed. Docker’s “Build once, Run anywhere” model accelerated container adoption.

Kubernetes Secures Its Position

Docker began as a single‑node solution; large‑scale deployments required orchestration, similar to OpenStack for VMs.

Early container orchestration tools (Mesos, Swarm) remained tied to IaaS thinking. Kubernetes emerged, backed by Google and inspired by Borg, offering native concepts like ReplicaSets and Services.

Docker’s own Swarm attempted to compete but eventually ceded ground to Kubernetes, which became the de‑facto standard.

Kubernetes abstracts resource management via extensible interfaces (CRI, CNI, CSI, Device Plugins, CRDs), evolving into a cloud operating system with a rich ecosystem of cloud‑native components.

Public‑Cloud Managed Kubernetes

Despite Kubernetes’ dominance, its operation remains complex. Public clouds responded with managed services, e.g., Alibaba Cloud Container Service for Kubernetes (ACK) launched in 2017.

ACK handles control‑plane installation and maintenance, using ECS or bare metal as compute nodes. Users obtain a kubeconfig to manage clusters via kubectl or APIs.

Scaling is as simple as adjusting ECS count; new instances auto‑register. ACK also supports one‑click version upgrades and plugin management, shifting operational burdens to the cloud and enabling minute‑level scaling.

From Managed Nodes to Serverless Pods

Public clouds emphasize cost efficiency; unlike private clouds with fixed infrastructure, they offer pay‑as‑you‑go models.

For bursty workloads—e.g., an online education platform needing tens of thousands of pods during peak hours—traditional node‑based scaling can be cumbersome.

AWS introduced Fargate, enabling pod‑level billing without managing nodes. Alibaba followed with Elastic Container Instance (ECI), where each ECI is a pod hosted by the cloud.

Alibaba offers two serverless Kubernetes approaches: ASK (Alibaba Serverless Kubernetes) and ACK + Virtual Node. In ASK, Virtual Nodes act as limitless compute resources, managing ECI lifecycles while appearing as regular nodes to Kubernetes.

Virtual Nodes can coexist with standard ACK nodes, allowing long‑running tasks on ECS while dispatching bursty jobs to ECI, achieving optimal cost.

ECI has been adopted by many internet and AI companies. Future articles will explore typical migration challenges and solutions.

In summary, the evolution from Docker to serverless Kubernetes illustrates how foundational cloud technologies converge into a cloud‑native operating system, driving down operational costs and allowing developers to focus on business value.