OpenEverest at KubeCon + CloudNativeCon China 2026: the Shanghai recap

OpenEverest at KubeCon + CloudNativeCon China 2026: the Shanghai recap

By Sergey Pronin Sergey Pronin

We finished the OpenEverest Asian tour in Shanghai with KubeCon + CloudNativeCon China. In practice it was more than a single KubeCon — it was a blend of events: KubeCon + CloudNativeCon, OpenInfra Summit, and the PyTorch Conference all under one roof. Because of that mix, and the AI hype driving the agenda, the talks were extremely diverse and not always tied to cloud native. There were plenty of conversations about GPU management, machine learning, and training large language models with PyTorch and its surrounding ecosystem.

But let’s take it one step at a time. Below is my take on the conference.

Talks

If I had to summarize the schedule in one sentence: this was Kubernetes as the operating system for AI production, co-hosted by the PyTorch Foundation. By my count, roughly 67 of the 95 sessions — about 70% — were AI-related in some way.

Only around eight talks were pure, traditional cloud-native infrastructure: Cilium, the Envoy dataplane, runc security, OpenStack migrations, Karmada updates, bootc/Ironic, KubeEdge, and impersonation controls. And even most of the “infrastructure” talks justified themselves through AI workloads — DRA for GPU scheduling, Kata for agent sandboxing, Dragonfly for model distribution. AI was not just a track; it was the gravitational center of the whole event.

A few patterns stood out to me:

  • Huawei was everywhere. They showed up in roughly a dozen slots — keynotes, the Ascend and PyTorch ecosystem, HyperParallel, vLLM/Volcano/KV-cache talks, and lightning talks — and also sponsored the community night and a co-located day.
  • Meta brought serious training content. Four solid talks: 100k-GPU fault tolerance, KernelAgent, PyTorch optimizers, and the Helion CuTe DSL — a strong signal on both NVIDIA alternatives and training efficiency.
  • Banks are now presenting like hyperscalers. China Merchants Bank alone had three sessions — a Tidal autoscaling keynote, digital employees at scale, and LLM training-as-a-service — a bank talking about GPU scheduling the way a cloud provider would.
  • vLLM was the center of gravity. More than eight sessions across the two days covered PD disaggregation, KV cache management, day-0 multi-backend inference, Helion tuning, and TTFT observability.
  • Agentic AI is the clear second wave. Around ten sessions covered agent runtimes, agent sandboxes, agent observability, and agent KV-cache — largely from Ant Group, Alibaba, Red Hat, and ZTE.
  • Alternative accelerators were a recurring theme. Ascend, Cambricon, RISC-V, and “device-agnostic PyTorch” formed a distinctly China-stack narrative. NVIDIA was present, but far from dominant. HAMi was mentioned a few million times during these talks.

It was surprising to see that the majority of the talks were given in Chinese. What surprised me even more was occasionally walking into a session labeled “English” in the schedule, only to find it delivered in Chinese — with English slides. :)

AI was the thread running through every keynote. It was great to see OpenEverest called out during a keynote as one of the interesting CNCF Sandbox projects.

OpenEverest - Blog - OpenEverest during KubeCon Keynote in Shanghai 2026

I also didn’t expect the maintainers track — where I gave my talk — to have such a large room, and it was full every time. That was really good to see.

Chinese projects

Whenever I travel to Asia, it is fascinating to watch how the project landscape shifts. In Japan and Taipei, for example, we noticed that MySQL and its derivatives — MariaDB, TiDB — are more popular than PostgreSQL.

Mainland China was a different world entirely. It runs on its own technologies — names I had heard of but never realized were this widely adopted.

Dragonfly

When I first heard “Dragonfly”, I immediately thought of dragonflydb, the Redis alternative. But it turns out this is a different project: dragonflyoss/dragonfly — a solution for delivering container images, models, and other content efficiently using P2P technology. It has 3.3k stars on GitHub and is extremely popular, especially given the push to speed up LLM serving.

OceanBase

A distributed relational database developed by Ant Group. Their main repository, oceanbase/oceanbase, has 10.3k GitHub stars, with contributions coming mostly from the Chinese community. And it is genuinely popular. On their website they publish a list of customers using it: en.oceanbase.com/customer/home. You’ll spot brands like Xiaomi, Li-Ning, and Alipay, alongside companies such as Trip.com and Vivo.

SGLang

I had heard of SGLang before, but I hadn’t realized how big its community is: almost 2,000 contributors and 35.8k stars on GitHub (sgl-project/sglang). A direct competitor to vLLM, this LLM serving framework is catching up fast. It can’t really be called a “Chinese project” anymore — its adoption has spread well beyond China and Asia — but the majority of contributions still come from China and companies based there.

Project pavilion

For me, the second day of the conference was all about the project booth, where I was the sole representative of OpenEverest. The project pavilion was in the main hall, right next to the big booths, so foot traffic was strong. It was a great opportunity to spread the word about OpenEverest, explain its value, and share the direction we’re taking it. I was glad to see people interested in trying out the KServe provider in OpenEverest.

One unusual conversation involved me explaining what Kubernetes is — a little surprising at a CloudNativeCon. :)

Overall, I really enjoyed the community, the new people I met, and the connections I made. Worth doing again next year, for sure.


Didn’t catch us in Shanghai, but want to connect?

Join Slack Star the Repo

See Also