NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #2128 by repository stars
Latest stable
v0.9.2
Last release 25 days ago
28 Oct 2026
Release timing varies
gaps range from 9 days to 3 months
Nearly every release is documented
notes for 21 of 22 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
189 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
[release/0.9] build: bump alpine to 3.24.3 by @Iceber in #915
Full Changelog: v0.9.1...v0.9.2
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.9.1...v0.9.2
Your coding agent can read these notes before it upgrades. Set up the MCP server →
kubeapiserver: normalize pod portforward proxy subresource option by @officialasishkumar in https://github.com/clusterpedia-io/clusterpedia/pull/830
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.9.0...v0.9.1
Full Changelog: v0.9.0...v0.9.1
[release/0.9-k8s1.32] bump Kubernetes dependencies from 1.31 to 1.32 by @Iceber in https://github.com/clusterpedia-io/clusterpedia/pull/827
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.9.0...v0.9.1-k8s1.32.13
Full Changelog: v0.9.0...v0.9.1-k8s1.32.13
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
The related PRs: (@Iceber, https://github.com/clusterpedia-io/clusterpedia/pull/783, https://github.com/clusterpedia-io/clusterpedia/pull/785, https:/
The related PRs: (@Iceber, https://github.com/clusterpedia-io/clusterpedia/pull/783, https://github.com/clusterpedia-io/clusterpedia/pull/785, https://github.com/clusterpedia-io/clusterpedia/pull/786, https://github.com/clusterpedia-io/clusterpedia/pull/788, https://github.com/clusterpedia-io/clusterpedia/pull/787)
This feature implements the basic functionality for storing and retrieving event associations. It will be continuously iterated on based on user needs in the future.
apiVersion: cluster.clusterpedia.io/v1alpha2
kind: PediaCluster
metadata:
name: cluster-example
spec:
kubeconfig: "**base64**"
syncResources:
- group: ""
resources:
- "*"
eventsInvolvedResources:
- "pods"
- "nodes"
Use spec.syncResources.[].eventsInvolvedResources to specify the resources whose events need to be synchronized.
Note: If eventsInvolvedResources includes resources that have already been synchronized, you'll need to restart the clustersynchro-manager. This behavior will be optimized in the future based on user needs.
Use the search label search.clusterpedia.io/inject-events=true to request that the returned data includes events.
The events will be injected into the shadow.clusterpedia.io/events annotation.
Note: The events are not currently sorted. Event filtering and sorting may be added in the future.
$ kubectl --cluster kpanda-global -n kpanda-system get po -l "search.clusterpedia.io/inject-events=true" -o yaml
...
- apiVersion: v1
kind: Pod
metadata:
annotations:
shadow.clusterpedia.io/cluster-name: kpanda-global
shadow.clusterpedia.io/events: '[{"kind":"Event","apiVersion":"v1","metadata":{"name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49.1843f13522e37ad9","namespace":"kpanda-system","uid":"2220a44a-5414-4698-bc89-16ae411f5dc1","resourceVersion":"23444068","creationTimestamp":"2025-06-23T01:49:12Z"},"involvedObject":{"kind":"Pod","namespace":"kpanda-system","name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49","uid":"1918b3fb-cf36-4a2f-8f35-2e105210c38c","apiVersion":"v1","resourceVersion":"7019","fieldPath":"spec.containers{kpanda-clusterpedia-controller-manager}"},"reason":"Created","message":"Created container: kpanda-clusterpedia-controller-manager","source":{"component":"kubelet","host":"g-master68"},"firstTimestamp":"2025-05-29T08:11:30Z","lastTimestamp":"2025-06-23T02:57:05Z","count":393,"type":"Normal","eventTime":null,"reportingComponent":"kubelet","reportingInstance":"g-master68"},{"kind":"Event","apiVersion":"v1","metadata":{"name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49.1843f215c90791e6","namespace":"kpanda-system","uid":"3e1417e9-68df-4b2a-947e-f8a37178429b","resourceVersion":"23444060","creationTimestamp":"2025-06-23T01:49:12Z"},"involvedObject":{"kind":"Pod","namespace":"kpanda-system","name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49","uid":"1918b3fb-cf36-4a2f-8f35-2e105210c38c","apiVersion":"v1","resourceVersion":"7019","fieldPath":"spec.containers{kpanda-clusterpedia-controller-manager}"},"reason":"Pulled","message":"Container ....'
...
Associated stored events will not be deleted when the corresponding events in the cluster are cleaned up. This means historical events will be retained permanently until the related resource itself is deleted.
The related PRs: (@Iceber @scydas, https://github.com/clusterpedia-io/clusterpedia/pull/753, https://github.com/clusterpedia-io/clusterpedia/pull/747)
You need to enable the feature gate --feature-gates=ClusterAuthenticationFromSecret=true for both clusterpedia-apiserver and clustersynchro-manager.
Then, configure the PediaCluster and its corresponding authentication Secrets.
apiVersion: cluster.clusterpedia.io/v1alpha2
kind: PediaCluster
metadata:
name: cluster-example
spec:
apiserver: "https://cluster-example.io:8080"
authenticationFrom:
kubeconfig:
name: "cluster-example-auth-kubeconfig"
key: "kubeconfig"
ca:
name: "cluster-example-auth"
key: "ca.crt"
cert:
name: "cluster-example-auth"
key: "client.crt"
key:
name: "cluster-example-auth"
key: "client.key"
token:
name: "cluster-example-auth"
key: "token"
syncResources:
- group: ""
resources:
- "*"
---
apiVersion: v1
data:
ca.crt: LS0tLS1...base64
client.crt: LS0tLS1...base64
client.key: LS0tLS1...base64
kind: Secret
metadata:
name: cluster-example-cert
namespace: clusterpedia-system
type: Opaque
Note: You don’t need to configure every field in spec.authenticationFrom. Just provide a valid combination, such as: 1. Only kubeconfig 2. ca + cert + key 3. ca + token
Authentication Priority:
The namespace of the cluster authentication secrets must match the namespace where the Clusterpedia components are deployed.
In this version, Clusterpedia supports request forwarding to member clusters. This feature is divided into two categories:
Stricter authentication configurations have also been introduced for this feature.
To enable it, you need to turn on the AllowProxyRequestToClusters feature gate and set the appropriate flags in the Clusterpedia API server.
$ ./bin/apiserver --help
Resource server flags:
--allow-forward-unsync-resource-request
Allow forwarding requests for unsynchronized resource types.By default, only requests for resource types configured in PediaCluster can be forwarded.
--allow-pediacluster-config-for-proxy-request
Allow proxy requests to use the cluster configuration from PediaCluster when authentication information cannot be got from the header.
--allowed-proxy-subresources strings
List of subresources that support proxying requests to the specified cluster, formatted as '[resource/subresource],[subresource],...'. Supported proxy subresources include
"services/proxy,pods/proxy,pods/log,pods/exec,pods/attach,pods/portfowrd,nodes/proxy".
--enable-proxy-path-for-forward-request
Add a '/proxy' path in the API to proxy any request.
The related PRs: (@Iceber @scydas, https://github.com/clusterpedia-io/clusterpedia/pull/715, https://github.com/clusterpedia-io/clusterpedia/pull/717, https://github.com/clusterpedia-io/clusterpedia/pull/723 , https://github.com/clusterpedia-io/clusterpedia/pull/719)
Enable this by setting the --allowed-proxy-subresources flag in the Clusterpedia API server.
$ # Enable the proxy subresources for all resources and the exec subresources of the pods.
$ ./bin/apiserver --allowed-proxy-subresources "pods/exec,proxy"
Currently supported subresource requests include:
The usage is consistent with native Kubernetes behavior. You can use kubectl to make calls. For example:
$ kubectl --cluster cluster-example logs nginx
$ kubectl --cluster cluster-example exec -ti nginx bash
The related PRs: (@Iceber @scydas, https://github.com/clusterpedia-io/clusterpedia/pull/716, https://github.com/clusterpedia-io/clusterpedia/pull/741, https://github.com/clusterpedia-io/clusterpedia/pull/748,https://github.com/clusterpedia-io/clusterpedia/pull/750, https://github.com/clusterpedia-io/clusterpedia/pull/752)
Clusterpedia supports three ways to forward requests directly to member clusters:
--enable-proxy-path-for-forward-request flag. The API server will support proxy-style paths like:
/apis/clusterpedia.io/v1beta1/resources/clusters/<cluster>/proxy/<forward path>X-CLUSTERPEDIA-FORWARD: truesearch.clusterpedia.io/forward to enable forwarding.# kubeconfig
- cluster:
insecure-skip-tls-verify: true
server: https://127.0.0.1:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/
name: cluster-example
- cluster:
insecure-skip-tls-verify: true
server: https://127.0.0.1:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/proxy
name: cluster-example-proxy
$ kubectl --cluster cluster-example-proxy get po -A
$ kubectl --cluster cluster-example get po -l search.clusterpedia.io/forward=true
$ curl -v -k --cert-type P12 --cert client.p12:password -H "X-CLUSTERPEDIA-FORWARD: true" "https://localhost:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/api/v1/namespaces/clusterpedia-system/pods"
You can enable a more relaxed mode by setting the --allow-forward-unsync-resource-request flag to allow forwarding requests for unsynchronized resources.
By default, proxy requests require authentication headers to be passed in the request for the target cluster. These headers include the necessary credentials.
Alternatively, you can enable --allow-pediacluster-config-for-proxy-request to reuse the authentication config defined in the PediaCluster.
$ ./bin/apiserver --help
...
Metrics flags:
--allow-metric-labels stringToString
The map from metric-label to value allow-list of this label. The key's format is <MetricName>,<LabelName>. The value's format is <allowed_value>,<allowed_value>...e.g.
metric1,label1='v1,v2,v3', metric1,label2='v1,v2,v3' metric2,label1='v1,v2,v3'. (default [])
--allow-metric-labels-manifest string
The path to the manifest file that contains the allow-list mapping. The format of the file is the same as the flag --allow-metric-labels. Note that the flag --allow-metric-labels will
override the manifest file.
--disabled-metrics strings
This flag provides an escape hatch for misbehaving metrics. You must provide the fully qualified metric name in order to disable it. Disclaimer: disabling metrics is higher in precedence
than showing hidden metrics.
--show-hidden-metrics-for-version string
The previous version for which you want to show hidden metrics. Only the previous minor version is meaningful, other values will not be allowed. The format is <major>.<minor>, e.g.:
'1.16'. The purpose of this format is make sure you have the opportunity to notice if the next release hides additional metrics, rather than being surprised when they are permanently
removed in the release after that.
...
# HELP clusterpedia_build_info [ALPHA] A metric with a constant '1' value labeled by git version, git commit, git tree state, build date, Go version, and compiler from which Clusterpedia was built, and platform on which it is running.
# TYPE clusterpedia_build_info gauge
clusterpedia_build_info{build_date="2025-06-17T07:06:13Z",compiler="gc",git_commit="ee85edb72c541ece9e0b2d7da54c0f442e9a1536",git_tree_state="clean",git_version="v0.9.0-beta.0",go_version="go1.23.10",platform="linux/arm64"} 1
# HELP kubernetes_build_info [ALPHA] A metric with a constant '1' value labeled by major, minor, git version, git commit, git tree state, build date, Go version, and compiler from which Kubernetes was built, and platform on which it is running.
# TYPE kubernetes_build_info gauge
kubernetes_build_info{build_date="2025-06-17T07:06:13Z",compiler="gc",git_commit="ee85edb72c541ece9e0b2d7da54c0f442e9a1536",git_tree_state="clean",git_version="v1.31.2",go_version="go1.23.10",major="1",minor="31",platform="linux/arm64"} 1
Metrics with prefix storage_dbstats are now available.
HELP storage_dbstats_idle The number of idle connections.
# TYPE storage_dbstats_idle gauge
storage_dbstats_idle{db_name="clusterpedia"} 1
# HELP storage_dbstats_in_use The number of connections currently in use.
# TYPE storage_dbstats_in_use gauge
storage_dbstats_in_use{db_name="clusterpedia"} 0
# HELP storage_dbstats_max_idle_closed The total number of connections closed due to SetMaxIdleConns.
# TYPE storage_dbstats_max_idle_closed gauge
storage_dbstats_max_idle_closed{db_name="clusterpedia"} 0
# HELP storage_dbstats_max_idletime_closed The total number of connections closed due to SetConnMaxIdleTime.
# TYPE storage_dbstats_max_idletime_closed gauge
...
If a resource is in the status.resources[].initialListPhase state, it means that the cluster data in Clusterpedia Storage is still being initialized and not yet consistent with the source cluster.
| dependency | old version | new version |
|---|---|---|
| gorm.io/gorm | v1.24.1 | 1.30.0 |
| gorm.io/driver/mysql | v1.4.4 | v1.6.0 |
| gorm.io/driver/postgres | v1.4.5 | v1.6.0 |
| gorm.io/driver/sqlite | v1.4.4 | v1.6.0 |
| gorm.io/datatypes | v1.0.7 | v1.2.5 |
| github.com/jackc/pgx | v4.17.2 | v5.7.5 |
| github.com/go-sql-driver/mysql | v1.6.0 | v1.9.3 |
Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
The related PRs: (@Iceber, #783, #785, #786, #788, #787)
This feature implements the basic functionality for storing and retrieving event associations. It will be continuously iterated on based on user needs in the future.
apiVersion: cluster.clusterpedia.io/v1alpha2
kind: PediaCluster
metadata:
name: cluster-example
spec:
kubeconfig: "**base64**"
syncResources:
- group: ""
resources:
- "*"
eventsInvolvedResources:
- "pods"
- "nodes"
Use spec.syncResources.[].eventsInvolvedResources to specify the resources whose events need to be synchronized.
Note: If eventsInvolvedResources includes resources that have already been synchronized, you'll need to restart the clustersynchro-manager. This behavior will be optimized in the future based on user needs.
Use the search label search.clusterpedia.io/inject-events=true to request that the returned data includes events.
The events will be injected into the shadow.clusterpedia.io/events annotation.
Note: The events are not currently sorted. Event filtering and sorting may be added in the future.
$ kubectl --cluster kpanda-global -n kpanda-system get po -l "search.clusterpedia.io/inject-events=true" -o yaml
...
- apiVersion: v1
kind: Pod
metadata:
annotations:
shadow.clusterpedia.io/cluster-name: kpanda-global
shadow.clusterpedia.io/events: '[{"kind":"Event","apiVersion":"v1","metadata":{"name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49.1843f13522e37ad9","namespace":"kpanda-system","uid":"2220a44a-5414-4698-bc89-16ae411f5dc1","resourceVersion":"23444068","creationTimestamp":"2025-06-23T01:49:12Z"},"involvedObject":{"kind":"Pod","namespace":"kpanda-system","name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49","uid":"1918b3fb-cf36-4a2f-8f35-2e105210c38c","apiVersion":"v1","resourceVersion":"7019","fieldPath":"spec.containers{kpanda-clusterpedia-controller-manager}"},"reason":"Created","message":"Created container: kpanda-clusterpedia-controller-manager","source":{"component":"kubelet","host":"g-master68"},"firstTimestamp":"2025-05-29T08:11:30Z","lastTimestamp":"2025-06-23T02:57:05Z","count":393,"type":"Normal","eventTime":null,"reportingComponent":"kubelet","reportingInstance":"g-master68"},{"kind":"Event","apiVersion":"v1","metadata":{"name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49.1843f215c90791e6","namespace":"kpanda-system","uid":"3e1417e9-68df-4b2a-947e-f8a37178429b","resourceVersion":"23444060","creationTimestamp":"2025-06-23T01:49:12Z"},"involvedObject":{"kind":"Pod","namespace":"kpanda-system","name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49","uid":"1918b3fb-cf36-4a2f-8f35-2e105210c38c","apiVersion":"v1","resourceVersion":"7019","fieldPath":"spec.containers{kpanda-clusterpedia-controller-manager}"},"reason":"Pulled","message":"Container ....'
...Associated stored events will not be deleted when the corresponding events in the cluster are cleaned up. This means historical events will be retained permanently until the related resource itself is deleted.
The related PRs: (@Iceber @scydas, #753, #747)
You need to enable the feature gate --feature-gates=ClusterAuthenticationFromSecret=true for both clusterpedia-apiserver and clustersynchro-manager.
Then, configure the PediaCluster and its corresponding authentication Secrets.
apiVersion: cluster.clusterpedia.io/v1alpha2
kind: PediaCluster
metadata:
name: cluster-example
spec:
apiserver: "https://cluster-example.io:8080"
authenticationFrom:
kubeconfig:
name: "cluster-example-auth-kubeconfig"
key: "kubeconfig"
ca:
name: "cluster-example-auth"
key: "ca.crt"
cert:
name: "cluster-example-auth"
key: "client.crt"
key:
name: "cluster-example-auth"
key: "client.key"
token:
name: "cluster-example-auth"
key: "token"
syncResources:
- group: ""
resources:
- "*"
---
apiVersion: v1
data:
ca.crt: LS0tLS1...base64
client.crt: LS0tLS1...base64
client.key: LS0tLS1...base64
kind: Secret
metadata:
name: cluster-example-cert
namespace: clusterpedia-system
type: OpaqueNote: You don’t need to configure every field in spec.authenticationFrom. Just provide a valid combination, such as: 1. Only kubeconfig 2. ca + cert + key 3. ca + token
Authentication Priority:
The namespace of the cluster authentication secrets must match the namespace where the Clusterpedia components are deployed.
In this version, Clusterpedia supports request forwarding to member clusters. This feature is divided into two categories:
Stricter authentication configurations have also been introduced for this feature.
To enable it, you need to turn on the AllowProxyRequestToClusters feature gate and set the appropriate flags in the Clusterpedia API server.
$ ./bin/apiserver --help
Resource server flags:
--allow-forward-unsync-resource-request
Allow forwarding requests for unsynchronized resource types.By default, only requests for resource types configured in PediaCluster can be forwarded.
--allow-pediacluster-config-for-proxy-request
Allow proxy requests to use the cluster configuration from PediaCluster when authentication information cannot be got from the header.
--allowed-proxy-subresources strings
List of subresources that support proxying requests to the specified cluster, formatted as '[resource/subresource],[subresource],...'. Supported proxy subresources include
"services/proxy,pods/proxy,pods/log,pods/exec,pods/attach,pods/portfowrd,nodes/proxy".
--enable-proxy-path-for-forward-request
Add a '/proxy' path in the API to proxy any request.The related PRs: (@Iceber @scydas, #715, #717, #723 , #719)
Enable this by setting the --allowed-proxy-subresources flag in the Clusterpedia API server.
$ # Enable the proxy subresources for all resources and the exec subresources of the pods.
$ ./bin/apiserver --allowed-proxy-subresources "pods/exec,proxy"Currently supported subresource requests include:
The usage is consistent with native Kubernetes behavior. You can use kubectl to make calls. For example:
$ kubectl --cluster cluster-example logs nginx
$ kubectl --cluster cluster-example exec -ti nginx bashThe related PRs: (@Iceber @scydas, #716, #741, #748, #752)
Clusterpedia supports three ways to forward requests directly to member clusters:
--enable-proxy-path-for-forward-request flag. The API server will support proxy-style paths like:X-CLUSTERPEDIA-FORWARD: truesearch.clusterpedia.io/forward to enable forwarding.# kubeconfig
- cluster:
insecure-skip-tls-verify: true
server: https://127.0.0.1:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/
name: cluster-example
- cluster:
insecure-skip-tls-verify: true
server: https://127.0.0.1:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/proxy
name: cluster-example-proxy$ kubectl --cluster cluster-example-proxy get po -A
$ kubectl --cluster cluster-example get po -l search.clusterpedia.io/forward=true
$ curl -v -k --cert-type P12 --cert client.p12:password -H "X-CLUSTERPEDIA-FORWARD: true" "https://localhost:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/api/v1/namespaces/clusterpedia-system/pods"You can enable a more relaxed mode by setting the --allow-forward-unsync-resource-request flag to allow forwarding requests for unsynchronized resources.
By default, proxy requests require authentication headers to be passed in the request for the target cluster. These headers include the necessary credentials.
Alternatively, you can enable --allow-pediacluster-config-for-proxy-request to reuse the authentication config defined in the PediaCluster.
$ ./bin/apiserver --help
...
Metrics flags:
--allow-metric-labels stringToString
The map from metric-label to value allow-list of this label. The key's format is <MetricName>,<LabelName>. The value's format is <allowed_value>,<allowed_value>...e.g.
metric1,label1='v1,v2,v3', metric1,label2='v1,v2,v3' metric2,label1='v1,v2,v3'. (default [])
--allow-metric-labels-manifest string
The path to the manifest file that contains the allow-list mapping. The format of the file is the same as the flag --allow-metric-labels. Note that the flag --allow-metric-labels will
override the manifest file.
--disabled-metrics strings
This flag provides an escape hatch for misbehaving metrics. You must provide the fully qualified metric name in order to disable it. Disclaimer: disabling metrics is higher in precedence
than showing hidden metrics.
--show-hidden-metrics-for-version string
The previous version for which you want to show hidden metrics. Only the previous minor version is meaningful, other values will not be allowed. The format is <major>.<minor>, e.g.:
'1.16'. The purpose of this format is make sure you have the opportunity to notice if the next release hides additional metrics, rather than being surprised when they are permanently
removed in the release after that.
...# HELP clusterpedia_build_info [ALPHA] A metric with a constant '1' value labeled by git version, git commit, git tree state, build date, Go version, and compiler from which Clusterpedia was built, and platform on which it is running.
# TYPE clusterpedia_build_info gauge
clusterpedia_build_info{build_date="2025-06-17T07:06:13Z",compiler="gc",git_commit="ee85edb72c541ece9e0b2d7da54c0f442e9a1536",git_tree_state="clean",git_version="v0.9.0-beta.0",go_version="go1.23.10",platform="linux/arm64"} 1
# HELP kubernetes_build_info [ALPHA] A metric with a constant '1' value labeled by major, minor, git version, git commit, git tree state, build date, Go version, and compiler from which Kubernetes was built, and platform on which it is running.
# TYPE kubernetes_build_info gauge
kubernetes_build_info{build_date="2025-06-17T07:06:13Z",compiler="gc",git_commit="ee85edb72c541ece9e0b2d7da54c0f442e9a1536",git_tree_state="clean",git_version="v1.31.2",go_version="go1.23.10",major="1",minor="31",platform="linux/arm64"} 1
Metrics with prefix storage_dbstats are now available.
HELP storage_dbstats_idle The number of idle connections.
# TYPE storage_dbstats_idle gauge
storage_dbstats_idle{db_name="clusterpedia"} 1
# HELP storage_dbstats_in_use The number of connections currently in use.
# TYPE storage_dbstats_in_use gauge
storage_dbstats_in_use{db_name="clusterpedia"} 0
# HELP storage_dbstats_max_idle_closed The total number of connections closed due to SetMaxIdleConns.
# TYPE storage_dbstats_max_idle_closed gauge
storage_dbstats_max_idle_closed{db_name="clusterpedia"} 0
# HELP storage_dbstats_max_idletime_closed The total number of connections closed due to SetConnMaxIdleTime.
# TYPE storage_dbstats_max_idletime_closed gauge
...
If a resource is in the status.resources[].initialListPhase state, it means that the cluster data in Clusterpedia Storage is still being initialized and not yet consistent with the source cluster.
| dependency | old version | new version |
|---|---|---|
| gorm.io/gorm | v1.24.1 | 1.30.0 |
| gorm.io/driver/mysql | v1.4.4 | v1.6.0 |
| gorm.io/driver/postgres | v1.4.5 | v1.6.0 |
| gorm.io/driver/sqlite | v1.4.4 | v1.6.0 |
| gorm.io/datatypes | v1.0.7 | v1.2.5 |
| github.com/jackc/pgx | v4.17.2 | v5.7.5 |
| github.com/go-sql-driver/mysql | v1.6.0 | v1.9.3 |
Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
fix MySQL not allowing default values for JSON column by @scydas in #805
Full Changelog: v0.9.0-beta.2...v0.9.0-beta.3
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.9.0-beta.2...v0.9.0-beta.3
Clusterpedia v0.9.0-beta.3 Pre-release
Pre-release
Compare
Merge pull request #802 from Iceber/fix_hack_script
Merge pull request #802 from Iceber/fix_hack_script
fix hack/verify-forked-code.sh
Clusterpedia v0.9.0-beta.2 Pre-release
Pre-release
Compare
The related PRs: (@Iceber, https://github.com/clusterpedia-io/clusterpedia/pull/783, https://github.com/clusterpedia-io/clusterpedia/pull/785, https:/
The related PRs: (@Iceber, https://github.com/clusterpedia-io/clusterpedia/pull/783, https://github.com/clusterpedia-io/clusterpedia/pull/785, https://github.com/clusterpedia-io/clusterpedia/pull/786, https://github.com/clusterpedia-io/clusterpedia/pull/788, https://github.com/clusterpedia-io/clusterpedia/pull/787)
This feature implements the basic functionality for storing and retrieving event associations. It will be continuously iterated on based on user needs in the future.
apiVersion: cluster.clusterpedia.io/v1alpha2
kind: PediaCluster
metadata:
name: cluster-example
spec:
kubeconfig: "**base64**"
syncResources:
- group: ""
resources:
- "*"
eventsInvolvedResources:
- "pods"
- "nodes"
Use spec.syncResources.[].eventsInvolvedResources to specify the resources whose events need to be synchronized.
Note: If eventsInvolvedResources includes resources that have already been synchronized, you'll need to restart the clustersynchro-manager. This behavior will be optimized in the future based on user needs.
Use the search label search.clusterpedia.io/inject-events=true to request that the returned data includes events.
The events will be injected into the shadow.clusterpedia.io/events annotation.
Note: The events are not currently sorted. Event filtering and sorting may be added in the future.
$ kubectl --cluster kpanda-global -n kpanda-system get po -l "search.clusterpedia.io/inject-events=true" -o yaml
...
- apiVersion: v1
kind: Pod
metadata:
annotations:
shadow.clusterpedia.io/cluster-name: kpanda-global
shadow.clusterpedia.io/events: '[{"kind":"Event","apiVersion":"v1","metadata":{"name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49.1843f13522e37ad9","namespace":"kpanda-system","uid":"2220a44a-5414-4698-bc89-16ae411f5dc1","resourceVersion":"23444068","creationTimestamp":"2025-06-23T01:49:12Z"},"involvedObject":{"kind":"Pod","namespace":"kpanda-system","name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49","uid":"1918b3fb-cf36-4a2f-8f35-2e105210c38c","apiVersion":"v1","resourceVersion":"7019","fieldPath":"spec.containers{kpanda-clusterpedia-controller-manager}"},"reason":"Created","message":"Created container: kpanda-clusterpedia-controller-manager","source":{"component":"kubelet","host":"g-master68"},"firstTimestamp":"2025-05-29T08:11:30Z","lastTimestamp":"2025-06-23T02:57:05Z","count":393,"type":"Normal","eventTime":null,"reportingComponent":"kubelet","reportingInstance":"g-master68"},{"kind":"Event","apiVersion":"v1","metadata":{"name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49.1843f215c90791e6","namespace":"kpanda-system","uid":"3e1417e9-68df-4b2a-947e-f8a37178429b","resourceVersion":"23444060","creationTimestamp":"2025-06-23T01:49:12Z"},"involvedObject":{"kind":"Pod","namespace":"kpanda-system","name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49","uid":"1918b3fb-cf36-4a2f-8f35-2e105210c38c","apiVersion":"v1","resourceVersion":"7019","fieldPath":"spec.containers{kpanda-clusterpedia-controller-manager}"},"reason":"Pulled","message":"Container ....'
...
Associated stored events will not be deleted when the corresponding events in the cluster are cleaned up. This means historical events will be retained permanently until the related resource itself is deleted.
The related PRs: (@Iceber @scydas, https://github.com/clusterpedia-io/clusterpedia/pull/753, https://github.com/clusterpedia-io/clusterpedia/pull/747)
You need to enable the feature gate --feature-gates=ClusterAuthenticationFromSecret=true for both clusterpedia-apiserver and clustersynchro-manager.
Then, configure the PediaCluster and its corresponding authentication Secrets.
apiVersion: cluster.clusterpedia.io/v1alpha2
kind: PediaCluster
metadata:
name: cluster-example
spec:
apiserver: "https://cluster-example.io:8080"
authenticationFrom:
kubeconfig:
name: "cluster-example-auth-kubeconfig"
key: "kubeconfig"
ca:
name: "cluster-example-auth"
key: "ca.crt"
cert:
name: "cluster-example-auth"
key: "client.crt"
key:
name: "cluster-example-auth"
key: "client.key"
token:
name: "cluster-example-auth"
key: "token"
syncResources:
- group: ""
resources:
- "*"
---
apiVersion: v1
data:
ca.crt: LS0tLS1...base64
client.crt: LS0tLS1...base64
client.key: LS0tLS1...base64
kind: Secret
metadata:
name: cluster-example-cert
namespace: clusterpedia-system
type: Opaque
Note: You don’t need to configure every field in spec.authenticationFrom. Just provide a valid combination, such as: 1. Only kubeconfig 2. ca + cert + key 3. ca + token
Authentication Priority:
The namespace of the cluster authentication secrets must match the namespace where the Clusterpedia components are deployed.
In this version, Clusterpedia supports request forwarding to member clusters. This feature is divided into two categories:
Stricter authentication configurations have also been introduced for this feature.
To enable it, you need to turn on the AllowProxyRequestToClusters feature gate and set the appropriate flags in the Clusterpedia API server.
$ ./bin/apiserver --help
Resource server flags:
--allow-forward-unsync-resource-request
Allow forwarding requests for unsynchronized resource types.By default, only requests for resource types configured in PediaCluster can be forwarded.
--allow-pediacluster-config-for-proxy-request
Allow proxy requests to use the cluster configuration from PediaCluster when authentication information cannot be got from the header.
--allowed-proxy-subresources strings
List of subresources that support proxying requests to the specified cluster, formatted as '[resource/subresource],[subresource],...'. Supported proxy subresources include
"services/proxy,pods/proxy,pods/log,pods/exec,pods/attach,pods/portfowrd,nodes/proxy".
--enable-proxy-path-for-forward-request
Add a '/proxy' path in the API to proxy any request.
The related PRs: (@Iceber @scydas, https://github.com/clusterpedia-io/clusterpedia/pull/715, https://github.com/clusterpedia-io/clusterpedia/pull/717, https://github.com/clusterpedia-io/clusterpedia/pull/723 , https://github.com/clusterpedia-io/clusterpedia/pull/719)
Enable this by setting the --allowed-proxy-subresources flag in the Clusterpedia API server.
$ # Enable the proxy subresources for all resources and the exec subresources of the pods.
$ ./bin/apiserver --allowed-proxy-subresources "pods/exec,proxy"
Currently supported subresource requests include:
The usage is consistent with native Kubernetes behavior. You can use kubectl to make calls. For example:
$ kubectl --cluster cluster-example logs nginx
$ kubectl --cluster cluster-example exec -ti nginx bash
The related PRs: (@Iceber @scydas, https://github.com/clusterpedia-io/clusterpedia/pull/716, https://github.com/clusterpedia-io/clusterpedia/pull/741, https://github.com/clusterpedia-io/clusterpedia/pull/748,https://github.com/clusterpedia-io/clusterpedia/pull/750, https://github.com/clusterpedia-io/clusterpedia/pull/752)
Clusterpedia supports three ways to forward requests directly to member clusters:
--enable-proxy-path-for-forward-request flag. The API server will support proxy-style paths like:
/apis/clusterpedia.io/v1beta1/resources/clusters/<cluster>/proxy/<forward path>X-CLUSTERPEDIA-FORWARD: truesearch.clusterpedia.io/forward to enable forwarding.# kubeconfig
- cluster:
insecure-skip-tls-verify: true
server: https://127.0.0.1:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/
name: cluster-example
- cluster:
insecure-skip-tls-verify: true
server: https://127.0.0.1:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/proxy
name: cluster-example-proxy
$ kubectl --cluster cluster-example-proxy get po -A
$ kubectl --cluster cluster-example get po -l search.clusterpedia.io/forward=true
$ curl -v -k --cert-type P12 --cert client.p12:password -H "X-CLUSTERPEDIA-FORWARD: true" "https://localhost:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/api/v1/namespaces/clusterpedia-system/pods"
You can enable a more relaxed mode by setting the --allow-forward-unsync-resource-request flag to allow forwarding requests for unsynchronized resources.
By default, proxy requests require authentication headers to be passed in the request for the target cluster. These headers include the necessary credentials.
Alternatively, you can enable --allow-pediacluster-config-for-proxy-request to reuse the authentication config defined in the PediaCluster.
$ ./bin/apiserver --help
...
Metrics flags:
--allow-metric-labels stringToString
The map from metric-label to value allow-list of this label. The key's format is <MetricName>,<LabelName>. The value's format is <allowed_value>,<allowed_value>...e.g.
metric1,label1='v1,v2,v3', metric1,label2='v1,v2,v3' metric2,label1='v1,v2,v3'. (default [])
--allow-metric-labels-manifest string
The path to the manifest file that contains the allow-list mapping. The format of the file is the same as the flag --allow-metric-labels. Note that the flag --allow-metric-labels will
override the manifest file.
--disabled-metrics strings
This flag provides an escape hatch for misbehaving metrics. You must provide the fully qualified metric name in order to disable it. Disclaimer: disabling metrics is higher in precedence
than showing hidden metrics.
--show-hidden-metrics-for-version string
The previous version for which you want to show hidden metrics. Only the previous minor version is meaningful, other values will not be allowed. The format is <major>.<minor>, e.g.:
'1.16'. The purpose of this format is make sure you have the opportunity to notice if the next release hides additional metrics, rather than being surprised when they are permanently
removed in the release after that.
...
# HELP clusterpedia_build_info [ALPHA] A metric with a constant '1' value labeled by git version, git commit, git tree state, build date, Go version, and compiler from which Clusterpedia was built, and platform on which it is running.
# TYPE clusterpedia_build_info gauge
clusterpedia_build_info{build_date="2025-06-17T07:06:13Z",compiler="gc",git_commit="ee85edb72c541ece9e0b2d7da54c0f442e9a1536",git_tree_state="clean",git_version="v0.9.0-beta.0",go_version="go1.23.10",platform="linux/arm64"} 1
# HELP kubernetes_build_info [ALPHA] A metric with a constant '1' value labeled by major, minor, git version, git commit, git tree state, build date, Go version, and compiler from which Kubernetes was built, and platform on which it is running.
# TYPE kubernetes_build_info gauge
kubernetes_build_info{build_date="2025-06-17T07:06:13Z",compiler="gc",git_commit="ee85edb72c541ece9e0b2d7da54c0f442e9a1536",git_tree_state="clean",git_version="v1.31.2",go_version="go1.23.10",major="1",minor="31",platform="linux/arm64"} 1
Metrics with prefix storage_dbstats are now available.
HELP storage_dbstats_idle The number of idle connections.
# TYPE storage_dbstats_idle gauge
storage_dbstats_idle{db_name="clusterpedia"} 1
# HELP storage_dbstats_in_use The number of connections currently in use.
# TYPE storage_dbstats_in_use gauge
storage_dbstats_in_use{db_name="clusterpedia"} 0
# HELP storage_dbstats_max_idle_closed The total number of connections closed due to SetMaxIdleConns.
# TYPE storage_dbstats_max_idle_closed gauge
storage_dbstats_max_idle_closed{db_name="clusterpedia"} 0
# HELP storage_dbstats_max_idletime_closed The total number of connections closed due to SetConnMaxIdleTime.
# TYPE storage_dbstats_max_idletime_closed gauge
...
If a resource is in the status.resources[].initialListPhase state, it means that the cluster data in Clusterpedia Storage is still being initialized and not yet consistent with the source cluster.
| dependency | old version | new version |
|---|---|---|
| gorm.io/gorm | v1.24.1 | 1.30.0 |
| gorm.io/driver/mysql | v1.4.4 | v1.6.0 |
| gorm.io/driver/postgres | v1.4.5 | v1.6.0 |
| gorm.io/driver/sqlite | v1.4.4 | v1.6.0 |
| gorm.io/datatypes | v1.0.7 | v1.2.5 |
| github.com/jackc/pgx | v4.17.2 | v5.7.5 |
| github.com/go-sql-driver/mysql | v1.6.0 | v1.9.3 |
Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
The related PRs: (@Iceber, #783, #785, #786, #788, #787)
This feature implements the basic functionality for storing and retrieving event associations. It will be continuously iterated on based on user needs in the future.
apiVersion: cluster.clusterpedia.io/v1alpha2
kind: PediaCluster
metadata:
name: cluster-example
spec:
kubeconfig: "**base64**"
syncResources:
- group: ""
resources:
- "*"
eventsInvolvedResources:
- "pods"
- "nodes"
Use spec.syncResources.[].eventsInvolvedResources to specify the resources whose events need to be synchronized.
Note: If eventsInvolvedResources includes resources that have already been synchronized, you'll need to restart the clustersynchro-manager. This behavior will be optimized in the future based on user needs.
Use the search label search.clusterpedia.io/inject-events=true to request that the returned data includes events.
The events will be injected into the shadow.clusterpedia.io/events annotation.
Note: The events are not currently sorted. Event filtering and sorting may be added in the future.
$ kubectl --cluster kpanda-global -n kpanda-system get po -l "search.clusterpedia.io/inject-events=true" -o yaml
...
- apiVersion: v1
kind: Pod
metadata:
annotations:
shadow.clusterpedia.io/cluster-name: kpanda-global
shadow.clusterpedia.io/events: '[{"kind":"Event","apiVersion":"v1","metadata":{"name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49.1843f13522e37ad9","namespace":"kpanda-system","uid":"2220a44a-5414-4698-bc89-16ae411f5dc1","resourceVersion":"23444068","creationTimestamp":"2025-06-23T01:49:12Z"},"involvedObject":{"kind":"Pod","namespace":"kpanda-system","name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49","uid":"1918b3fb-cf36-4a2f-8f35-2e105210c38c","apiVersion":"v1","resourceVersion":"7019","fieldPath":"spec.containers{kpanda-clusterpedia-controller-manager}"},"reason":"Created","message":"Created container: kpanda-clusterpedia-controller-manager","source":{"component":"kubelet","host":"g-master68"},"firstTimestamp":"2025-05-29T08:11:30Z","lastTimestamp":"2025-06-23T02:57:05Z","count":393,"type":"Normal","eventTime":null,"reportingComponent":"kubelet","reportingInstance":"g-master68"},{"kind":"Event","apiVersion":"v1","metadata":{"name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49.1843f215c90791e6","namespace":"kpanda-system","uid":"3e1417e9-68df-4b2a-947e-f8a37178429b","resourceVersion":"23444060","creationTimestamp":"2025-06-23T01:49:12Z"},"involvedObject":{"kind":"Pod","namespace":"kpanda-system","name":"kpanda-clusterpedia-controller-manager-67758bb46d-mpl49","uid":"1918b3fb-cf36-4a2f-8f35-2e105210c38c","apiVersion":"v1","resourceVersion":"7019","fieldPath":"spec.containers{kpanda-clusterpedia-controller-manager}"},"reason":"Pulled","message":"Container ....'
...Associated stored events will not be deleted when the corresponding events in the cluster are cleaned up. This means historical events will be retained permanently until the related resource itself is deleted.
The related PRs: (@Iceber @scydas, #753, #747)
You need to enable the feature gate --feature-gates=ClusterAuthenticationFromSecret=true for both clusterpedia-apiserver and clustersynchro-manager.
Then, configure the PediaCluster and its corresponding authentication Secrets.
apiVersion: cluster.clusterpedia.io/v1alpha2
kind: PediaCluster
metadata:
name: cluster-example
spec:
apiserver: "https://cluster-example.io:8080"
authenticationFrom:
kubeconfig:
name: "cluster-example-auth-kubeconfig"
key: "kubeconfig"
ca:
name: "cluster-example-auth"
key: "ca.crt"
cert:
name: "cluster-example-auth"
key: "client.crt"
key:
name: "cluster-example-auth"
key: "client.key"
token:
name: "cluster-example-auth"
key: "token"
syncResources:
- group: ""
resources:
- "*"
---
apiVersion: v1
data:
ca.crt: LS0tLS1...base64
client.crt: LS0tLS1...base64
client.key: LS0tLS1...base64
kind: Secret
metadata:
name: cluster-example-cert
namespace: clusterpedia-system
type: OpaqueNote: You don’t need to configure every field in spec.authenticationFrom. Just provide a valid combination, such as: 1. Only kubeconfig 2. ca + cert + key 3. ca + token
Authentication Priority:
The namespace of the cluster authentication secrets must match the namespace where the Clusterpedia components are deployed.
In this version, Clusterpedia supports request forwarding to member clusters. This feature is divided into two categories:
Stricter authentication configurations have also been introduced for this feature.
To enable it, you need to turn on the AllowProxyRequestToClusters feature gate and set the appropriate flags in the Clusterpedia API server.
$ ./bin/apiserver --help
Resource server flags:
--allow-forward-unsync-resource-request
Allow forwarding requests for unsynchronized resource types.By default, only requests for resource types configured in PediaCluster can be forwarded.
--allow-pediacluster-config-for-proxy-request
Allow proxy requests to use the cluster configuration from PediaCluster when authentication information cannot be got from the header.
--allowed-proxy-subresources strings
List of subresources that support proxying requests to the specified cluster, formatted as '[resource/subresource],[subresource],...'. Supported proxy subresources include
"services/proxy,pods/proxy,pods/log,pods/exec,pods/attach,pods/portfowrd,nodes/proxy".
--enable-proxy-path-for-forward-request
Add a '/proxy' path in the API to proxy any request.The related PRs: (@Iceber @scydas, #715, #717, #723 , #719)
Enable this by setting the --allowed-proxy-subresources flag in the Clusterpedia API server.
$ # Enable the proxy subresources for all resources and the exec subresources of the pods.
$ ./bin/apiserver --allowed-proxy-subresources "pods/exec,proxy"Currently supported subresource requests include:
The usage is consistent with native Kubernetes behavior. You can use kubectl to make calls. For example:
$ kubectl --cluster cluster-example logs nginx
$ kubectl --cluster cluster-example exec -ti nginx bashThe related PRs: (@Iceber @scydas, #716, #741, #748, #752)
Clusterpedia supports three ways to forward requests directly to member clusters:
--enable-proxy-path-for-forward-request flag. The API server will support proxy-style paths like:X-CLUSTERPEDIA-FORWARD: truesearch.clusterpedia.io/forward to enable forwarding.# kubeconfig
- cluster:
insecure-skip-tls-verify: true
server: https://127.0.0.1:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/
name: cluster-example
- cluster:
insecure-skip-tls-verify: true
server: https://127.0.0.1:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/proxy
name: cluster-example-proxy$ kubectl --cluster cluster-example-proxy get po -A
$ kubectl --cluster cluster-example get po -l search.clusterpedia.io/forward=true
$ curl -v -k --cert-type P12 --cert client.p12:password -H "X-CLUSTERPEDIA-FORWARD: true" "https://localhost:8443/apis/clusterpedia.io/v1beta1/resources/clusters/cluster-example/api/v1/namespaces/clusterpedia-system/pods"You can enable a more relaxed mode by setting the --allow-forward-unsync-resource-request flag to allow forwarding requests for unsynchronized resources.
By default, proxy requests require authentication headers to be passed in the request for the target cluster. These headers include the necessary credentials.
Alternatively, you can enable --allow-pediacluster-config-for-proxy-request to reuse the authentication config defined in the PediaCluster.
$ ./bin/apiserver --help
...
Metrics flags:
--allow-metric-labels stringToString
The map from metric-label to value allow-list of this label. The key's format is <MetricName>,<LabelName>. The value's format is <allowed_value>,<allowed_value>...e.g.
metric1,label1='v1,v2,v3', metric1,label2='v1,v2,v3' metric2,label1='v1,v2,v3'. (default [])
--allow-metric-labels-manifest string
The path to the manifest file that contains the allow-list mapping. The format of the file is the same as the flag --allow-metric-labels. Note that the flag --allow-metric-labels will
override the manifest file.
--disabled-metrics strings
This flag provides an escape hatch for misbehaving metrics. You must provide the fully qualified metric name in order to disable it. Disclaimer: disabling metrics is higher in precedence
than showing hidden metrics.
--show-hidden-metrics-for-version string
The previous version for which you want to show hidden metrics. Only the previous minor version is meaningful, other values will not be allowed. The format is <major>.<minor>, e.g.:
'1.16'. The purpose of this format is make sure you have the opportunity to notice if the next release hides additional metrics, rather than being surprised when they are permanently
removed in the release after that.
...# HELP clusterpedia_build_info [ALPHA] A metric with a constant '1' value labeled by git version, git commit, git tree state, build date, Go version, and compiler from which Clusterpedia was built, and platform on which it is running.
# TYPE clusterpedia_build_info gauge
clusterpedia_build_info{build_date="2025-06-17T07:06:13Z",compiler="gc",git_commit="ee85edb72c541ece9e0b2d7da54c0f442e9a1536",git_tree_state="clean",git_version="v0.9.0-beta.0",go_version="go1.23.10",platform="linux/arm64"} 1
# HELP kubernetes_build_info [ALPHA] A metric with a constant '1' value labeled by major, minor, git version, git commit, git tree state, build date, Go version, and compiler from which Kubernetes was built, and platform on which it is running.
# TYPE kubernetes_build_info gauge
kubernetes_build_info{build_date="2025-06-17T07:06:13Z",compiler="gc",git_commit="ee85edb72c541ece9e0b2d7da54c0f442e9a1536",git_tree_state="clean",git_version="v1.31.2",go_version="go1.23.10",major="1",minor="31",platform="linux/arm64"} 1
Metrics with prefix storage_dbstats are now available.
HELP storage_dbstats_idle The number of idle connections.
# TYPE storage_dbstats_idle gauge
storage_dbstats_idle{db_name="clusterpedia"} 1
# HELP storage_dbstats_in_use The number of connections currently in use.
# TYPE storage_dbstats_in_use gauge
storage_dbstats_in_use{db_name="clusterpedia"} 0
# HELP storage_dbstats_max_idle_closed The total number of connections closed due to SetMaxIdleConns.
# TYPE storage_dbstats_max_idle_closed gauge
storage_dbstats_max_idle_closed{db_name="clusterpedia"} 0
# HELP storage_dbstats_max_idletime_closed The total number of connections closed due to SetConnMaxIdleTime.
# TYPE storage_dbstats_max_idletime_closed gauge
...
If a resource is in the status.resources[].initialListPhase state, it means that the cluster data in Clusterpedia Storage is still being initialized and not yet consistent with the source cluster.
| dependency | old version | new version |
|---|---|---|
| gorm.io/gorm | v1.24.1 | 1.30.0 |
| gorm.io/driver/mysql | v1.4.4 | v1.6.0 |
| gorm.io/driver/postgres | v1.4.5 | v1.6.0 |
| gorm.io/driver/sqlite | v1.4.4 | v1.6.0 |
| gorm.io/datatypes | v1.0.7 | v1.2.5 |
| github.com/jackc/pgx | v4.17.2 | v5.7.5 |
| github.com/go-sql-driver/mysql | v1.6.0 | v1.9.3 |
Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
Clusterpedia v0.9.0-beta.1 Pre-release
Pre-release
Compare
Nothing published for this version
golangci-lint: remove deprecated linters by @Iceber in https://github.com/clusterpedia-io/clusterpedia/pull/671
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.8.0...v0.9.0-beta.0
Full Changelog: v0.8.0...v0.9.0-beta.0
Clusterpedia v0.9.0-beta.0 Pre-release
Pre-release
Compare
bump gorm.io dependencies and fix conflicts by @Iceber in https://github.com/clusterpedia-io/clusterpedia/pull/767
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.9.0-alpha.1...v0.9.0-alpha.2
Full Changelog: v0.9.0-alpha.1...v0.9.0-alpha.2
Clusterpedia v0.9.0-alpha.2 Pre-release
Pre-release
Compare
Nothing published for this version
golangci-lint: remove deprecated linters by @Iceber in https://github.com/clusterpedia-io/clusterpedia/pull/671
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.8.0...v0.9.0-alpha.1
Full Changelog: v0.8.0...v0.9.0-alpha.1
Clusterpedia v0.9.0-alpha.1 Pre-release
Pre-release
Compare
[release/0.8] fix the version order of 'discovery.k8s.io' by @Iceber in https://github.com/clusterpedia-io/clusterpedia/pull/660
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.8.0...v0.8.1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
add clusterpedia openapi (@wawa0210 @huiwq1990, https://github.com/clusterpedia-io/clusterpedia/pull/579, https://github.com/clusterpedia-io/clusterpe
The kube apiserver no longer prints the following error log on a recurring basis:
E1225 07:23:43.660066 1 controller.go:116] loading OpenAPI spec for "v1beta1.clusterpedia.io" failed with: OpenAPI spec does not exist
I1225 07:23:43.660079 1 controller.go:129] OpenAPI AggregationController: action for item v1beta1.clusterpedia.io: Rate Limited Requeue.
Add the --tracing-config-file flag to allow configuration of Otel trace, example configuration
apiVersion: apiserver.config.k8s.io/v1beta1
kind: TracingConfiguration
# default
# endpoint: localhost:4317
samplingRatePerMillion: 1000000
Detailed configuration can be found in TracingConfiguration
This feature will reduce the maximum memory footprint for resource synchronisation.
It is controlled by two feature gates:
StreamHandlePaginatedListForResourceSync: stream handling of paged resources, resources within a pager will be processed as soon as possible instead of waiting until all resources are pulled before calling the ResourceHandler.ForcePaginatedListForResourceSync: force paging, Reflector will sometimes use APIServer's cache, even if paging is specified APIServer will return all resources for performance, then it will skip Reflector's streaming memory optimization.ForcePaginatedListForResourceSync may put extra pressure on the imported cluster APIServer, please be careful to enable it.
clustersynchro-manager add --page-size flags, you can control the page size of the List, the smaller the page size, the smaller the memory consumption, but may also generate more requests to APIServer.
In the future we may be able to configure these in PediaCluster.
In two steps:
--sharding-name flag.spec.shardingName field of PediaClusterPediaCluster will only be synchronised by ClusterSynchroManagers with the same sharding name.
leases.coordination.k8s.io (@27149chen, https://github.com/clusterpedia-io/clusterpedia/pull/615, https://github.com/clusterpedia-io/clusterpedia/pull/622)The leases resource usually needs to be skipped when using resource wildcards or synchronising full resources, and this feature gating ensures that the leases resource is globally skipped without modifying PediaCluster.
In the future, it is more recommended to use https://github.com/clusterpedia-io/clusterpedia/pull/617 to exclude certain resource types.
The cluster synchro has the same source data as kube-state-metrics available to it at sync time, so clusterpedia can easily support functionality similar to kube-state-metrics
# HELP kube_deployment_created [STABLE] Unix creation timestamp
# TYPE kube_deployment_created gauge
kube_deployment_created{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-apiserver"} 1.676557618e+09
kube_deployment_created{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-clustersynchro-manager"} 1.676557618e+09
kube_deployment_created{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-controller-manager"} 1.676557618e+09
kube_deployment_created{cluster="test-14",namespace="kube-system",deployment="coredns"} 1.673603507e+09
# HELP kube_deployment_status_replicas [STABLE] The number of replicas per deployment.
# TYPE kube_deployment_status_replicas gauge
kube_deployment_status_replicas{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-apiserver"} 1
kube_deployment_status_replicas{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-clustersynchro-manager"} 0
kube_deployment_status_replicas{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-controller-manager"} 1
kube_deployment_status_replicas{cluster="test-14",namespace="kube-system",deployment="coredns"} 2
Added --enable-kube-state-metrics and a set of related flags to clustersynchro-manager to control multi-cluster kube-state-metrics capability.
$ ./bin/clustersynchro-manager -h
Metrics server flags:
...
Kube state metrics flags:
...
Returns a more readable error message(storage error: database connection error: bad connection) in the case of driver.DBError
Existing url query - whereSQL needs to splice the value directly in sql, which can easily lead to sql injection problems.
We added three url queries to support parameterized query,give users the ability to prevent sql injection.
| url query | desc | example |
|---|---|---|
whereSQLStatement |
Splice the sql statement after WHERE,Use ? to represent the value. |
whereSQLStatement=(cluster=?) AND (namespace=(?)) |
whereSQLParam |
Multiple whereSQLParam can be set, each corresponding to a question mark. | whereSQLParam=docker-desktop&whereSQLParam=default |
whereSQLJSONParams |
whereSQLParam has the obvious drawback that it can't pass complex structures and special types such as arrays, etc., so you can use whereSQLJSONParam to do so. | whereSQLStatement=(cluster=?) AND (namespace IN (?))&whereSQLJSONParams=WyJkb2NrZXItZGVza3RvcCIsWyJkZWZhdWx0Iiwia3ViZS1zeXN0ZW0iXV0K |
whereSQLJSONParam is a base64 of an array:
$ echo WyJkb2NrZXItZGVza3RvcCIsWyJkZWZhdWx0Iiwia3ViZS1zeXN0ZW0iXV0K | base64 -d
["docker-desktop",["default","kube-system"]]
Parameterised SQL queries are enabled by the AllowParameterizedSQLQuery feature gate
created_at field when updating resource (@flpanbin, https://github.com/clusterpedia-io/clusterpedia/pull/629)Bump golang from 1.19.5 to 1.21.4 (@dependabot @khareyash05, https://github.com/clusterpedia-io/clusterpedia/pull/537, https://github.com/clusterpedia-io/clusterpedia/pull/552, https://github.com/clusterpedia-io/clusterpedia/pull/581, https://github.com/clusterpedia-io/clusterpedia/pull/587, https://github.com/clusterpedia-io/clusterpedia/pull/610)
Bump alpine from 3.17.3 to 3.18.4 (@dependabot, https://github.com/clusterpedia-io/clusterpedia/pull/549, https://github.com/clusterpedia-io/clusterpedia/pull/554, https://github.com/clusterpedia-io/clusterpedia/pull/573)
Bump Kubernetes from v1.26.3 to v1.28.4 (@Iceber @wawa0210, https://github.com/clusterpedia-io/clusterpedia/pull/538, https://github.com/clusterpedia-io/clusterpedia/pull/579, https://github.com/clusterpedia-io/clusterpedia/pull/606)
Use kustomize to install clusterpedia (@khareyash05 @Iceber, https://github.com/clusterpedia-io/clusterpedia/pull/551, https://github.com/clusterpedia-io/clusterpedia/pull/556, https://github.com/clusterpedia-io/clusterpedia/pull/558)
$ kubectl kustomize ./kustomize | kubectl apply -f -
Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
add clusterpedia openapi (@wawa0210 @huiwq1990, https://github.com/clusterpedia-io/clusterpedia/pull/579, https://github.com/clusterpedia-io/clusterpe
The kube apiserver no longer prints the following error log on a recurring basis:
E1225 07:23:43.660066 1 controller.go:116] loading OpenAPI spec for "v1beta1.clusterpedia.io" failed with: OpenAPI spec does not exist
I1225 07:23:43.660079 1 controller.go:129] OpenAPI AggregationController: action for item v1beta1.clusterpedia.io: Rate Limited Requeue.
Add the --tracing-config-file flag to allow configuration of Otel trace, example configuration
apiVersion: apiserver.config.k8s.io/v1beta1
kind: TracingConfiguration
# default
# endpoint: localhost:4317
samplingRatePerMillion: 1000000
Detailed configuration can be found in TracingConfiguration
This feature will reduce the maximum memory footprint for resource synchronisation.
It is controlled by two feature gates:
StreamHandlePaginatedListForResourceSync: stream handling of paged resources, resources within a pager will be processed as soon as possible instead of waiting until all resources are pulled before calling the ResourceHandler.ForcePaginatedListForResourceSync: force paging, Reflector will sometimes use APIServer's cache, even if paging is specified APIServer will return all resources for performance, then it will skip Reflector's streaming memory optimization.ForcePaginatedListForResourceSync may put extra pressure on the imported cluster APIServer, please be careful to enable it.
clustersynchro-manager add --page-size flags, you can control the page size of the List, the smaller the page size, the smaller the memory consumption, but may also generate more requests to APIServer.
In the future we may be able to configure these in PediaCluster.
In two steps:
--sharding-name flag.spec.shardingName field of PediaClusterPediaCluster will only be synchronised by ClusterSynchroManagers with the same sharding name.
leases.coordination.k8s.io (@27149chen, https://github.com/clusterpedia-io/clusterpedia/pull/615, https://github.com/clusterpedia-io/clusterpedia/pull/622)The leases resource usually needs to be skipped when using resource wildcards or synchronising full resources, and this feature gating ensures that the leases resource is globally skipped without modifying PediaCluster.
In the future, it is more recommended to use https://github.com/clusterpedia-io/clusterpedia/pull/617 to exclude certain resource types.
The cluster synchro has the same source data as kube-state-metrics available to it at sync time, so clusterpedia can easily support functionality similar to kube-state-metrics
# HELP kube_deployment_created [STABLE] Unix creation timestamp
# TYPE kube_deployment_created gauge
kube_deployment_created{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-apiserver"} 1.676557618e+09
kube_deployment_created{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-clustersynchro-manager"} 1.676557618e+09
kube_deployment_created{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-controller-manager"} 1.676557618e+09
kube_deployment_created{cluster="test-14",namespace="kube-system",deployment="coredns"} 1.673603507e+09
# HELP kube_deployment_status_replicas [STABLE] The number of replicas per deployment.
# TYPE kube_deployment_status_replicas gauge
kube_deployment_status_replicas{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-apiserver"} 1
kube_deployment_status_replicas{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-clustersynchro-manager"} 0
kube_deployment_status_replicas{cluster="test-14",namespace="clusterpedia-system",deployment="clusterpedia-controller-manager"} 1
kube_deployment_status_replicas{cluster="test-14",namespace="kube-system",deployment="coredns"} 2
Added --enable-kube-state-metrics and a set of related commands, flags, to clustersynchro-manager to control multi-cluster kube-state-metrics capability.
$ ./bin/clustersynchro-manager -h
Metrics server flags:
--metrics-disable-gzip-encoding
Gzip responses when requested by clients via 'Accept-Encoding: gzip' header.
--metrics-host string
Host to expose clustersynchro manager metrics on. (default "::")
--metrics-port int
Port to expose clustersynchro manager metrics on. (default 8081)
--metrics-tls-config string
Path to the TLS configuration file of metrics
Kube state metrics flags:
--enable-kube-state-metrics
Enabled kube state metrics
--kube-state-metrics-host string
Host to expose kube state metrics on. (default "::")
--kube-state-metrics-metric-allowlist string
Comma-separated list of metrics to be exposed. This list comprises of exact metric names
and/or regex patterns. The allowlist and denylist are mutually exclusive.
--kube-state-metrics-metric-denylist string
Comma-separated list of metrics not to be enabled. This list comprises of exact metric
names and/or regex patterns. The allowlist and denylist are mutually exclusive.
--kube-state-metrics-metric-opt-in-list string
Comma-separated list of metrics which are opt-in and not enabled by default. This is in
addition to the metric allow- and denylists
--kube-state-metrics-namespaces string
Comma-separated list of namespaces to be enabled. Defaults to ""
--kube-state-metrics-namespaces-denylist string
Comma-separated list of namespaces not to be enabled. If namespaces and
namespaces-denylist are both set, only namespaces that are excluded in namespaces-denylist
will be used.
--kube-state-metrics-port int
Port to expose kube state metrics on. (default 8080)
--kube-state-metrics-resources string
Comma-separated list of Resources to be enabled. Supported resources:
"cronjobs,daemonsets,deployments,ingressclasses,ingresses,jobs,namespaces,nodes,pods,replicasets,secrets,services,statefulsets" (default "deployments,pods,services")
Returns a more readable error message(storage error: database connection error: bad connection) in the case of driver.DBError
Existing url query - whereSQL needs to splice the value directly in sql, which can easily lead to sql injection problems.
We added three url queries to support parameterized query,give users the ability to prevent sql injection.
| url query | desc | example |
|---|---|---|
whereSQLStatement |
Splice the sql statement after WHERE,Use ? to represent the value. |
whereSQLStatement=(cluster=?) AND (namespace=(?)) |
whereSQLParam |
Multiple whereSQLParam can be set, each corresponding to a question mark. | whereSQLParam=docker-desktop&whereSQLParam=default |
whereSQLJSONParam |
whereSQLParam has the obvious drawback that it can't pass complex structures and special types such as arrays, etc., so you can use whereSQLJSONParam to do so. | whereSQLStatement=(cluster=?) AND (namespace IN (?))&whereSQLJSONParams=WyJkb2NrZXItZGVza3RvcCIsWyJkZWZhdWx0Iiwia3ViZS1zeXN0ZW0iXV0K |
whereSQLJSONParam is a base64 of an array:
$ echo WyJkb2NrZXItZGVza3RvcCIsWyJkZWZhdWx0Iiwia3ViZS1zeXN0ZW0iXV0K | base64 -d
["docker-desktop",["default","kube-system"]]
Parameterised SQL queries are enabled by the AllowParameterizedSQLQuery feature gate
created_at field when updating resource (@flpanbin, https://github.com/clusterpedia-io/clusterpedia/pull/629)Bump golang from 1.19.5 to 1.21.4 (@dependabot @khareyash05, https://github.com/clusterpedia-io/clusterpedia/pull/537, https://github.com/clusterpedia-io/clusterpedia/pull/552, https://github.com/clusterpedia-io/clusterpedia/pull/581, https://github.com/clusterpedia-io/clusterpedia/pull/587, https://github.com/clusterpedia-io/clusterpedia/pull/610)
Bump alpine from 3.17.3 to 3.18.4 (@dependabot, https://github.com/clusterpedia-io/clusterpedia/pull/549, https://github.com/clusterpedia-io/clusterpedia/pull/554, https://github.com/clusterpedia-io/clusterpedia/pull/573)
Bump Kubernetes from v1.26.3 to v1.28.4 (@Iceber @wawa0210, https://github.com/clusterpedia-io/clusterpedia/pull/538, https://github.com/clusterpedia-io/clusterpedia/pull/579, https://github.com/clusterpedia-io/clusterpedia/pull/606)
Use kustomize to install clusterpedia (@khareyash05 @Iceber, https://github.com/clusterpedia-io/clusterpedia/pull/551, https://github.com/clusterpedia-io/clusterpedia/pull/556, https://github.com/clusterpedia-io/clusterpedia/pull/558)
$ kubectl kustomize ./kustomize | kubectl apply -f -
Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[release/0.7] fix the version order of 'discovery.k8s.io' by @Iceber in https://github.com/clusterpedia-io/clusterpedia/pull/661
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.7.1...v0.7.2
[release/0.7] fix the version order of 'discovery.k8s.io' by @Iceber in https://github.com/clusterpedia-io/clusterpedia/pull/661
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.7.1...v0.7.2-rc.0
Nothing published for this version
[release/0.7] bump kwokctl by @wzshiming in https://github.com/clusterpedia-io/clusterpedia/pull/605
[release/0.7] bump kwokctl by @wzshiming in https://github.com/clusterpedia-io/clusterpedia/pull/605
[release/0.7] feat: added new parameters for parameterized query by @nekomeowww in https://github.com/clusterpedia-io/clusterpedia/pull/603
Added three search queries - whereSQLStatement, whereSQLParam, and whereSQLJSONParams to make the internalstorage layer support parameterised sql. More detailed introduction to use
[release/0.7] add featureGate IgnoreSyncLease to stop sync leases.coordination.k8s.io by @27149chen in https://github.com/clusterpedia-io/clusterpedia/pull/621 https://github.com/clusterpedia-io/clusterpedia/pull/623
Added a feature gate - IgnoreSyncLease that does not synchronise the leases.coordination.k8s.io resource regardless of user configuration in PediaCluster
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.7.0...v0.7.1
[release/0.7] bump kwokctl by @wzshiming in https://github.com/clusterpedia-io/clusterpedia/pull/605
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.7.0...v0.7.1-rc.1
Nothing published for this version
[release/0.7] bump kwokctl by @wzshiming in https://github.com/clusterpedia-io/clusterpedia/pull/605
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.7.0...v0.7.1-rc.0
Nothing published for this version
One column per quarter.