<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by KubeSphere on Medium]]></title>
        <description><![CDATA[Stories by KubeSphere on Medium]]></description>
        <link>https://medium.com/@kubesphere?source=rss-a29a021fa88d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*xjnHNbGOzvSQzlRcmQ9hCg.png</url>
            <title>Stories by KubeSphere on Medium</title>
            <link>https://medium.com/@kubesphere?source=rss-a29a021fa88d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 03:33:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kubesphere/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Kubernetes v1.36 “Haru” Is Here: Spring Returns, Growth Begins, and Stability Takes Center Stage]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kubesphere.medium.com/kubernetes-v1-36-haru-is-here-spring-returns-growth-begins-and-stability-takes-center-stage-c16485f1eb5b?source=rss-a29a021fa88d------2"><img src="https://cdn-images-1.medium.com/max/701/0*Nbgv9gf1kwRwj8ex.png" width="701"></a></p><p class="medium-feed-snippet">In April across the Northern Hemisphere, mountains begin to wake and cherry blossoms still linger. At this time of renewal, the Kubernetes&#x2026;</p><p class="medium-feed-link"><a href="https://kubesphere.medium.com/kubernetes-v1-36-haru-is-here-spring-returns-growth-begins-and-stability-takes-center-stage-c16485f1eb5b?source=rss-a29a021fa88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kubesphere.medium.com/kubernetes-v1-36-haru-is-here-spring-returns-growth-begins-and-stability-takes-center-stage-c16485f1eb5b?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c16485f1eb5b</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Fri, 24 Apr 2026 09:13:46 GMT</pubDate>
            <atom:updated>2026-04-24T09:13:46.320Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Cloud Native Weekly: A Look Ahead to Kubernetes v1.36]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kubesphere.medium.com/cloud-native-weekly-a-look-ahead-to-kubernetes-v1-36-53e01bf5d1cf?source=rss-a29a021fa88d------2"><img src="https://cdn-images-1.medium.com/max/990/1*aF01SrOYCwhEQBNoFVxFgw.png" width="990"></a></p><p class="medium-feed-snippet">Cloud Native Highlights</p><p class="medium-feed-link"><a href="https://kubesphere.medium.com/cloud-native-weekly-a-look-ahead-to-kubernetes-v1-36-53e01bf5d1cf?source=rss-a29a021fa88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kubesphere.medium.com/cloud-native-weekly-a-look-ahead-to-kubernetes-v1-36-53e01bf5d1cf?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/53e01bf5d1cf</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Tue, 14 Apr 2026 09:59:33 GMT</pubDate>
            <atom:updated>2026-04-14T09:59:33.213Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Cloud Native Weekly: Kubernetes 1.36 Is Coming]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kubesphere.medium.com/cloud-native-weekly-kubernetes-1-36-is-coming-6608224dcbaf?source=rss-a29a021fa88d------2"><img src="https://cdn-images-1.medium.com/max/966/1*3cJgYAOa3nO3IRi4JmR6XQ.png" width="966"></a></p><p class="medium-feed-snippet">Cloud Native Highlights</p><p class="medium-feed-link"><a href="https://kubesphere.medium.com/cloud-native-weekly-kubernetes-1-36-is-coming-6608224dcbaf?source=rss-a29a021fa88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kubesphere.medium.com/cloud-native-weekly-kubernetes-1-36-is-coming-6608224dcbaf?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6608224dcbaf</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Thu, 19 Mar 2026 03:36:12 GMT</pubDate>
            <atom:updated>2026-03-19T03:36:12.903Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why managing Kubernetes still feels broken in 2026]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kubesphere.medium.com/why-managing-kubernetes-still-feels-broken-in-2026-9aff5aa8a5c2?source=rss-a29a021fa88d------2"><img src="https://cdn-images-1.medium.com/max/1376/1*hzptcMnbuqVeIjWk4QYUZg.jpeg" width="1376"></a></p><p class="medium-feed-snippet">I&#x2019;ve been working with Kubernetes for a while now, and despite how powerful the ecosystem has become, I can&#x2019;t shake the feeling that&#x2026;</p><p class="medium-feed-link"><a href="https://kubesphere.medium.com/why-managing-kubernetes-still-feels-broken-in-2026-9aff5aa8a5c2?source=rss-a29a021fa88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kubesphere.medium.com/why-managing-kubernetes-still-feels-broken-in-2026-9aff5aa8a5c2?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9aff5aa8a5c2</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Fri, 13 Mar 2026 09:22:21 GMT</pubDate>
            <atom:updated>2026-03-13T09:22:21.776Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Cloud Native Weekly: What Is Docker? The Starting Point of the Container Revolution]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kubesphere.medium.com/cloud-native-weekly-what-is-docker-the-starting-point-of-the-container-revolution-116effe75774?source=rss-a29a021fa88d------2"><img src="https://cdn-images-1.medium.com/max/1800/1*yuFL_sn-1OsJcoo9pTOXdg.png" width="1800"></a></p><p class="medium-feed-snippet">Cloud Native Highlights</p><p class="medium-feed-link"><a href="https://kubesphere.medium.com/cloud-native-weekly-what-is-docker-the-starting-point-of-the-container-revolution-116effe75774?source=rss-a29a021fa88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kubesphere.medium.com/cloud-native-weekly-what-is-docker-the-starting-point-of-the-container-revolution-116effe75774?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/116effe75774</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 10:43:17 GMT</pubDate>
            <atom:updated>2026-03-12T10:43:17.671Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Kubernetes Is Powerful — But Painful for Small Teams]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kubesphere.medium.com/kubernetes-is-powerful-but-painful-for-small-teams-73463aabf230?source=rss-a29a021fa88d------2"><img src="https://cdn-images-1.medium.com/max/1376/1*COWb1ylb0RE12laGVOcvDQ.jpeg" width="1376"></a></p><p class="medium-feed-snippet">Kubernetes has become the default infrastructure layer for modern cloud-native applications. It powers large-scale platforms at companies&#x2026;</p><p class="medium-feed-link"><a href="https://kubesphere.medium.com/kubernetes-is-powerful-but-painful-for-small-teams-73463aabf230?source=rss-a29a021fa88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kubesphere.medium.com/kubernetes-is-powerful-but-painful-for-small-teams-73463aabf230?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/73463aabf230</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Fri, 06 Mar 2026 02:25:30 GMT</pubDate>
            <atom:updated>2026-03-06T02:25:30.684Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Cloud Native Weekly: New Progress in Unified AI Scheduling & a Major Policy-Engine Upgrade]]></title>
            <link>https://kubesphere.medium.com/cloud-native-weekly-new-progress-in-unified-ai-scheduling-a-major-policy-engine-upgrade-e65fa5db352a?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e65fa5db352a</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 09:31:58 GMT</pubDate>
            <atom:updated>2026-03-02T09:31:58.580Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Native Highlights</h3><h4><a href="https://github.com/volcano-sh/volcano/releases/tag/v1.14.0">Volcano v1.14 Released: Toward a New Era of Unified AI Scheduling</a></h4><p>Volcano is a cloud-native batch / high-performance scheduler on Kubernetes, designed for AI training, big data computing, MPI/HPC workloads, and more. It provides stronger scheduling capabilities such as gang scheduling, queues &amp; fair sharing, and preemption — while remaining natively compatible with the Kubernetes ecosystem. It is a CNCF Incubating project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S53e8WIBY6QYciKU164niA.png" /></figure><p>Volcano v1.14.0 has been released, expanding its AI focus from offline training to new challenges introduced by online inference and AI agents. The release’s key direction is moving toward a “unified scheduling platform” that can cover training, inference, RL, and agent workloads. A headline change is a scalable multi-scheduler architecture with a dynamic node scheduling shard mechanism (Alpha), which computes candidate node pools for different schedulers and enables coordinated scheduling at scale.</p><h4><a href="https://blog.k0sproject.io/posts/k0s-1.35-released/?sessionid=">k0s 1.35: Major Improvements for Windows Node Management &amp; a Storage Backend Overhaul</a></h4><p>k0s is an open-source, lightweight, CNCF-certified Kubernetes distribution focused on a “zero friction” operational experience: it packages core components into a single binary, aiming for minimal host dependencies and simplified installation/upgrade. It supports setups from single-node to production-grade multi-controller/multi-node clusters.</p><p>k0s 1.35 is powered by upstream Kubernetes 1.35.1 and focuses on practical operator improvements. Highlights include more mature Windows node support (closer to Linux feature parity) and a modernized storage backend aimed at better reliability and operator experience.</p><h4><a href="https://kyverno.io/blog/2026/02/02/announcing-kyverno-release-1.17/?sessionid=">Kyverno 1.17: CEL Policies Reach GA, with Performance &amp; Standardization Upgrades</a></h4><p>Kyverno is a Kubernetes-native policy engine that expresses policies as Kubernetes resources, enabling validation, mutation, generation, and cleanup without requiring users to learn a new dedicated policy language. It is also a CNCF Incubating project and promotes “policy as code” for compliance, security, and operational consistency.</p><p>Kyverno 1.17 is positioned as a milestone release: CEL-based policy types are promoted to stable (v1) / production-ready, and the project signals a clear shift away from legacy policy APIs. In particular, the announcement notes that ClusterPolicy and CleanupPolicy are marked as deprecated, starting the countdown toward removal in favor of CEL-based approaches.</p><h3>Technical Practice</h3><h3>Recommended Reading</h3><h4><a href="https://kubernetes.io/blog/2026/02/27/ingress-nginx-before-you-migrate/?utm_source=chatgpt.com">Before You Migrate: Five Surprising Ingress-NGINX Behaviors You Need to Know</a></h4><p>With Ingress-NGINX maintenance ending in March 2026, Kubernetes recommends planning a migration to alternatives such as Gateway API implementations.</p><p>This post explains five “surprising” Ingress-NGINX default behaviors you should understand before migrating, because they can cause outages if you assume other controllers behave the same way:</p><p>Regex matches behave as case-insensitive prefix matches (which may differ from Gateway API implementations).</p><p>The nginx.ingress.kubernetes.io/use-regex: &quot;true&quot; annotation applies to all paths for the same host across all Ingresses handled by Ingress-NGINX.</p><p>nginx.ingress.kubernetes.io/rewrite-target implicitly enables regex behavior (it effectively brings use-regex-like side effects).</p><p>Requests missing a trailing slash may be redirected (301) to the same path with a trailing slash.</p><p>URL/path normalization behaviors can differ; many Gateway API implementations normalize . and .. segments by default, which may impact backends relying on specific URL forms.</p><p>The article also provides Gateway API equivalents (e.g., explicit regex patterns, URL rewrite filters, redirect filters) to preserve the original behavior when needed.</p><h4><a href="https://www.infoq.com/news/2026/02/kubernetes-node-readiness/?utm_source=chatgpt.com">Kubernetes Introduces Node Readiness Controller to Improve Pod Scheduling Reliability</a></h4><p>This report covers a newly introduced Node Readiness Controller (described as an Alpha feature) intended to improve scheduling reliability by making the API server’s view of node readiness more accurate — especially under transient failures such as brief network disruptions between kubelet and the API server. The goal is to reduce inconsistent scheduling decisions and improve workload stability in large or dynamic clusters.</p><h3>Open Source Project Picks</h3><h4><a href="https://github.com/derailed/k9s?utm_source=chatgpt.com">K9s</a></h4><p>K9s is a Kubernetes terminal UI (TUI) that continuously watches cluster resources and lets you quickly navigate, filter, and troubleshoot using keyboard-driven workflows — reducing repetitive kubectl context switching.</p><h4><a href="https://github.com/badlogic/pi-mono?utm_source=chatgpt.com">pi-mono</a></h4><p>pi-mono is a monorepo “AI agent toolkit” that includes a coding-agent CLI, a unified LLM API layer, reusable TUI/Web UI libraries, Slack bot integration, and tooling related to running vLLM inference services (“pods”). It’s useful for building an internal “coding assistant + tooling + deployment” integrated solution.</p><h4><a href="https://github.com/Turbo1123/roubao?utm_source=chatgpt.com">roubao</a></h4><p>roubao is an Android automation assistant built on vision-language models (VLMs): the model interprets screenshots, plans steps, and can execute actions like tapping, swiping, typing, and opening apps. The project emphasizes a native Android approach.</p><h4><a href="https://github.com/obra/superpowers?utm_source=chatgpt.com">Superpowers</a></h4><p>Superpowers is an “agentic skills” framework and workflow for coding agents. It provides a structured development process built on composable “skills” plus strong instructions to ensure agents follow the workflow (e.g., planning, systematic debugging, code review, and reusable skills).</p><h3>About KubeSphere</h3><p>KubeSphere is a container platform built on top Kubernetes with applications at its core. It provides full-stack IT automated operation and streamlined DevOps workflows.</p><p>KubeSphere has been adopted by thousands of enterprises across the globe, such as Aqara, Sina, Benlai, China Taiping, Huaxia Bank, Sinopharm, WeBank, Geko Cloud, VNG Corporation and Radore. KubeSphere offers wizard interfaces and various enterprise-grade features for operation and maintenance, including Kubernetes resource management, <a href="https://kubesphere.io/devops/">DevOps (CI/CD)</a>, application lifecycle management, service mesh, multi-tenant management, <a href="https://kubesphere.io/observability/">monitoring</a>, logging, alerting, notification, storage and network management, and GPU support. With KubeSphere, enterprises are able to quickly establish a strong and feature-rich container platform.</p><p>To stay updated, visit <a href="https://kubesphere.io/">our official website</a> or follow us on <a href="https://twitter.com/KubeSphere">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e65fa5db352a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[KubeSphere 2025 Annual Review]]></title>
            <link>https://kubesphere.medium.com/kubesphere-2025-annual-review-e408e6c5f687?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e408e6c5f687</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Thu, 12 Feb 2026 03:12:20 GMT</pubDate>
            <atom:updated>2026-02-12T03:12:20.982Z</atom:updated>
            <content:encoded><![CDATA[<p>In 2025, the digital transformation wave has entered deep waters. Enterprises are no longer focused on building experimental cloud-native environments; instead, their core demand has shifted toward platforms capable of supporting mission-critical workloads and scaling business value sustainably. This requires both the power to make bold breakthroughs and the control to steadily master the core.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*DgxWumWZ424b-q9-.png" /></figure><p>As an enterprise-grade multi-tenant container platform, KubeSphere is committed to being a reliable partner and a steady vehicle in this transformation journey. By simplifying operational complexity, integrating industry best practices, and delivering production-ready capabilities out of the box, we help global customers manage stable, efficient, and self-controlled application management planes across multi-cloud and heterogeneous environments — accelerating innovation delivery, optimizing resource costs, and ensuring business continuity.</p><p>Looking back over the past year, we not only achieved key breakthroughs in product capabilities, but also witnessed the steady realization of platform value in mission-critical scenarios across industries including finance, government, manufacturing, and education.</p><h3>Product Excellence: Strengthening the Enterprise Foundation</h3><p>In 2025, we continued refining the product through iterative releases, culminating in the launch of v4.2.1 — a milestone that marks a solid step forward toward “exceptional experience and production readiness.” This release and all updates throughout the year focused on addressing the core challenges of large-scale enterprise application management, delivering a more stable and efficient experience across industries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Uq6-tZqIWs7GphHG.png" /></figure><h4>1. Enhanced Unified Management of Heterogeneous Resources</h4><p>To address the complexity brought by hybrid architectures, v4.2.1 focuses on building a unified and efficient heterogeneous computing foundation. The platform strengthens unified management and scheduling adaptation for heterogeneous computing resources such as GPU and vGPU, meeting diverse workload requirements from AI inference to graphics rendering.</p><p>In addition, through the integration of intelligent data caching acceleration capabilities, I/O latency for storage-intensive applications is significantly reduced. Together, these enhancements provide enterprises with a standardized resource pool across clouds and chip architectures, enabling global coordination and elastic supply of computing resources.</p><h4>2. Upgraded Elastic Scheduling System</h4><p>To maximize resource efficiency and optimize costs, v4.2.1 introduces a multi-dimensional intelligent elastic scheduling system. The platform innovatively integrates Vertical Pod Autoscaling (VPA), Horizontal Pod Autoscaling (HPA), and event-driven autoscaling (KEDA) into a unified experience.</p><p>VPA automatically optimizes container resource specifications based on historical workloads, reducing over-provisioning.</p><p>Enhanced HPA policies allow fine-grained and independent control over scaling behaviors.</p><p>KEDA converts external events such as message queues into scaling signals and even supports scaling replicas down to zero for extreme cost optimization.</p><h4>3. Strengthened Cluster Stability and Governance</h4><p>To ensure global stability in large-scale, multi-cluster production environments, v4.2.1 delivers significant enhancements in governance and observability.</p><p>The newly introduced Node Group capability enables logical grouping of physical nodes and binding them to enterprise workspaces — perfectly supporting complex scenarios such as multi-tenant resource isolation and mixed deployment in secure domestic computing environments.</p><p>On the operations side, the platform provides visualized online upgrades for member clusters and precise status synchronization, significantly simplifying multi-cluster lifecycle management.</p><h3>Global Practices: Deep Engagement in Mission-Critical Scenarios</h3><p>The ultimate value of a product is proven when users face real-world core business challenges. In 2025, KubeSphere’s reliability, flexibility, and openness earned deep trust across key global industries.</p><p>A leading automotive finance company adopted KubeSphere Enterprise Edition to build a unified hybrid cloud platform. While meeting stringent financial compliance and isolation requirements, it achieved global elastic resource scheduling and one-stop operations management, improving overall operational efficiency by over 40% and strongly supporting rapid innovation and stable business operations.</p><p>A Municipal Bureau of Planning and Natural Resources built a “One Cloud, Multiple Architectures” government container cloud platform. By seamlessly managing heterogeneous chip architectures and enabling unified cross-architecture scheduling with standardized processes, it effectively supported the digital transformation of smart city and spatial planning systems.</p><p>Macau Meteorological and Geophysical Bureau selected KubeSphere Trusted Edition to build the cloud-native foundation for its core forecasting and monitoring systems. While meeting high security and compliance requirements, the platform enabled unified resource scheduling and automated operations, ensuring 24/7 uninterrupted and stable meteorological services.</p><p>AMPLUS S.A., a European IT solutions provider, built a standardized cloud-native management solution based on KubeSphere for a public university research platform. This approach significantly reduced long-term operational costs, empowered users with self-management capabilities, and improved solution reusability and delivery efficiency — enabling Amplus to establish a productized service model reusable across education and enterprise customers.</p><h3>Ecosystem Co-Building: Bringing Industry Together</h3><p>In 2025, KubeSphere’s technical influence and ecosystem recognition continued to grow, with GitHub stars surpassing 16,000 — reflecting strong global developer engagement. We remain committed to collaboration and win-win partnerships, building a vibrant technical ecosystem with partners and users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/0*u5cIeGWYuRaes6Xc.png" /></figure><p><strong>Cultivating Cloud-Native Talent</strong></p><p>Through technical collaborations, joint innovation programs, and talent development initiatives, we established deep partnerships with industry players and universities. Programs such as “Open Source Summer” successfully incubated innovative prototypes like an intelligent operations assistant, accelerating the practical exploration of cutting-edge technologies.</p><p><strong>Integrating Industry Best Practices</strong></p><p>Through a flexible extension component architecture, we achieved deep integration with leading technologies such as Fluid (data orchestration) and OceanBase (distributed database). This allows users to flexibly select and combine production-proven components to build a robust and reliable infrastructure foundation.</p><p><strong>Advancing Technology Integration and Standard Practices</strong></p><p>We continue contributing stability and performance optimization experience gained from large-scale enterprise deployments back to the ecosystem, working closely with industry communities to advance the maturity and adoption of cloud-native application management standards.</p><h3>Looking Ahead: Platform-Based Agile Evolution</h3><p>To respond more agilely to technological evolution and diverse business scenarios, KubeSphere will adopt a new development model in 2026:Annual core platform updates, with quarterly extension component releases.</p><p>This model focuses on strengthening core capabilities and key scenario support while leveraging flexible modular strategies to adapt quickly to market changes — helping enterprises continuously unlock cutting-edge value on a stable foundation.</p><p>Our roadmap will focus on four key directions to make the platform smarter, more resilient, and more open:</p><h4>1. Global Governance and High Availability Assurance</h4><p>To support global business continuity, we will strengthen multi-cluster federation governance capabilities. A key focus is enabling active-active management planes and disaster recovery by integrating leading solutions such as Karmada, ensuring cross-availability-zone high availability and fault recovery for the control plane itself — providing a solid management foundation for large-scale, geographically distributed deployments.</p><h4>2. Intelligent Operations and Cost Insights</h4><p>We will evolve operations from visualization toward intelligence and refinement.</p><p>A newly designed global overview dashboard and centralized alert center will provide administrators and tenants with clear visibility into system status and event management.</p><p>Building on this, a planned AI-powered operations assistant will analyze alerts, logs, and performance data to provide root cause analysis and remediation suggestions.</p><p>In parallel, we will deepen cost insight capabilities by analyzing resource consumption and billing data to deliver visualized cost allocation reports and optimization recommendations — making cloud-native resource costs transparent, controllable, and optimizable, truly enabling cost reduction and efficiency improvement.</p><h4>3. Ecosystem Integration and Standard Practices</h4><p>We will deepen integration with leading cloud-native technologies and deliver production-ready solutions while promoting standardization.</p><ul><li>Cilium Integration: We will provide a Cilium-based container networking solution built on eBPF, offering higher network performance and observability. Its powerful security policy capabilities — including network policies and service mesh features — better meet enterprise security and compliance requirements.</li><li>Adopting Gateway API:As the widely adopted Ingress NGINX gradually moves toward maintenance mode, we will provide next-generation traffic management solutions based on the Gateway API standard. This enables users to smoothly transition from existing Ingress implementations to a more powerful and unified governance framework, mitigating technology obsolescence risks and future-proofing architecture evolution.</li></ul><p>These integrations aim to productize community best practices, promote adoption of industry-recognized standards, and reduce technology selection and implementation complexity.</p><h4>4. Extension of Core PaaS Capabilities</h4><p>To simplify the cloud-native deployment and management of critical middleware, we will enhance extension components to improve full lifecycle management for container-based databases, message queues, and other middleware — providing one-stop capabilities for deployment, monitoring, and backup, ensuring critical enterprise applications run smoothly and reliably on a unified container platform.</p><h3>Conclusion</h3><p>Every breakthrough in 2025 was built on the trust and collaboration of customers, partners, and community members.</p><p>Looking ahead to 2026, KubeSphere stands ready with a more resilient foundation and a more agile ecosystem. We invite you to master your digital core and embrace an intelligent and resilient digital future together.<br>KubeSphere invites you to navigate the digital future together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e408e6c5f687" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Native Weekly: Ingress NGINX Is Approaching End of Maintenance]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kubesphere.medium.com/cloud-native-weekly-ingress-nginx-is-approaching-end-of-maintenance-993ae19a2354?source=rss-a29a021fa88d------2"><img src="https://cdn-images-1.medium.com/max/1256/1*VXw8KQdATwtMkBiBR8csqg.png" width="1256"></a></p><p class="medium-feed-snippet">Cloud Native Highlights</p><p class="medium-feed-link"><a href="https://kubesphere.medium.com/cloud-native-weekly-ingress-nginx-is-approaching-end-of-maintenance-993ae19a2354?source=rss-a29a021fa88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kubesphere.medium.com/cloud-native-weekly-ingress-nginx-is-approaching-end-of-maintenance-993ae19a2354?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/993ae19a2354</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Fri, 06 Feb 2026 09:12:37 GMT</pubDate>
            <atom:updated>2026-02-06T09:12:37.432Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Rancher vs OpenShift vs KubeSphere: trade-offs nobody tells you about]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Choosing a Kubernetes management platform is rarely about features.
&#xA0;It&#x2019;s about what kind of complexity you&#x2019;re willing to live with.</p><p class="medium-feed-link"><a href="https://kubesphere.medium.com/rancher-vs-openshift-vs-kubesphere-trade-offs-nobody-tells-you-about-f4d154f2862e?source=rss-a29a021fa88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kubesphere.medium.com/rancher-vs-openshift-vs-kubesphere-trade-offs-nobody-tells-you-about-f4d154f2862e?source=rss-a29a021fa88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4d154f2862e</guid>
            <dc:creator><![CDATA[KubeSphere]]></dc:creator>
            <pubDate>Fri, 30 Jan 2026 03:18:25 GMT</pubDate>
            <atom:updated>2026-01-30T03:18:25.622Z</atom:updated>
        </item>
    </channel>
</rss>