Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: v0.8.0.md

Exciting news! KubeBlocks v0.8.0 is officially released! KubeBlocks v0.8.0 takes a big step forward in user experience by introducing component-level APIs, which makes standardized building blocks even smaller and more convenient to be reused. For example, popular Key-Value store components like ETCD and/or ZK services, which are widely used as state store in various type of database clusters, can be directly referenced. We also made Vitess Proxy a standard component, so that developers do not need to repeat the heavy lifting work when defining the read-write separation topology of MySQL or PostgreSQL DB engines. Further more, the Addon mechanism has also been significantly improved, as database engines' Helm charts is decoupled from the release stream. When integrating the new database engine, we found deficiencies in the abstract design of KubeBlocks. v0.8.0 splits Component from Cluster definition to better support database types with multiple components. It supports variable references between Components, including ConfigMap, Secret, Service, ServiceReference and other variable reference types, which can better connect the relationships between components and lay the foundation for building clusters with different topologies. In previous versions, Helm charts for database engines were located in the "deploy" directory, tightly coupled with the KubeBlocks Operator. However, this caused two problems: first, upgrading KubeBlocks would trigger the upgrade of the database engine; second, upgrading the database engine would overwrite existing CD/CV, restarting all the clusters. To address these problems, KubeBlocks v0.8.0 has placed the database engines into a standalone repository called "kubeblocks-addon", with version numbers added for both the database engines and associated resources. This ensures that new installations do not overwrite existing resources, thereby eliminating cluster restarts. And KubeBlocks provides the "kbcli addon" command, which allows users to download, install, use, and uninstall specific engine versions. Prior to v0.8.0, KubeBlocks upgrades might trigger a restart of the database cluster. KubeBlocks v0.8.0, with the new Component API and Addon helm chart storage mechanism, this problem has been solved to a certain extent. We will continue to optimize the design of multiple versions in the future, and ultimately achieve burden-free upgrades. Supports multiple Pulsar clusters that can share a zookeeper component. Integrates monitoring, scale-out and high

Adds new active and standby cluster modes to support the complete life cycle and integrate backup, recovery, monitoring and switching The Community Edition of MySQL 5.7 and 8.0 supports a full lifecycle with integrated backup recovery, monitoring, and HA. Adds log audit function on ApeCloud MySQL. Postgresql supports wal-g full backup and PITR. Supports custom OpsRequest, enabling specific operational actions. For example, creating and deleting Kafka topics. Enables NodePort access for Redis. Compatible with the pre-refactored ClusterDefinition and ClusterVersion APIs. opsRequest supports task queuing, allowing users to submit multiple tasks at once. For tasks that cannot run concurrently, the system will automatically execute the next task after the previous one is completed #5887 During KubeBlocks installation, specifying the image repository address is now possible, speeding up image pull. Unifies configuration and management for logs and metrics collection. Adds interface definition in ComponentDefinition #5031 Adds OpsDefinition API #5940 Adds PreDelete Action for ActionSet . You can perform this action before deleting backup. #6361 Stability Stability testings and related improvements Enhances addon sub-command, you can install the addon from the index repository. (PROVIDE LINKS FOR HOWTO?) In KubeBlocks 0.8.0, we have made improvements to Oceanbase (adding functions like creating master/standby clusters, support host network and dynamic ports, support backup/recovery, monitoring, logging, etc.), the clusters created in version 0.7.0 are incompatible with those in version 0.8.0, so if you are using the 0.7.0 version to manage Oceanbase, you are recommended to upgrade to the 0.8.0 version of KubeBlocks. Upgrade KubeBlocks first, then upgrade Oceanbase Addon. It is recommended to use OceanBase official data import and export tools (OBLOADER and OBDUMPER) to migrate data. KubeBlocks 0.8.0 streamlines the data engines installed by default when deploying KubeBlocks by removing greptime, influxdb, neon, oracle-mysql, oroledb, tdengine, mariadb, nebula, risingwave, starrocks, tidb, zookeeper. You can install them on-demand from the addon indexing repository with the kbcli addon subcommand or the kubectl apply command; if you are upgrading from a lower version, follow the upgrade manual to avoid deleting addons that are in use, which may affect running clusters. The Helm Chart of KubeBlocks 0.8.0 no longer contains dependent CRDs. When installing or upgrading KubeBlocks with the helm command, you need to install the corresponding CRDs before installing or upgrading KubeBlocks, please refer to the upgrade manual for details.