Releases: apecloud/kubeblocks
KubeBlocks v0.7.1
What's Changed
- feat: support KubeBlocks component postStart hook by @Y-Rookie in #5824
- fix: get lorry container by @xuriwuyun in #5897
- chore: optimize cluster patch post start done annotation by @Y-Rookie in #5898
- chore: redis secondary startup waiting util primary ready by @Y-Rookie in #5900
Full Changelog: v0.7.0...v0.7.1
KubeBlocks v0.6.5
Full Changelog: v0.6.4...v0.6.5
KubeBlocks v0.7.0
KubeBlocks 0.7.0 (2023-11-06)
We're thrilled to announce the official release of KubeBlocks v0.7.0! 🚀 🎉 🎈
This version supports the function of referencing external components, making it possible to assemble building blocks - add-ons more flexibly.
Backup is decoupled from the cluster with a separate API, and three new object storage services from public cloud providers are added as backup storage options.
Thanks to the support of our community, KubeBlocks has included 31 open-source database engines, including MariaDB, Elasticsearch, Pulsar, Pika and more, providing more choices for you.
We would like to extend our appreciation to all contributors who helped make this release happen.
Highlights
Support referencing external components
The new feature of referencing external components brings greater flexibility to KubeBlocks clusters, allowing them to be assembled like building blocks to create new clusters. Currently, this function can be applied to two scenarios. Firstly, you can reference external components, such as external Zookeeper, that are not created and managed by KubeBlocks. You just need to define the service description and Kubernetes deployment is not required. Another scenario is that clusters created by KubeBlocks can be referenced as components by other clusters. For example, a Redis Sentinel cluster can be referenced by other Redis Replication clusters for managing high-availability.
Decouple cluster and backup #4877, #4494
The backup policy supports customizing backup methods, allowing you to specify a backup method when creating a backup. The BackupTool has been replaced with the ActionSet CRD, which defines actions for backup and restore. Three new object storage services, GCS, OBS, and COS, have been added as backup storage options. Besides, BackupSchedule is added to decouple automatic scheduling configurations from BackupPolicy that can be used for both automatic and manual backup.
Support Pika v3.5
Pika, developed by Qihoo, is an open-source NoSQL database that is compatible with Redis interfaces such as string, hash, list, zset, and set operations. It offers a cost advantage in 100 GB level and larger data volumes. Switching from Redis to Pika is seamless, as it maintains the same usage and operation habits. Currently, KubeBlocks has already supported deploying the sharded cluster mode from Pika v3.5. After a cluster is created by KubeBlocks, Pika is automatically added to the Codis cluster with rebalancing applied. KubeBlocks can also automatically manage Pika Primary-Secondary clusters, which can automatically add one primary with one or multiple secondaries.
What's Changed
New features
Pulsar #4587
Supports multiple Pulsar clusters that can share a zookeeper component.
Backup and restore
Supports three object storage services, namely GCS(Google Cloud Storage), OBS (Huawei Cloud Object Storage), and COS (Tencent Cloud Object Storage), as backup storage options.
Compatibility
Compatible with Huawei Cloud. #4697
Support multiple open-source engines
The table below provides an overview of the integrated engines and their capabilities in KubeBlocks.
V0.7.0 | Vscale | Hscale | Volumeexpand | Stop/Start | Restart | Backup/Restore | Logs | Config | Upgrade (DB engine version) | Account | Failover | Switchover | Monitor |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
apecloud-mysql | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | ✔️ | ✔️ | ✔️ | ✔️ |
postgresql | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
redis | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | ✔️ | ✔️ | N/A | ✔️ |
mongodb | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | ✔️ | ✔️ | ✔️ |
kafka | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | ✔️ | N/A | N/A | N/A | N/A | ✔️ |
pulsar | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | ✔️ | N/A | N/A | N/A | N/A | ✔️ |
weaviate | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | ✔️ | N/A | N/A | N/A | N/A | ✔️ |
qdrant | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | ✔️ |
greptimedb | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
nebula | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
risingwave | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
starrocks | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
etcd | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
oceanbase | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | |
foxlake | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
orioledb | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
oracle-mysql | ✔️ | N/A | ✔️ | ✔️ | ✔️ | ✔️ | N/A | ✔️ | N/A | N/A | N/A | N/A | N/A |
official-postgresql | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
mysql (Primary-Secondary replication) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ✔️ |
openldap | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
neon | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
opensearch | ✔️ | N/A | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
vllm | N/A | N/A | N/A | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
ggml | N/A | N/A | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | |
milvus | ✔️ | N/A | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
elasticsearch | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
tdengine | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
clickhouse | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
PolarDB-X | ✔️ | ✔️ | N/A | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A ... |
KubeBlocks v0.6.4
What's Changed
Full Changelog: v0.6.3...v0.6.4
KubeBlocks v0.6.3
What's Changed
- fix: probe crash when create cm failed by @xuriwuyun in #5260
- feat: support to specify volume mode when creating clusters by @leon-inf in #5333
- fix: reduce mongodb log size by @xuriwuyun in #5334
Full Changelog: v0.6.2...v0.6.3
KubeBlocks v0.6.2
What's Changed
- feat: mongodb support ft by @xuriwuyun in #4960
- fix: mongodb connect by @xuriwuyun in #5032
- chore: add options --set logCollector.enabled for apecloud-mysql addon by @sophon-zt in #5042
Full Changelog: v0.6.1...v0.6.2
KubeBlocks v0.6.1
Full Changelog: v0.6.0...v0.6.1
KubeBlocks v0.6.0
KubeBlocks 0.6.0 (2023-08-18)
We are happy to announce the official release of KubeBlocks 0.6.0! 🚀 🎉 🎈
This version supports stream computing engines Kafka and Pulsar and supports MySQL read-write splitting, introduces an interactive parameter configuration method.
We would like to extend our appreciation to all contributors who helped make this release happen.
Highlights
- KubeBlocks supports Kafka v3.3
- Apache Kafka is an open-source distributed event storage and streaming computing system that provides high reliability, throughput, and low latency for data pipelines, streaming analysis, and data integration. It is widely used in log collection and metric monitoring scenarios. KubeBlocks supports Kafka v3.3, which announced that KRaft meets production requirements, providing better partition scalability and resilience, and saving the additional costs of ZooKeeper. In addition, KubeBlocks also supports pushing data changes from MySQL and PostgreSQL to Kafka, making it easier for users to further process and handle the data.
- KubeBlocks supports Pulsar v2.11
- Apache Pulsar is an open-source distributed messaging and stream processing platform. It aims to provide scalability, high performance, and reliability to meet the needs of modern data processing and real-time messaging. KubeBlocks supports Apache Pulsar v2.11, and compared to traditional deployment methods, KubeBlocks can automate fault tolerance, scaling, and other day2 operations.
- KubeBlocks supports MySQL read-write splitting
- Read-write splitting is designed to improve the read-only processing capability of a MySQL database cluster. All write queries are sent to the master node, while read-only queries that do not modify data are distributed to multiple slave nodes. Read-write splitting is used together with the MySQL Raft Group cluster, which automatically detects changes in the master node and uses the current master node of the cluster to achieve failover. Set
read_write_splitting_policy
as read-write splitting at the global or session level, and the default policy isLEAST_CURRENT_OPERATIONS
, which routes read-only queries to the slave node with the least active operations. The MySQL Raft Group cluster supports up to 5 nodes.
- Read-write splitting is designed to improve the read-only processing capability of a MySQL database cluster. All write queries are sent to the master node, while read-only queries that do not modify data are distributed to multiple slave nodes. Read-write splitting is used together with the MySQL Raft Group cluster, which automatically detects changes in the master node and uses the current master node of the cluster to achieve failover. Set
Breaking changes
- For KubeBlocks v0.6, newly created Redis and PG clusters need password to connect, while v0.5 used to allow password-free login
- For KubeBlocks v0.6, the backup and restore function is updated greatly. You need to manually upgrade the 0.5 version cluster to 0.6 and update backupPolicy to use the new function.
- For KubeBlocks v0.6, since password-free login function is not supported for Postgres cluster, when restoring cluster upgraded from v0.5, if the new restored cluster is in creating status for a long time, you can check the pod logs to see whether there is
password authentication failed
error, you can update password to fix this.
Acknowledgements
Thanks to everyone who made this release possible!
What's New
Pulsar
- Cluster lifecycle management and operation management, supporting the creation of Pulsar clusters, cluster deletion, cluster restarting, horizontal scaling, vertical scaling, volume expanding, and parameter modifying.
- For monitoring, support performance monitoring of CPU, memory, network read/write traffic, and more for ZooKeeper, BookKeeper, and Broker.
Kafka
- Cluster lifecycle management and operation management, supporting cluster creation, deletion, horizontal scaling, vertical scaling, volume expanding, and modifying parameters.
- Horizontal scaling: In combined mode, broker replicas support 1, 3, or 5 copies. In separated mode, brokers support 1 to 100 copies and Kafka controllers support 1, 3, or 5 copies.
- For monitoring, supports performance monitoring of Broker's CPU, memory, network read/write traffic, etc.
MySQL
- MySQL RaftGroup Cluster supports Switchover
- MySQL RaftGroup Cluster supports MySQL read-write splitting.
- Data Recovery, Non-Destructive Recovery by Point-in-time(PITR). It's a beta feature.
- Support proxy enable when creating cluster. (Beta)
- The default specification of Vitess proxy can meet the vast majority of user scenarios. Vitess proxy automatically triggers resource increase or decrease based on changes in database nodes and node specifications, without manual operation. The CPU of Vitess proxy is 1/6 of the total number of CPU cores in the cluster nodes (three nodes), rounded up to 0.5c granularity, with a minimum of 0.5c and a maximum of 64c. The default number of replicas is 1, and currently, modifying the number of replicas is not supported
- Connection Address: The proxy has a default connection address that supports read-write splitting. The expose command can generate VPC addresses and public network addresses for the proxy connection address.
- Supports setting Vitess proxy read-write splitting policies.
PostgreSQL
- Support switchover for PG Replication Cluster
- Built-in pgBouncer
MongoDB
- MongoDB replicaset supports switchover
- Data recovery, non-destructive PITR (Beta)
Data migration
- Add
kbcli migration
command, including creating migration tasks, viewing migration task list, viewing migration task details, terminating migration tasks, viewing logs, viewing migration templates, and other functions. Supports full migration and incremental synchronization. - Support MySQL data migration from MySQL 8.0 to MySQL 8.0.
- Support PostgreSQL data migration from PostgreSQL 14 to PostgreSQL 14.
- Support MongoDB data migration from MongoDB5.X/6.0 to MongoDB 5.X/6.0.
Compatibility
- Support remote write to Prometheus server through Prometheus v2.41 - 2.45 compatibility testing
- Adapt kbcli to package managers of Ubuntu and Amazon Linux 2
- Adapt kbcli to Windows PowerShell and package managers
- Support local environment running on Ubuntu and Amazon Linux 2 for kbcli playground
- Support local environment running on Windows for kbcli playground
Usability
- kbcli supports users to modify KubeBlocks parameters with local editing tools on the operating system
- kbcli supports the "fault-inject" extension for fault injection
- kbcli supports the "report" command to package cluster context information into a compressed file for problem troubleshooting assistance
- kbcli supports interactive editing of configuration information for DB clusters. For cluster create, support --edit to interactively edit the yaml, and show the cluster summary before create.
- Support canceling Hscale/Vscale OpsRequest that are running (Beta)
- Add kbcli playground Grafana overview page
- Kbcli alert can set email server
- Support initializing the creation of databases and users
- Specify a configuration file for initialization settings when installing KubeBlocks
- Disk full lock for MySQL, PostgreSQL, MongoDB: When the database storage space is about to be full (disk usage is more than 90%), set the database to a read-only state.
Backup and Restore
- The backup storage repository (backupRepo) refers to the target path where backup files are stored. KubeBlocks supports public cloud object storage and S3-compatible object storage.
- Support modifying cluster configuration when restoring a new cluster
- Add "describe-backup" command to view backup details
Observability
- Support integration with external monitoring systems include Prometheus, VictoriaMetrics, and AMP. Cluster performance monitoring metrics are output to the target monitoring system through remote write.
- Real-time dumping of operation logs for K8s/KubeBlocks clusters to object storage, divided by time and size, and providing read-only addresses
- Real-time dumping of error logs for K8s/KubeBlocks clusters to object storage, divided by time and size, and providing read-only addresses
Bug Fixes
- There is a quota problem, no default resource limits are set for containers such as metrics. (#2738, @nashtsai)
- cli ops command output lost ops name (#2904, @ldming)
- probe event lost (#3172, @xuriwuyun)
- update probe internal module (#3414, @xuriwuyun)
- cli playground init cluster without sa, role and rolebinding (#3428, @ldming)
- cli created cluster with wrong sa name (#3500, @ldming)
- The cluster status and pod status are inconsistent. clusters can terminate faster than pods. (#3558, @lynnleelhl)
- enable consensus_set controller by feature gate (#3616, @free6om)
- licensing description (#3664, @free6om)
- change preflight checks rule for low spec machine in test case (#3722, @yangmeilly)
- redis prohibits passwordless access by default (#3726,@Y-Rookie)
- mongodb post start script (#3956, @xuriwuyun)
- mongodb pod terminating takes too long time (#3971, @xuriwuyun)
- mongodb restore problem, reset password (#3987, @xuriwuyun)
- MongoDB does not receive signals when terminating pods. (#3990, @xuriwuyun)
- add more judgements for mongodb replset initialization (#4034, @xuriwuyun)
- parallel_transformer concurrent map writes ([#4079](https:...
KubeBlocks v0.5.3
What's Changed
- chore: pick connection-auth-error related fixes to release by @shanshanying in #3714
- fix: merge service annotations has logic error by @yimeisun in #3830
- chore: have Addon's chartLocationURL attribute setup as '.Values.addonChartLocationBase' template value by @nashtsai in #3899
- fix: set failed when volumesnapshot config error (#3816) by @wangyelei in #3918
- chore: addon support to set private helm registry by @ldming in #3920
- chore: logfile backup fail with the same name cluster by @wangyelei in #3927
- chore: disable performance schema for smaller class by @ldming in #3934
- fix: pitr recoverable time is incorrect by @wangyelei in #3943
- fix: mongodb post start script by @xuriwuyun in #3956
- fix: mongodb pod terminating take too long time by @xuriwuyun in #3972
Full Changelog: v0.5.2...v0.5.3
KubeBlocks v0.5.2
What's Changed
- chore: remove volume from class by @iziang in #3462
- docs: adjust docs 5.0 (#3597) by @ldming in #3600
- docs: cherry pick from main by @michelle-0808 in #3618
- chore: remove mysql classes by @iziang in #3634
- chore: add missing delphic chart by @iziang in #3635
- chore: update postgresql wal relative params and hba.conf by @Y-Rookie in #3638
- fix: do not create fsnotify.Watcher when using sync mode (#3617) by @sophon-zt in #3645
- fix: cli playground error when repeatedly init by @ldming in #3651
- chore: release failed test case by @ldming in #3656
- fix: only call leader when scale by @lynnleelhl in #3677
- chore: cp embedded wesql images by @demian0110 in #3687
- fix: a typo in doc by @xtcyclist in #3704
New Contributors
- @xtcyclist made their first contribution in #3704
Full Changelog: v0.5.1...v0.5.2