clusterpedia-io/clusterpedia

Description: The Encyclopedia of Kubernetes clusters

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 24 minutes ago
Added to GitGenius on May 25th, 2026
Created on October 8th, 2021
Open Issues & Pull Requests: 64 (+0)
Number of forks: 126
Total Stargazers: 880 (+0)
Total Subscribers: 10 (+0)

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 456 days
Stale 30+ days: 10
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • kind/feature (11)
  • area/apiserver (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 0.0 hours
90th percentile: 0.0 hours
Tracked items: 17

Most active contributors

Detailed Description

Clusterpedia is a Kubernetes multi-cluster resource management and search platform designed to synchronize, index, and retrieve resources across multiple Kubernetes clusters. Written in Go, it functions as an encyclopedia for multi-cluster environments, enabling users to search and manage resources across distributed Kubernetes deployments with a unified interface compatible with standard Kubernetes OpenAPI conventions.

The project serves as a Cloud Native Computing Foundation sandbox project and can be deployed as a standalone platform or integrated with existing multi-cloud orchestration systems including Cluster API, Karmada, Clusternet, vCluster, and KubeVela. This flexibility allows Clusterpedia to work seamlessly within established multi-cloud ecosystems without requiring manual maintenance, as it automatically synchronizes resources from clusters managed by these platforms.

Clusterpedia's core functionality centers on advanced resource retrieval capabilities. Users can query resources using standard Kubernetes tools like kubectl, client-go, or controller-runtime/client, with support for retrieving both full resource objects and metadata. The search system provides rich filtering options including filtering by cluster, namespace, name, and creation time, searching by parent or ancestor owners, multi-cluster label selectors, enhanced field selectors, and custom search conditions. The platform supports a unified search entry point through Kubernetes Aggregated API, meaning users access multi-cluster resources through the same IP and port as their master cluster.

The architecture comprises four main components: the Clusterpedia APIServer that registers with Kubernetes via Aggregated API, the ClusterSynchro Manager that handles cluster resource synchronization, a pluggable Storage Layer that connects to specific storage backends, and the underlying Storage Component itself. The system uses a custom resource called PediaCluster for cluster authentication and synchronization configuration. Clusterpedia provides a default storage layer supporting MySQL and PostgreSQL, with plans to add support for graph databases and Elasticsearch.

A significant capability is Clusterpedia's handling of Kubernetes version heterogeneity. It supports importing clusters running Kubernetes 1.10 and later, automatically converting resources between different API versions. This means users can retrieve Deployments using v1, v1beta2, or v1beta1 versions regardless of which version runs in individual clusters. The platform also supports Collection Resources, allowing retrieval of multiple resource types through a single API call, such as querying Deployments, DaemonSets, and StatefulSets simultaneously.

The synchronization system offers flexible policies including wildcard support for syncing all resource types within specified groups or clusters, automatic synchronization of all custom resources, and intelligent adaptation to CRD and API changes. Clusterpedia optimizes for low memory usage through optimized informer caches and implements weak network optimization with automatic synchronization start and stop based on cluster health status.

GitGenius activity data shows the project maintains rapid issue and pull request response times with a median latency of 0.0 hours across tracked items. Feature requests represent the most active issue category with 11 tracked items, while the apiserver area accounts for 1 tracked item. Primary contributors include Iceber with 17 tracked events, TNonet with 4 events, and chloeyin with 2 events. The repository shares contributors with kubernetes/kubernetes, llm-d/llm-d, and containerd/containerd, indicating integration with broader Kubernetes ecosystem projects.

clusterpedia
by
clusterpedia-ioclusterpedia-io/clusterpedia

Repository Details

Fetching additional details & charts...