Insights from Lingque Cloud Engineers on Six Years of Kubernetes Adoption
In this interview, senior engineers from Lingque Cloud share how their company adopted Kubernetes six years ago, discuss the evolution of the platform, their contributions to the open‑source community, and their expectations for the future of cloud‑native technologies.
2020 marks the sixth anniversary of Kubernetes, and the community celebrated with various events worldwide, highlighting its growth into one of the largest open‑source projects and a core component of cloud‑native strategies across industries.
Lingque Cloud, an early adopter of Kubernetes, interviewed five long‑time engineers to recount their experiences with the technology.
Q1: When did your company start moving to Kubernetes and what memorable discussions occurred during the evaluation? The team received its first Kubernetes project at the end of 2016 for a large securities client, transitioning from Mesos under strong client demand, which led to a successful private‑cloud deployment and high client satisfaction.
Engineers noted that early Kubernetes felt uncertain and immature, but after extensive community effort and internal preparation, Kubernetes won the container‑orchestration battle in early 2017, prompting rapid adoption.
Q2: What was your first impression of Kubernetes and when did you realize its power? Engineers described a two‑level mastery: basic operational use (e.g., passing CKA) and deep involvement such as source‑level extensions and community contributions. Their products added fixed IP, network tenancy, TLS, and traffic‑control features on top of Kubernetes.
They observed that by 2017 Kubernetes had matured, focusing on stability and extensions like CRDs and APIs, driven by Google’s vision and CNCF promotion.
Q3: When did you start engaging with open‑source communities and how do you contribute? Participation began with Docker and deepened with Kubernetes, leading to contributions such as Kube‑OVN. The team collaborates with partners like Intel and adopts community‑driven solutions for custom controllers, CRDs, and ecosystem integration.
Q4: Which product or version release left the strongest impression? The first CaaS platform was highlighted for its pioneering container hosting and CI/CD capabilities, setting a foundation for later ACP and ACE platforms that emphasize stability, rich feature sets, and native Kubernetes integration.
Q5: What are your thoughts and expectations for Kubernetes after six years? Engineers compare Kubernetes to Linux, emphasizing that the exciting part lies in applications built on it. They foresee continued ecosystem consolidation (e.g., OpenTelemetry, GitOps tools) and stress the need for more diverse solutions beyond dominant projects like Prometheus and Istio.
Overall, the interview reflects on Kubernetes’s journey from a nascent project to a mature, extensible PaaS framework that drives modern cloud‑native development.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Cloud Native Technology Community
The Cloud Native Technology Community, part of the CNBPA Cloud Native Technology Practice Alliance, focuses on evangelizing cutting‑edge cloud‑native technologies and practical implementations. It shares in‑depth content, case studies, and event/meetup information on containers, Kubernetes, DevOps, Service Mesh, and other cloud‑native tech, along with updates from the CNBPA alliance.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
