Tagged articles
Karmada
11 articles · Page 1 of 1
This article details Ctrip's migration from Kubefed to Karmada for multi‑cluster governance, describing the architectural evolution, production deployment for high‑availability and smooth cross‑cluster pod migration, and the performance and memory optimizations required to support over 200 GB of control‑plane memory usage and tens of thousands of Pods.
Control Plane OptimizationFederationHigh Availability
0 likes · 18 min read

This article explains why organizations adopt multi‑cluster Kubernetes for high availability, hybrid‑cloud scaling, and fault isolation, outlines the preparatory steps, compares Federation v1 and v2, introduces Karmada as a CNCF project, and shares practical non‑federated deployment, monitoring, traffic management, and migration techniques with code examples.
DevOpsFederationKarmada
0 likes · 18 min read

The article describes how a company implements an idle compute sharing feature for dedicated Kubernetes clusters, leveraging Karmada to allocate spare CPU and memory to offline workloads, thereby improving resource utilization, reducing costs, and outlining usage scenarios, configuration steps, technical architecture, and future plans.
Idle Compute SharingKarmadaKubernetes
0 likes · 9 min read

This article examines the motivations, benefits, and existing solutions for Kubernetes multi‑cluster management, then details Vivo's non‑federated and federated approaches, application‑centric continuous delivery, elastic scaling, unified scheduling, gray‑release strategies, and summarizes the current state and challenges.
DevOpsKarmadaKubernetes
0 likes · 22 min read

The article explains why enterprises adopt multi‑cluster Kubernetes architectures, reviews community solutions such as Karmada, Clusternet and OCM, and details vivo’s hybrid strategy that combines a unified UI for independent clusters with Karmada‑based federation for resource distribution, elastic scaling, cross‑cluster scheduling, and gray‑release migration.
KarmadaKubernetesMulti-Cluster
0 likes · 20 min read

This article examines the origins and core challenges of Kubernetes multi‑cluster management, compares four open‑source solutions—KubeFed, Karmada, Open Cluster Management (OCM) and Gardener—by detailing their architectures, application models, scheduling and service discovery mechanisms, and discusses emerging trends such as multi‑tenant isolation, virtual clusters, and stateful‑application migration strategies.
GardenerKarmadaKubernetes
0 likes · 27 min read

The Karmada community's Cloud Native Days China 2022 session in Nanjing gathered over 30 enterprises and developers to share multi‑cloud, multi‑cluster production practices, large‑scale testing results, and real‑world implementations from Huawei Cloud, vivo, Hurricane Engine, China Mobile, DaoCloud, and Zhejiang University, highlighting Karmada's scalability and ecosystem growth.
KarmadaKubernetesMulti-Cluster
0 likes · 9 min read

Vivo’s engineering team shares their practical experience creating a Karmada‑Operator using the Operator SDK and Ansible, detailing background, deployment challenges, design choices, API and architecture, etcd management, member cluster handling, CI pipeline, and performance testing to enable robust multi‑cloud Kubernetes orchestration.
AnsibleKarmadaKubernetes
0 likes · 15 min read

vivo created an Ansible‑based Karmada‑Operator that declaratively manages multi‑cluster deployments, etcd backup/restore, and control‑plane upgrades via custom CRDs and CI pipelines, addressing the limitations of existing tools and providing extensible, reliable, self‑healing orchestration for large‑scale Kubernetes environments.
AnsibleCI/CDKarmada
0 likes · 13 min read

This article explains why Kubernetes federation is needed for managing multiple clusters, compares the deprecated Federation v1 with the improved v2 architecture, and introduces Karmada as a modern multi‑cloud orchestration solution, complete with configuration examples, scheduling strategies, and CRD definitions.
CRDFederationKarmada
0 likes · 16 min read

This article explains why Kubernetes single‑cluster scalability is limited to about 5,000 nodes, introduces the concept of multi‑cluster federation, compares the legacy kubefed project with the actively maintained Karmada solution, and shows how policies and replica‑scheduling enable flexible cross‑AZ deployments and failover.
FederationKarmadaKubernetes
0 likes · 13 min read
