Interview with Kubernetes Contributor Lei (Harry) Zhang on CRI Shimv2 and Cloud‑Native Trends

The article introduces the upcoming GIAC Global Internet Architecture Conference in Shanghai (Nov 23‑24) and notes that Lei (Harry) Zhang, a Kubernetes core maintainer focusing on the Container Runtime Interface (CRI) and Shimv2, will be a speaker.

Zhang explains that CRI is the stable plugin mechanism linking Kubernetes with container runtimes such as Docker and containerd, while Shimv2 extends this by providing a standard interface between container runtimes (Docker, containerd) and OCI runtimes (runC, KataContainers, gvisor), enabling a single Kubernetes node to manage multiple runtime types.

He highlights the advantages of Shimv2: greater flexibility for users to choose different runtimes per workload, facilitating security‑focused containers and diverse execution environments.

Discussing the broader container landscape in 2018, Zhang points out that the most significant shift was the move toward plugin‑based and interface‑driven architectures, which pushed innovation up to Serverless and Service‑Mesh layers, giving rise to projects like Knative.

Regarding KubeCon Shanghai 2018, he notes that the event featured the richest set of end‑user case studies to date, with many internet companies customizing Kubernetes through plugins, illustrating the ongoing “democratization” of the platform at internet scale.

Zhang also shares his experience authoring a 40‑lecture series on Kubernetes for the GeekTime platform, emphasizing that consistent knowledge accumulation, not last‑minute effort, is key, and that interacting with frontline engineers provides the best insight into technology adoption.

On the dual roles of technical evangelism and development, he argues that open‑source engineers must master both, describing how in the West dedicated evangelism teams handle outreach, whereas in China engineers often wear both hats, which can limit effectiveness.

The article concludes with logistical details about the conference, the Cloud Native track, and a call for readers to attend and explore the full agenda.