The Encyclopedia of Kubernetes clusters
# sqlite.yaml
type: sqlite
dsn: file:test.db
When using the sqlite storage layer, it is recommended to use the binding-apiserver cmd.
type: mysql
mysql:
recoverableErrNumbers: [1053, 1205, 1290]
For recoverable errors, the synchro assumes that the storage layer is recoverable and will permanently retry handling the resources until it encounters other errors or succeeds.
ParseTime of mysql to be true (@RuliXu, https://github.com/clusterpedia-io/clusterpedia/pull/530)Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
# sqlite.yaml
type: sqlite
dsn: file:test.db
When using the sqlite storage layer, it is recommended to use the binding-apiserver cmd.
type: mysql
mysql:
recoverableErrNumbers: [1053, 1205, 1290]
For recoverable errors, the synchro assumes that the storage layer is recoverable and will permanently retry handling the resources until it encounters other errors or succeeds.
ParseTime of mysql to be true (@RuliXu, https://github.com/clusterpedia-io/clusterpedia/pull/530)Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
# sqlite.yaml
type: sqlite
dsn: file:test.db
When using the sqlite storage layer, it is recommended to use the binding-apiserver cmd.
type: mysql
mysql:
recoverableErrNumbers: [1053, 1205, 1290]
For recoverable errors, the synchro assumes that the storage layer is recoverable and will permanently retry handling the resources until it encounters other errors or succeeds.
ParseTime of mysql to be true (@RuliXu, https://github.com/clusterpedia-io/clusterpedia/pull/530)Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.6.3...v0.6.4
Full Changelog: https://github.com/clusterpedia-io/clusterpedia/compare/v0.6.3...v0.6.4
Thanks everyone who contributed to this release!
The following users (sort alphabetically) are those who committed much in this release. Thank you!
type: mysql
mysql:
recoverableErrNumbers:
- 1029
or
type: postgres
postgres:
recoverableErrCodes:
- "57P01"
$ CLUSTERPEDIA_URL="http://127.0.0.1:8080/apis/clusterpedia.io/v1beta1/resources"
$ FAKE_CLUSTER="unknown"
$ curl $CLUSTERPEDIA_URL/clusters/$FAKE_CLUSTER/apis/apps/v1/deployments
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "the server could not find the requested cluster",
"reason": "BadRequest",
"code": 400
}
The request of the cluster health check using the same TCP connection as the resource synchronized informer, which may cause TCP blocking and increased health check latency if a large number of informers are started for the first time.
We add a feature gate - HealthCheckerWithStandaloneTCP to allow users to use a standalone tcp for health checks.
./clustersynchro-manager --feature-gates=HealthCheckerWithStandaloneTCP=true
Previously we set the number of workers used to reconcile PediaClusters to 1,
but now we allow the number of workers to be specified by --worker-number flag, which defaults to 5
./clustersynchro-manager --worker-number=5
The dynamic discovery manager starts and stops based on cluster status (#456, @Iceber)
The interval between health checks does not include the execution time (#440, @cleverhu)
Resolve Cluster Healthy Condition Message isn't empty (#347, @qiuming520)
groups=* is given (#407, @27149chen)driver.ErrBadConn to recoverable errors (#463, @cleverhu)notin and != operators in JSONBuilder (#404, @Iceber)status.version of PediaCluster as optional field (#373, @kuangcheng66)$ CLUSTERPEDIA_URL="http://127.0.0.1:8080/apis/clusterpedia.io/v1beta1/resources"
$ FAKE_CLUSTER="unknown"
$ curl $CLUSTERPEDIA_URL/clusters/$FAKE_CLUSTER/apis/apps/v1/deployments
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "the server could not find the requested cluster",
"reason": "BadRequest",
"code": 400
}
The request of the cluster health check using the same TCP connection as the resource synchronized informer, which may cause TCP blocking and increased health check latency if a large number of informers are started for the first time.
We add a feature gate - HealthCheckerWithStandaloneTCP to allow users to use a standalone tcp for health checks.
./clustersynchro-manager --feature-gates=HealthCheckerWithStandaloneTCP=true
Previously we set the number of workers used to reconcile PediaClusters to 1,
but now we allow the number of workers to be specified by --worker-number flag, which defaults to 5
./clustersynchro-manager --worker-number=5
The dynamic discovery manager starts and stops based on cluster status (#456, @Iceber)
The interval between health checks does not include the execution time (#440, @cleverhu)
Resolve Cluster Healthy Condition Message isn't empty (#347, @qiuming520)
groups=* is given (#407, @27149chen)driver.ErrBadConn to recoverable errors (#463, @cleverhu)notin and != operators in JSONBuilder (#404, @Iceber)status.version of PediaCluster as optional field (#373, @kuangcheng66)