Why KubeSphere’s Sudden Open‑Source Shutdown Shook the Cloud‑Native Community

Former Star Project: What Is KubeSphere

KubeSphere was launched in 2018 by Qingyun Technology as an open‑source Kubernetes distribution and quickly became one of the most watched projects in China, claiming “100% open source, built by the community.” It adds enterprise‑grade features such as DevOps pipelines, micro‑service observability, an application store, and multi‑tenant support, and provides an intuitive web console that lowers the barrier to using container clouds.

Because of its near‑zero‑configuration installation and full‑stack capabilities, KubeSphere attracted users from hundreds of countries and earned over 16 k stars on GitHub.

Background: Supply Cut

On August 1 2025 the KubeSphere team silently posted on GitHub: “Effective immediately, the download links for the open‑source edition are suspended and free technical support is discontinued.” The announcement came without any prior issue notice or community discussion, and the changes took effect overnight.

Users discovered that deployment scripts could no longer pull images because the official image repository was removed, causing nodes to fail to update and production environments to break. The abrupt removal of download links and images was a classic “supply cut” rather than a gradual transition.

Angry users opened GitHub issues demanding at least a temporary rollback or backup of the images. The community suggested handing over maintenance to volunteers, while many vented their frustration with profanity. The maintainers locked the discussion area and closed issue comments, turning the situation into a control‑by‑the‑vendor scenario.

Community members expressed deep disappointment. A Reddit user lamented, “Another open‑source project has died; it feels like the rug was pulled out from under us.” Others mocked the move, saying they were glad they never used KubeSphere and avoided the “open‑source bait” trap.

License Change and Trust Crisis

Although the source code remains on GitHub, KubeSphere is no longer a true open‑source project. In 2024 Qingyun switched the license to Apache 2.0 with additional clauses that prohibit any unauthorized commercial use, including providing the software as a service, integrating it into commercial products, or even removing the logo. These extra restrictions make the license incompatible with the Open Source Definition, turning the project into “source‑available” rather than truly open source.

This license manipulation shattered community trust. The sudden “hard cut” of essential resources is akin to pulling the power plug from users’ production systems, a classic Rug Pull that erodes years of goodwill in a single night.

Why Qingyun Abandoned Open Source? Competition and Profit Dilemma

Qingyun cited competitive pressure as a trigger: rivals were leveraging KubeSphere’s code to build their own solutions, thereby infringing on Qingyun’s investment. The company also faced revenue and survival pressure; as a publicly listed firm, it must satisfy shareholders, and the open‑source team had become a cost center with declining profitability.

Similar to other cases where companies altered licenses after gaining market share (e.g., Elastic, Redis, MongoDB), Qingyun felt the open‑source edition had become a “free lunch” for competitors, prompting a shift to a fully commercial model.

Pseudo Open‑Source Strategy That Leads Users Away

Qingyun first used an Apache 2.0 license to attract users and build community trust, then quietly added restrictive clauses in 2024, and finally shut down the open‑source edition in 2025 to monetize the product. This mirrors a broader industry pattern where open source is used as a marketing funnel and later abandoned.

Old Feng’s Comments

Old Feng maintains the open‑source PostgreSQL distribution Pigsty, which includes over 200 extensions and a community of nearly 3 000 users. He argues that true open‑source sustainability relies on either well‑funded individuals or societies with strong safety nets, and that companies should treat open source as a gift to the community rather than a mere acquisition channel.

He notes that Pigsty has become a key part of the PostgreSQL ecosystem, with downstream vendors and cloud providers relying on it, illustrating how genuine open‑source contributions can create lasting value.

Alternative Solutions

While KubeSphere’s open‑source edition is gone, alternatives such as SealOS are emerging to fill the gap for users seeking a community‑driven Kubernetes distribution.

Reference Reading

Announcement of KubeSphere’s open‑source adjustment

Understanding KubeSphere’s “turnaround” and its poor farewell

The Register: Another one bites the dust as KubeSphere kills open source edition

Night Sky Book #62: Pseudo Open‑Source Strategy that Lures Users