diff --git a/blogs/en/5-network-modes-for-kubeblocks-for-redis.mdx b/blogs/en/5-network-modes-for-kubeblocks-for-redis.mdx index 7fae119..a4e1b96 100644 --- a/blogs/en/5-network-modes-for-kubeblocks-for-redis.mdx +++ b/blogs/en/5-network-modes-for-kubeblocks-for-redis.mdx @@ -12,7 +12,7 @@ keywords: Redis Operator, Kubernetes, Networking, Headless Service, NodePort, Lo image: /img/blogs/thumbnails/blog-redis-network-modes.png --- -# Mastering Redis Network Modes in Kubernetes with KubeBlocks +# Mastering [Redis](/docs/preview/kubeblocks-for-redis) Network Modes in Kubernetes with KubeBlocks ## I. Introduction: KubeBlocks and the Importance of Networking @@ -424,4 +424,12 @@ The 5 network modes supported by KubeBlocks fully cover various scenarios from d ## References - [1] SpiderPool: https://github.com/spidernet-io/spiderpool -- [2] InstanceSet controller:https://github.com/apecloud/spiderpool/tree/support/preserve-pod-ip-until-sts-is-deleted \ No newline at end of file +- [2] InstanceSet controller:https://github.com/apecloud/spiderpool/tree/support/preserve-pod-ip-until-sts-is-deleted + +## Related + +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [Redis Containerization: Challenges and Solutions](/blog/redis-containerization) +- [Redis on KubeBlocks](/blog/redis-on-kb) +- [Migrate Redis in Kuaishou from Bare Metal to Kubernetes](/blog/migrate-redis-in-kuaishou-from-bare-metal-to-k8s) +- [Run Redis on K8s: Kuaishou's Solution with KubeBlocks](/blog/run-redis-on-k8s-kuaishou-solution-with-kubeblocks) diff --git a/blogs/en/a-testing-report-for-optimizing-PG-performance-on-kubeblocks.mdx b/blogs/en/a-testing-report-for-optimizing-PG-performance-on-kubeblocks.mdx index fe8da87..352ffc0 100644 --- a/blogs/en/a-testing-report-for-optimizing-PG-performance-on-kubeblocks.mdx +++ b/blogs/en/a-testing-report-for-optimizing-PG-performance-on-kubeblocks.mdx @@ -12,7 +12,7 @@ Keywords: PostgreSQL, Kubernetes Operator, KubeBlocks, Performance Tuning, Bench image: /img/blogs/thumbnails/blog-pg.png --- -# PostgreSQL Performance Tuning on Kubernetes: A KubeBlocks Deep Dive +# [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) Performance Tuning on Kubernetes: A KubeBlocks Deep Dive ## Introduction @@ -506,3 +506,10 @@ After introducing pgBouncer, PG could handle more connections without significan 5. By default, PG is IO-bound, but after the optimizations mentioned above, it becomes CPU-bound. 6. ACK and SLB networks are robust, meeting performance and stability requirements. 7. K8s offers convenient adjustments to filesystem and PG parameters, and different combinations of tests can be conducted rapidly and effectively. Moreover, running a database on K8s does not incur performance degradation. With general tuning, the database can exhibit excellent results. K8s provides more freedom and autonomy to users with fewer restrictions. + +## Related + +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [Does Running MySQL on Kubernetes Lead to Significant Performance Degradation?](/blog/does-running-mysql-on-kubernetes-lead-to-significant-performance-degradation) +- [Does Containerization Affect the Performance of Databases?](/blog/does-containerization-affect-the-performance-of-databases) +- [Is Kubernetes a Database?](/blog/is-k8s-a-database) diff --git a/blogs/en/announcing-kubeblocks-v0-7-0.mdx b/blogs/en/announcing-kubeblocks-v0-7-0.mdx index b99cd9c..9827a68 100644 --- a/blogs/en/announcing-kubeblocks-v0-7-0.mdx +++ b/blogs/en/announcing-kubeblocks-v0-7-0.mdx @@ -27,7 +27,7 @@ To address this issue, we plan to decouple the cluster's lifecycle management fu ### Pika v3.5 -Pika, an open-source NoSQL database developed by Qihoo, supports the Redis protocol and offers a cost advantage for handling data volumes exceeding 100 GB. The transition from Redis to Pika is smooth, as Pika preserves the same operational and usage patterns, ensuring minimal disruption to existing workflows. As of now, KubeBlocks supports the deployment of the Pika v3.5 sharding cluster. +Pika, an open-source NoSQL database developed by Qihoo, supports the [Redis](/docs/preview/kubeblocks-for-redis) protocol and offers a cost advantage for handling data volumes exceeding 100 GB. The transition from Redis to Pika is smooth, as Pika preserves the same operational and usage patterns, ensuring minimal disruption to existing workflows. As of now, KubeBlocks supports the deployment of the Pika v3.5 sharding cluster. ## Overview of Integrated Engines @@ -66,3 +66,11 @@ The table below provides an overview of the integrated engines and their capabil | PolarDB-X | ✔️ | ✔️ | N/A | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ✔️ | | Zookeeper | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | N/A | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | | MariaDB | ✔️ | N/A | ✔️ | ✔️ | ✔️ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v0-8-0.mdx b/blogs/en/announcing-kubeblocks-v0-8-0.mdx index 2b6fe90..877c222 100644 --- a/blogs/en/announcing-kubeblocks-v0-8-0.mdx +++ b/blogs/en/announcing-kubeblocks-v0-8-0.mdx @@ -15,7 +15,7 @@ KubeBlocks v0.8.0 takes a big step forward in user experience by introducing com For example, popular meta-database components like ETCD and ZK, which are widely used in various database clusters, now can be directly referenced after component modularization. -We also made Vitess Proxy a standard component, so that developers do not need to repeat their work (heavy lifting) when defining the read-write separation topology of MySQL or PostgreSQL engines in various distributions. +We also made Vitess Proxy a standard component, so that developers do not need to repeat their work (heavy lifting) when defining the read-write separation topology of [MySQL](/docs/preview/kubeblocks-for-mysql) or [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) engines in various distributions. Further, the Add-on mechanism has also been significantly improved. The helm chart of the database engine has been split from the KubeBlocks repo. From then on, changes in the database engine or version have been unbound from the KubeBlocks release. @@ -62,11 +62,11 @@ Supports wal-g full backup and PITR. #### OpsRequest -Supports custom OpsRequest, enabling specific operational actions. For example, create and delete Kafka topics. +Supports custom OpsRequest, enabling specific operational actions. For example, create and delete [Kafka](/docs/preview/kubeblocks-for-kafka) topics. #### NodePort -Enables NodePort access for Redis. +Enables NodePort access for [Redis](/docs/preview/kubeblocks-for-redis). ### Compatibility @@ -101,4 +101,12 @@ Enhances addon sub-command. You can install the addon from the index repository. - 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. \ No newline at end of file +- 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. + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v0-9-0.mdx b/blogs/en/announcing-kubeblocks-v0-9-0.mdx index 1bcfcd9..eba3eea 100644 --- a/blogs/en/announcing-kubeblocks-v0-9-0.mdx +++ b/blogs/en/announcing-kubeblocks-v0-9-0.mdx @@ -13,7 +13,7 @@ We are thrilled to announce the release of KubeBlocks v0.9.0, which brings us on ## API Highlights -- In KubeBlocks v0.9, with the introduction of topology support in KubeBlocks, the cluster building experience has become much more flexible and intuitive, akin to assembling a cluster using building blocks. The ClusterDefinition API has added the `topologies` field, allowing developers to provide various deployment patterns with different topologies. Database users can choose a topology when creating a Cluster through the `topology` field. For instance, the Redis Addon offers three topologies: Standalone, Replication, and Proxy. The Standalone topology only includes one Component - RedisServer, the Replication topology includes both RedisServer and Sentinel Components, and the Proxy topology adds a third Component, such as Twemproxy. +- In KubeBlocks v0.9, with the introduction of topology support in KubeBlocks, the cluster building experience has become much more flexible and intuitive, akin to assembling a cluster using building blocks. The ClusterDefinition API has added the `topologies` field, allowing developers to provide various deployment patterns with different topologies. Database users can choose a topology when creating a Cluster through the `topology` field. For instance, the [Redis](/docs/preview/kubeblocks-for-redis) Addon offers three topologies: Standalone, Replication, and Proxy. The Standalone topology only includes one Component - RedisServer, the Replication topology includes both RedisServer and Sentinel Components, and the Proxy topology adds a third Component, such as Twemproxy. - KubeBlocks now supports managing horizontal scaling (Reshard) of distributed databases. You can represent a horizontal shard with a Component, and scale up or down this horizontal shard by adding or removing Components. This scaling capability will also be used in the distributed deployment of Redis and Pika. - KubeBlocks now uses InstanceSet instead of StatefulSet to manage Pods. InstanceSet supports taking a specified Pod offline and Pod in-place update, and also the primary and secondary databases can adopt different Pod specs in a database Replication architecture (StatefulSet doesn't support these features). - Developers can add more custom event handlers for Components! The ComponentDefinition API, introduced in v0.8, includes the `lifeCycleActions` field, allowing you to define various custom event handlers. Building on this, KubeBlocks v0.9 provides more handlers for custom addon implementation, including roleprobe (node role probing), memberLeave (node offline), preTerminate (Component offline), and postProvision (Component online). The expansion of event handlers enhances KubeBlocks' expression capabilities. For example, preTerminate and postProvision can be used to execute cross-shard data redistribution (Rebalance) in distributed databases or initiate registration to third-party HA managers like Sentinel and Orchestrator. @@ -24,7 +24,7 @@ We are thrilled to announce the release of KubeBlocks v0.9.0, which brings us on Redis Cluster is designed to provide horizontal write scalability and intelligent client high-availability strategies, in addition to its excellent failover capability. Redis Cluster distributes data across multiple Redis nodes, significantly enhancing system capacity, performance, and availability. -- KubeBlocks introduces MySQL Replication mode +- KubeBlocks introduces [MySQL](/docs/preview/kubeblocks-for-mysql) Replication mode Compared to MGR clusters, the MySQL Replication topology requires fewer resources (only two database replicas) and incurs less overhead for data replication. When there is no extreme demands for service availability and data reliability, the Replication topology is a more cost-effective choice. You can actively switch MySQL replica roles using `kbcli` or trigger a passive failover by deleting specified Kubernetes pods via `kubectl`. If there are no long transactions and large table DDLs, the failover generally can be completed within 30 seconds. @@ -64,7 +64,7 @@ We are thrilled to announce the release of KubeBlocks v0.9.0, which brings us on #### kbcli -- Supports PostgreSQL point-in-time recovery. +- Supports [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) point-in-time recovery. - `cluster` supports the `rebuild-instance` subcommand to rebuild instances. - `cluster create` subcommand supports `elasticsearch`. - Supports specifying the path prefix when creating a backup repository. @@ -144,3 +144,11 @@ KubeBlocks Release 0.9 still maintains the compatibility with API marked as depr ## Upgrade to v0.9 Refer to [Upgrade to KubeBlocks v0.9](https://kubeblocks.io/docs/release-0.9/user_docs/installation/upgrade/upgrade-kubeblocks-to-0.9). + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v0-9-1.mdx b/blogs/en/announcing-kubeblocks-v0-9-1.mdx index d006664..33c1b40 100644 --- a/blogs/en/announcing-kubeblocks-v0-9-1.mdx +++ b/blogs/en/announcing-kubeblocks-v0-9-1.mdx @@ -11,7 +11,7 @@ image: /img/blogs/thumbnails/blog-release-0.9.1.png We're thrilled to announce that KubeBlocks v0.9.1 now is released! -In this release, KubeBlocks further optimizes its APIs and Addons to bring you new features and better user experience. This release includes new features like stopping/starting a cluster by Cluster API, instance rebuild capability in OpsRequest, PITR and key-based recovery for Redis. We also fixed some bugs and introduced several improvements to enhance the overall functionality. +In this release, KubeBlocks further optimizes its APIs and Addons to bring you new features and better user experience. This release includes new features like stopping/starting a cluster by Cluster API, instance rebuild capability in OpsRequest, PITR and key-based recovery for [Redis](/docs/preview/kubeblocks-for-redis). We also fixed some bugs and introduced several improvements to enhance the overall functionality. Read the full release note and [upgrade to KubeBlocks v0.9.1](https://kubeblocks.io/docs/preview/user_docs/upgrade/upgrade-with-kbcli/upgrade-kubeblocks-to-0.9.1) to explore more features! @@ -39,7 +39,7 @@ Read the full release note and [upgrade to KubeBlocks v0.9.1](https://kubeblocks - New versions - MySQL and PostgreSQL Addons support more versions. For the latest versions of Addons, refer to the [Addon List](https://github.com/apecloud/kubeblocks-addons?tab=readme-ov-file#supported-add-ons). + [MySQL](/docs/preview/kubeblocks-for-mysql) and [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) Addons support more versions. For the latest versions of Addons, refer to the [Addon List](https://github.com/apecloud/kubeblocks-addons?tab=readme-ov-file#supported-add-ons). ## What's Changed @@ -94,3 +94,11 @@ Read the full release note and [upgrade to KubeBlocks v0.9.1](https://kubeblocks - Remove the Application Addon (#7866) The Application Addon has been removed from the codebase and is no longer installed by default. However, you can still install it manually if needed. + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v0-9-2.mdx b/blogs/en/announcing-kubeblocks-v0-9-2.mdx index fe13672..7f1c532 100644 --- a/blogs/en/announcing-kubeblocks-v0-9-2.mdx +++ b/blogs/en/announcing-kubeblocks-v0-9-2.mdx @@ -24,11 +24,11 @@ Read the full release note and [upgrade to KubeBlocks v0.9.2](https://kubeblocks ## Addons -### MySQL +### [MySQL](/docs/preview/kubeblocks-for-mysql) - Added Jemalloc support for improved memory management. ([#1158](https://github.com/apecloud/kubeblocks-addons/pull/1158)) -### Redis +### [Redis](/docs/preview/kubeblocks-for-redis) - Added NodePort announce mode support for Redis Sentinel. ([#1227](https://github.com/apecloud/kubeblocks-addons/pull/1227)) - Introduced support for fixed pod IPs, custom master names, and full FQDN domains.([#1222](https://github.com/apecloud/kubeblocks-addons/pull/1222)) @@ -39,15 +39,23 @@ Read the full release note and [upgrade to KubeBlocks v0.9.2](https://kubeblocks - Added support for member leave operations to enable scale-in scenarios. ([#1229](https://github.com/apecloud/kubeblocks-addons/pull/1229)) - Enhanced RabbitMQ configuration with config constraints and file-based logs. ([#1199](https://github.com/apecloud/kubeblocks-addons/pull/1199)) -### MongoDB +### [MongoDB](/docs/preview/kubeblocks-for-mongodb) - Added support for host networking. ([#1152](https://github.com/apecloud/kubeblocks-addons/pull/1152)) -### PostgreSQL +### [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) - Enhanced vanilla PostgreSQL integration and added support for PostgreSQL 15. ([#1092](https://github.com/apecloud/kubeblocks-addons/pull/1092)) - Added support for Supabase PostgreSQL. ([#1154](https://github.com/apecloud/kubeblocks-addons/pull/1154)) Xinference - Added support for Xinference v0.15.4. ([#1248](https://github.com/apecloud/kubeblocks-addons/pull/1248)) -You can view the [full changelog here](https://github.com/apecloud/kubeblocks/compare/v0.9.1...v0.9.2). \ No newline at end of file +You can view the [full changelog here](https://github.com/apecloud/kubeblocks/compare/v0.9.1...v0.9.2). + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v0-9-3.mdx b/blogs/en/announcing-kubeblocks-v0-9-3.mdx index 5d24733..4897f85 100644 --- a/blogs/en/announcing-kubeblocks-v0-9-3.mdx +++ b/blogs/en/announcing-kubeblocks-v0-9-3.mdx @@ -23,7 +23,7 @@ We are delighted to announce the release of KubeBlocks v0.9.3. This release incl ## KubeBlocks Addons -### MySQL +### [MySQL](/docs/preview/kubeblocks-for-mysql) - **Improvements:** - Supported configuring `lower_case_table_names` for MySQL ([#1335](https://github.com/apecloud/kubeblocks-addons/pull/1335)). @@ -31,14 +31,14 @@ We are delighted to announce the release of KubeBlocks v0.9.3. This release incl - **Fixes:** - Fixed an issue where the MySQL backup policy wasn't applied. ([#1310](https://github.com/apecloud/kubeblocks-addons/pull/1310)). -### PostgreSQL +### [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) - **Fixes:** - Fixed PITR (Point-in-Time Recovery) failures due to missing WAL log backups ([#1280](https://github.com/apecloud/kubeblocks-addons/pull/1280)). - Resolved PITR failures ([#1290](https://github.com/apecloud/kubeblocks-addons/pull/1290)). - Improved WAL log archiving. -### Redis +### [Redis](/docs/preview/kubeblocks-for-redis) - **Improvements:** - Updated Redis to address [CVE-2024-46981](https://access.redhat.com/security/cve/cve-2024-46981) ([#1405](https://github.com/apecloud/kubeblocks-addons/pull/1405)). @@ -47,13 +47,13 @@ We are delighted to announce the release of KubeBlocks v0.9.3. This release incl - **Fixes:** - Fixed FQDN issues when scaling out shards in Redis Cluster ([#1283](https://github.com/apecloud/kubeblocks-addons/pull/1283)). -### MongoDB +### [MongoDB](/docs/preview/kubeblocks-for-mongodb) - **Improvements:** - Added new MongoDB versions: v5.0.30/6.0.20/7.0.16/8.0.4 ([#1431](https://github.com/apecloud/kubeblocks-addons/pull/1431)). - Updated MongoDB cluster creation examples ([#1363](https://github.com/apecloud/kubeblocks-addons/pull/1363)). -### ClickHouse +### [ClickHouse](/docs/preview/kubeblocks-for-clickhouse) - **Improvements:** - Added ClickHouse reconfiguration examples ([#1401](https://github.com/apecloud/kubeblocks-addons/pull/1401)). @@ -84,3 +84,11 @@ Refer to [Upgrade to KubeBlocks v0.9.x](../upgrade/upgrade-to-v09-version). ## Full Changelog You can check the [full changelog](https://github.com/apecloud/kubeblocks/compare/v0.9.2...v0.9.3) for additional changes. + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v0-9-4.mdx b/blogs/en/announcing-kubeblocks-v0-9-4.mdx index 030ce49..2876c49 100644 --- a/blogs/en/announcing-kubeblocks-v0-9-4.mdx +++ b/blogs/en/announcing-kubeblocks-v0-9-4.mdx @@ -23,21 +23,21 @@ We are delighted to announce the release of KubeBlocks v0.9.4. This release incl ## KubeBlocks Addons -### MySQL +### [MySQL](/docs/preview/kubeblocks-for-mysql) * Update parameter scope for `innodb_redo_log_capacity` and `secure_file_priv` [(#1510)](https://github.com/apecloud/kubeblocks-addons/pull/1510) [(#1585)](https://github.com/apecloud/kubeblocks-addons/pull/1585) -### PostgreSQL +### [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) * Fix missing `backupPolicy` for PostgreSQL 15 & 16 [(#1546)](https://github.com/apecloud/kubeblocks-addons/pull/1546) -### Redis +### [Redis](/docs/preview/kubeblocks-for-redis) * Improve Redis cluster on stop-start [(#1554)](https://github.com/apecloud/kubeblocks-addons/pull/1554) * Improve member leave logic (do not rely on announce address) [(#1548)](https://github.com/apecloud/kubeblocks-addons/pull/1548) * Refine Redis host network variables [(#1603)](https://github.com/apecloud/kubeblocks-addons/pull/1603) -### MongoDB +### [MongoDB](/docs/preview/kubeblocks-for-mongodb) * Add support for MongoDB exporter [(#1721)](https://github.com/apecloud/kubeblocks-addons/pull/1721) @@ -63,7 +63,7 @@ We are delighted to announce the release of KubeBlocks v0.9.4. This release incl * Support environment variable when creating VictoriaMetrics clusters [(#1622)](https://github.com/apecloud/kubeblocks-addons/pull/1622) -### ClickHouse +### [ClickHouse](/docs/preview/kubeblocks-for-clickhouse) * Persist log files for ClickHouse and Keeper [(#1560)](https://github.com/apecloud/kubeblocks-addons/pull/1560) @@ -73,4 +73,12 @@ Refer to [Upgrade to KubeBlocks v0.9.x](https://kubeblocks.io/docs/preview/user_ ## Full Changelog -You can check the [full changelog](https://github.com/apecloud/kubeblocks/compare/v0.9.3...v0.9.4) for additional changes. \ No newline at end of file +You can check the [full changelog](https://github.com/apecloud/kubeblocks/compare/v0.9.3...v0.9.4) for additional changes. + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v0-9-5.mdx b/blogs/en/announcing-kubeblocks-v0-9-5.mdx index 2d56ed4..079be8d 100644 --- a/blogs/en/announcing-kubeblocks-v0-9-5.mdx +++ b/blogs/en/announcing-kubeblocks-v0-9-5.mdx @@ -23,28 +23,28 @@ We are delighted to announce the release of KubeBlocks v0.9.5. This release incl ## KubeBlocks Addons -### MySQL Variants (MySQL, GreatSQL) +### [MySQL](/docs/preview/kubeblocks-for-mysql) Variants (MySQL, GreatSQL) - Support greatsql. ([#1793](https://github.com/apecloud/kubeblocks-addons/pull/1793)) - Support mysql audit log config. ([#1890](https://github.com/apecloud/kubeblocks-addons/pull/1890)) - Support greatsql auditlog config. ([#1893](https://github.com/apecloud/kubeblocks-addons/pull/1893)) -### PostgreSQL +### [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) - Refactor PostgreSQL addon and support PostgreSQL 16 and 17. ([#1734](https://github.com/apecloud/kubeblocks-addons/pull/1734)) - Support using etcd as DCS for PostgreSQL. ([#1864](https://github.com/apecloud/kubeblocks-addons/pull/1864)) -### Redis +### [Redis](/docs/preview/kubeblocks-for-redis) - Support redis 7.2.10 and redis 8 ([#1812](https://github.com/apecloud/kubeblocks-addons/pull/1812)) - Fix Redis slave instance memory leak when loading redisgears module. - Change redis maxmemory-policy to volatile-lru and maxmemory = 0.8 * limit_memory. -### MongoDB +### [MongoDB](/docs/preview/kubeblocks-for-mongodb) - Support mongodb sharding. ([#1701](https://github.com/apecloud/kubeblocks-addons/pull/1701)) ### Elasticsearch - Optimize backup. ([#1853](https://github.com/apecloud/kubeblocks-addons/pull/1853)) - Support new version 8.15.5. ([#1929](https://github.com/apecloud/kubeblocks-addons/pull/1929)) -### ClickHouse +### [ClickHouse](/docs/preview/kubeblocks-for-clickhouse) - Clickhouse support backup and restore. ([#1800](https://github.com/apecloud/kubeblocks-addons/pull/1800)) - Update metrics. ([#1916](https://github.com/apecloud/kubeblocks-addons/pull/1916)) @@ -65,4 +65,12 @@ Refer to [Upgrade to KubeBlocks v0.9.x](https://kubeblocks.io/docs/preview/user_ ## Full Changelog -You can check the [full changelog](https://github.com/apecloud/kubeblocks/compare/v0.9.4...v0.9.5) for additional changes. \ No newline at end of file +You can check the [full changelog](https://github.com/apecloud/kubeblocks/compare/v0.9.4...v0.9.5) for additional changes. + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v1-0-0.mdx b/blogs/en/announcing-kubeblocks-v1-0-0.mdx index 9c68f2a..1380404 100644 --- a/blogs/en/announcing-kubeblocks-v1-0-0.mdx +++ b/blogs/en/announcing-kubeblocks-v1-0-0.mdx @@ -43,10 +43,10 @@ The following CRDs are now **`v1` and considered stable**, with long-term suppor ### KubeBlocks Addon Highlights -* **MySQL Enhancements**: Adds TLS, group replication with ProxySQL, and PITR using WAL-G—boosting security and recovery -* **MongoDB PITR & Versioning**: Introduces Point-in-Time Recovery and new version support for MongoDB -* **Kafka Improvements**: Supports external ZooKeeper, custom Prometheus metrics, and multi-network access for better flexibility and observability -* **Redis Enhancements**: Adds cluster switchover, instance rebuild, and external config support to improve operational robustness +* **[MySQL](/docs/preview/kubeblocks-for-mysql) Enhancements**: Adds TLS, group replication with ProxySQL, and PITR using WAL-G—boosting security and recovery +* **[MongoDB](/docs/preview/kubeblocks-for-mongodb) PITR & Versioning**: Introduces Point-in-Time Recovery and new version support for MongoDB +* **[Kafka](/docs/preview/kubeblocks-for-kafka) Improvements**: Supports external ZooKeeper, custom Prometheus metrics, and multi-network access for better flexibility and observability +* **[Redis](/docs/preview/kubeblocks-for-redis) Enhancements**: Adds cluster switchover, instance rebuild, and external config support to improve operational robustness --- @@ -106,7 +106,7 @@ The following CRDs are now **`v1` and considered stable**, with long-term suppor * **New Versions**: Adds support for RabbitMQ versions 4.0.9 [#1596](https://github.com/apecloud/kubeblocks-addons/pull/1596) -#### ClickHouse +#### [ClickHouse](/docs/preview/kubeblocks-for-clickhouse) * **22.9.4 Support**: Adds compatibility with ClickHouse 22.9.4 [#1376](https://github.com/apecloud/kubeblocks-addons/pull/1376) @@ -186,4 +186,12 @@ Special thanks to Kuaishou, China Mobile Cloud, Vipshop, Tencent, and 360 for th We’re also deeply grateful to our community contributors — your code contributions, issue reports, discussions, and reviews have been instrumental in driving the project forward with quality and innovation. -With 1.0.0, we’ve reached a major milestone in building a robust, cloud-native database platform. We look forward to continuing this journey with all of you — growing the ecosystem, tackling new challenges, and pushing the boundaries of what’s possible in data infrastructure. \ No newline at end of file +With 1.0.0, we’ve reached a major milestone in building a robust, cloud-native database platform. We look forward to continuing this journey with all of you — growing the ecosystem, tackling new challenges, and pushing the boundaries of what’s possible in data infrastructure. + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v1-0-1.mdx b/blogs/en/announcing-kubeblocks-v1-0-1.mdx index 50098ea..8fb63a1 100644 --- a/blogs/en/announcing-kubeblocks-v1-0-1.mdx +++ b/blogs/en/announcing-kubeblocks-v1-0-1.mdx @@ -27,12 +27,12 @@ We are delighted to announce the release of KubeBlocks v1.0.1. This release incl ## KubeBlocks Addons -### PostgreSQL +### [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) - Improve PostgreSQL dcs mode ([#1874](https://github.com/apecloud/kubeblocks-addons/pull/1874)) - Support synchronous mode ([#1941](https://github.com/apecloud/kubeblocks-addons/pull/1941)) - Update patroni scope value and dcs scope ([#2005](https://github.com/apecloud/kubeblocks-addons/pull/2005),[#1997](https://github.com/apecloud/kubeblocks-addons/pull/1997)) -### Redis +### [Redis](/docs/preview/kubeblocks-for-redis) - Support new Redis versions 8.2,8.0.3, 7.2.10 and 7.4.5/([#1968](https://github.com/apecloud/kubeblocks-addons/pull/1968), [#1785](https://github.com/apecloud/kubeblocks-addons/pull/1785), [#1710](https://github.com/apecloud/kubeblocks-addons/pull/1710)) - Fixed Redis memory leak when loading redisgears module ([#1855](https://github.com/apecloud/kubeblocks-addons/pull/1855)) - Support reconfiguration of `client-output-buffer-limit` ([#1973](https://github.com/apecloud/kubeblocks-addons/pull/1973)) @@ -59,4 +59,12 @@ We are delighted to announce the release of KubeBlocks v1.0.1. This release incl ## Full Changelog -You can check the [full changelog](https://github.com/apecloud/kubeblocks/compare/v1.0.0...v1.0.1) for additional changes. \ No newline at end of file +You can check the [full changelog](https://github.com/apecloud/kubeblocks/compare/v1.0.0...v1.0.1) for additional changes. + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/announcing-kubeblocks-v1-0-2.mdx b/blogs/en/announcing-kubeblocks-v1-0-2.mdx index ad925fa..d0ebe6c 100644 --- a/blogs/en/announcing-kubeblocks-v1-0-2.mdx +++ b/blogs/en/announcing-kubeblocks-v1-0-2.mdx @@ -30,18 +30,18 @@ We are delighted to announce the release of KubeBlocks v1.0.2. This release incl ## KubeBlocks Addons -### MySQL +### [MySQL](/docs/preview/kubeblocks-for-mysql) - Support MySQL minor versions 8.0.41, 8.0.44 ([#2295](https://github.com/apecloud/kubeblocks-addons/pull/2295)) - Fix MySQL `log_output` parameter constraint ([#2408](https://github.com/apecloud/kubeblocks-addons/pull/2408)) - Disable jemalloc for ARM ([#2381](https://github.com/apecloud/kubeblocks-addons/pull/2381))) -### PostgreSQL +### [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) - Support PostgreSQL 18.1 ([#2409](https://github.com/apecloud/kubeblocks-addons/pull/2409)) - Improve PostgreSQL config constraint comment ([#2376](https://github.com/apecloud/kubeblocks-addons/pull/2376)) - Unset `archive_timeout` immutable for PostgreSQL ([#2380](https://github.com/apecloud/kubeblocks-addons/pull/2380)) - Set `wal_keep_size` by data disk size ([#2372](https://github.com/apecloud/kubeblocks-addons/pull/2372)) -### Redis +### [Redis](/docs/preview/kubeblocks-for-redis) - Support 7.2.11/7.4.6/8.0.4/8.2.2 for redis CVE-2025-49844 issue ([#2123](https://github.com/apecloud/kubeblocks-addons/pull/2123)) - Support more minor versions of Redis 7.2.12/7.4.7/8.0.5/8.2.3/8.4.0 ([#2347](https://github.com/apecloud/kubeblocks-addons/pull/2347)) - Improve Redis `maxmemory` parameter ([#2392](https://github.com/apecloud/kubeblocks-addons/pull/2392)) @@ -51,12 +51,12 @@ We are delighted to announce the release of KubeBlocks v1.0.2. This release incl - Fix redis cluster restore failed ([#2404](https://github.com/apecloud/kubeblocks-addons/pull/2404)) - Fix redis pitr no time range ([#2204](https://github.com/apecloud/kubeblocks-addons/pull/2204)) -### MongoDB +### [MongoDB](/docs/preview/kubeblocks-for-mongodb) - Support MongoDB minor versions 8.0.17/7.0.28/6.0.27 ([#2382](https://github.com/apecloud/kubeblocks-addons/pull/2382)) - Support MongoDB audit log ([#2111](https://github.com/apecloud/kubeblocks-addons/pull/2111)) - Fix MongoDB backup hang ([#2387](https://github.com/apecloud/kubeblocks-addons/pull/2387)) -### ClickHouse +### [ClickHouse](/docs/preview/kubeblocks-for-clickhouse) - Improve ClickHouse `memberjoin` ([#2431](https://github.com/apecloud/kubeblocks-addons/pull/2431)) - Improve ClickHouse sharding restore ([#2357](https://github.com/apecloud/kubeblocks-addons/pull/2357)) - Fix ClickHouse restore failed when specified the init cluster name ([#2429](https://github.com/apecloud/kubeblocks-addons/pull/2429)) @@ -68,7 +68,7 @@ We are delighted to announce the release of KubeBlocks v1.0.2. This release incl - Fix single node backup failed ([#2290](https://github.com/apecloud/kubeblocks-addons/pull/2290)) - Fix ES render tpl compatibility ([#2411](https://github.com/apecloud/kubeblocks-addons/pull/2411)) -### Kafka +### [Kafka](/docs/preview/kubeblocks-for-kafka) - Support Kafka 3.7/3.8/3.9 ([#2174](https://github.com/apecloud/kubeblocks-addons/pull/2174)) - Support custom SASL ([#2259](https://github.com/apecloud/kubeblocks-addons/pull/2259)) - Support Kafka backup topics ([#2260](https://github.com/apecloud/kubeblocks-addons/pull/2260)) @@ -154,3 +154,11 @@ Refer to [Upgrade to KubeBlocks v1.0.x](https://kubeblocks.io/docs/preview/user_ ## Full Changelog You can check the [full changelog](https://github.com/apecloud/kubeblocks/compare/v1.0.1...v1.0.2) for additional changes and [kubeblocks-addons](https://github.com/apecloud/kubeblocks-addons/compare/v1.0.1...v1.0.2) for addons changes. + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for Kafka — Operations Guide](/docs/preview/kubeblocks-for-kafka) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/community-monthly-report-for-april-2024.mdx b/blogs/en/community-monthly-report-for-april-2024.mdx index 5964459..d587564 100644 --- a/blogs/en/community-monthly-report-for-april-2024.mdx +++ b/blogs/en/community-monthly-report-for-april-2024.mdx @@ -50,7 +50,7 @@ Nice to have you here in the KubeBlocks family. Chiwency managed to merge a PR l KubeBlocks & WeScale have participated in OSPP 2024. Join us in exploring solutions to challenging problems. And guess what? There are generous rewards, gifts, and certificates waiting for you! Click the links below to view the details and contact your mentor. - Basic: [KubeBlocks supports etcd Add-on](https://summer-ospp.ac.cn/org/prodetail/248330234?lang=en&list=pro) -- Advanced: [KubeBlocks supports Redis PITR (Point-in-Time Recovery) and recovery of specific keys](https://summer-ospp.ac.cn/org/prodetail/248330238?lang=en&list=pro) +- Advanced: [KubeBlocks supports [Redis](/docs/preview/kubeblocks-for-redis) PITR (Point-in-Time Recovery) and recovery of specific keys](https://summer-ospp.ac.cn/org/prodetail/248330238?lang=en&list=pro) - Advanced: [Implementing Consistency Optimization with Table-Level Read-After-Write Strategy Based on Wescale](https://summer-ospp.ac.cn/org/prodetail/245d80005?lang=en&list=pro) ## Good First Issues @@ -69,4 +69,11 @@ Related links: Feel free to join the GitHub Discussion or the [KubeBlocks Slack group](https://join.slack.com/t/kubeblocks/shared_invite/zt-29tx52d8n-vli24S6gtD5ODJlNUqLqbQ)! -![2024-04-overview](/img/blogs/2024-04-overview.jpg) \ No newline at end of file +![2024-04-overview](/img/blogs/2024-04-overview.jpg) + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/community-monthly-report-for-february-2024.mdx b/blogs/en/community-monthly-report-for-february-2024.mdx index 7db2d42..565b53d 100644 --- a/blogs/en/community-monthly-report-for-february-2024.mdx +++ b/blogs/en/community-monthly-report-for-february-2024.mdx @@ -18,11 +18,11 @@ In the past month, the community has merged 76 PRs and resolved 57 issues. A tot ## Highlights - Supported ShardingSpec API to define database clusters with sharding topology (to be released in v0.8.2). -- Supported creating and deleting official Redis Clusters based on KubeBlocks Sharding API (to be released in v0.8.2). +- Supported creating and deleting official [Redis](/docs/preview/kubeblocks-for-redis) Clusters based on KubeBlocks Sharding API (to be released in v0.8.2). - Supported Camellia Redis Proxy for one-click deployment, configuration management, horizontal scaling, restarts, and other operations (to be released in v0.8.2). - Supported declaring host network capabilities (#6705). - Supported specifying namespaces that operators should manage (#6641). -- MongoDB supported connections from outside of K8s using host network (#6689). +- [MongoDB](/docs/preview/kubeblocks-for-mongodb) supported connections from outside of K8s using host network (#6689). - Lorry supported action commands(#6474). - Compatible with CronJob v1beta1 to resolve backup failures when using K8s v1.20 (#6687). - 【External Contribution】Added version validation for Addon spec. Addon CRD supported provider and version fields, and the controller could add provider information to labels for quick querying (#6603). @@ -33,7 +33,7 @@ In the past month, the community has merged 76 PRs and resolved 57 issues. A tot - Adjusted the OceanBase switchover feature to accommodate Oracle tenant mode (#6710). - Resolved backup and restore failures when using the host network (#6715). - Fixed the issue of parameter reconfiguration failures(#6664 #6665). -- Fixed the issue of inoperative dynamic parameters. In Patroni PostgreSQL, if dynamic parameters and static parameters were modified simultaneously, the dynamic parameters did not take effect (#6648). +- Fixed the issue of inoperative dynamic parameters. In Patroni [PostgreSQL](/docs/preview/kubeblocks-for-postgresql), if dynamic parameters and static parameters were modified simultaneously, the dynamic parameters did not take effect (#6648). - Removed duplicate ports generated when exposing SVC (#6631). - Fixed bugs related to ServiceAccount. If RestoreCR specifies a ServiceAccount, the backup and restore pods will use the specified SA (#6605). @@ -56,4 +56,11 @@ Related links: Feel free to join the GitHub Discussion or the [KubeBlocks Slack group](https://join.slack.com/t/kubeblocks/shared_invite/zt-29tx52d8n-vli24S6gtD5ODJlNUqLqbQ)! -![2024-02-overview](/img/blogs/2024-02-overview.png) \ No newline at end of file +![2024-02-overview](/img/blogs/2024-02-overview.png) + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/community-monthly-report-for-january-2024.mdx b/blogs/en/community-monthly-report-for-january-2024.mdx index 9f71d60..ede6b7c 100644 --- a/blogs/en/community-monthly-report-for-january-2024.mdx +++ b/blogs/en/community-monthly-report-for-january-2024.mdx @@ -28,7 +28,7 @@ image: /img/blogs/thumbnails/blog-2024-01-monthly-report.png - KubeBlocks has supported more addons, such as TiDB, Xinference, openGauss, InfluxDB, OceanBase (primary/standby), and Flink. Check the [official documentation](https://kubeblocks.io/docs/release-0.8/user_docs/overview/supported-addons) for the supported capabilities of each engine. - KubeBlocks Client SDK is now available (check the [repo](https://github.com/apecloud/kubeblocks-client)) and currently supports Java, Python, and Rust. -- Switchover is now supported for MySQL Replication clusters, and it allows `kbcli promote` commands. +- Switchover is now supported for [MySQL](/docs/preview/kubeblocks-for-mysql) Replication clusters, and it allows `kbcli promote` commands. ## New Contributors @@ -57,4 +57,11 @@ On January 10th, the community announced the recruitment for the second round of ![2024-01-overview](/img/blogs/2024-01-overview.png) -By the way, the traditional Chinese Spring Festival is around the corner 🎉. May you have a prosperous New Year! \ No newline at end of file +By the way, the traditional Chinese Spring Festival is around the corner 🎉. May you have a prosperous New Year! + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/community-monthly-report-for-march-2024.mdx b/blogs/en/community-monthly-report-for-march-2024.mdx index 69de701..223b3bf 100644 --- a/blogs/en/community-monthly-report-for-march-2024.mdx +++ b/blogs/en/community-monthly-report-for-march-2024.mdx @@ -11,7 +11,7 @@ image: /img/blogs/thumbnails/blog-2024-03-monthly-report.png ## Overview -In March, KubeBlocks officially released v0.8.2. This update notably included the support for Redis Cluster, camellia-redis-proxy, and compatibility with Pulsar v3.0.2. Furthermore, the development team has been actively working on the upcoming v0.9.0. +In March, KubeBlocks officially released v0.8.2. This update notably included the support for [Redis](/docs/preview/kubeblocks-for-redis) Cluster, camellia-redis-proxy, and compatibility with Pulsar v3.0.2. Furthermore, the development team has been actively working on the upcoming v0.9.0. Over the past month, the community has merged 91 PRs and resolved 92 issues. A total of 19 community members participated in these contributions, including 6 new contributors. @@ -22,7 +22,7 @@ So far, a total of 1607 GitHub users have starred KubeBlocks. We do appreciate y - Supported Redis Cluster. - Supported Sharding topology for Cluster APIs, so that users could define shard numbers and component specs with ShardingSpec. - Supported camellia-redis-proxy. It is currently running on K8s v1.14, and allows configuring external Redis instances, including those outside the K8s cluster. -- Supported high-availability access from an external K8s cluster for MongoDB Replicaset addresses. +- Supported high-availability access from an external K8s cluster for [MongoDB](/docs/preview/kubeblocks-for-mongodb) Replicaset addresses. - Supported Pulsar v3.0.2. - Supported exposing nodeport addresses for each Pulsar broker. - Supported IPv4/IPv6 dual stack for StarRocks. Both private and public addresses could use IPv4 and IPv6. However, IPv6 support in the StarRocks kernel was still required. @@ -56,4 +56,11 @@ Related links: Feel free to join the GitHub Discussion or the [KubeBlocks Slack group](https://join.slack.com/t/kubeblocks/shared_invite/zt-29tx52d8n-vli24S6gtD5ODJlNUqLqbQ)! -![2024-03-overview](/img/blogs/2024-03-overview.jpg) \ No newline at end of file +![2024-03-overview](/img/blogs/2024-03-overview.jpg) + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/community-monthly-report-for-may-2024.mdx b/blogs/en/community-monthly-report-for-may-2024.mdx index ad7b2b0..8638805 100644 --- a/blogs/en/community-monthly-report-for-may-2024.mdx +++ b/blogs/en/community-monthly-report-for-may-2024.mdx @@ -22,7 +22,7 @@ Over the past month, the community merged 170 PRs, and resolved 133 issues, with ## Bug Fixes -- [#7475](https://github.com/apecloud/kubeblocks/pull/7475) Fixed the crash issue after executing a switchover for MongoDB. +- [#7475](https://github.com/apecloud/kubeblocks/pull/7475) Fixed the crash issue after executing a switchover for [MongoDB](/docs/preview/kubeblocks-for-mongodb). - [#7447](https://github.com/apecloud/kubeblocks/pull/7447) Adapted rolecheck to accommodate cluster initialization for some database engines. - [#7365](https://github.com/apecloud/kubeblocks/pull/7365) Supported PVC to create idempotent. - [#7352](https://github.com/apecloud/kubeblocks/pull/7352) Added labels to distinguish KubeBlocks from dataprotection. @@ -55,4 +55,11 @@ Related links: Feel free to join the GitHub Discussion or the [KubeBlocks Slack group](https://join.slack.com/t/kubeblocks/shared_invite/zt-29tx52d8n-vli24S6gtD5ODJlNUqLqbQ)! -![2024-05-overview](/img/blogs/2024-05-overview.png) \ No newline at end of file +![2024-05-overview](/img/blogs/2024-05-overview.png) + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/deploy-kubeblocks-on-openshift.mdx b/blogs/en/deploy-kubeblocks-on-openshift.mdx index 0b75a15..e556805 100644 --- a/blogs/en/deploy-kubeblocks-on-openshift.mdx +++ b/blogs/en/deploy-kubeblocks-on-openshift.mdx @@ -22,7 +22,7 @@ Red Hat OpenShift is an enterprise-grade container platform built on Kubernetes, However, even on a mature platform like OpenShift, database management remains a complex task, requiring specialized tools and solutions to simplify operational processes. -KubeBlocks is a cloud-native data infrastructure designed specifically for Kubernetes environments, providing a complete solution for enterprises to manage database workloads in cloud-native environments. Through a unified control plane, KubeBlocks can easily manage the full lifecycle of 30+ database engines such as MySQL, PostgreSQL, MongoDB, and Redis. +KubeBlocks is a cloud-native data infrastructure designed specifically for Kubernetes environments, providing a complete solution for enterprises to manage database workloads in cloud-native environments. Through a unified control plane, KubeBlocks can easily manage the full lifecycle of 30+ database engines such as [MySQL](/docs/preview/kubeblocks-for-mysql), [PostgreSQL](/docs/preview/kubeblocks-for-postgresql), [MongoDB](/docs/preview/kubeblocks-for-mongodb), and [Redis](/docs/preview/kubeblocks-for-redis). Core advantages of KubeBlocks: @@ -464,4 +464,12 @@ For enterprise users with higher requirements, we also provide [Enterprise KubeB * Commercial database support: Includes enterprise-grade commercial database engines such as Oracle, SQL Server, and more version choices. * Enterprise-grade disaster recovery and observability: Provides cross-region disaster recovery capabilities, comprehensive monitoring metrics, log management, and alert services. -If you are interested in Enterprise KubeBlocks or wish to deploy KubeBlocks in a production environment, please visit our [official website](https://apecloud.cn/products/kubeblocks-enterprise) for more information or contact us for a trial version. \ No newline at end of file +If you are interested in Enterprise KubeBlocks or wish to deploy KubeBlocks in a production environment, please visit our [official website](https://apecloud.cn/products/kubeblocks-enterprise) for more information or contact us for a trial version. + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for MongoDB — Operations Guide](/docs/preview/kubeblocks-for-mongodb) +- [How to Manage Database Clusters Without a Dedicated Operator](/blog/how-to-manage-database-clusters-without-a-dedicated-operator) diff --git a/blogs/en/how-to-fix-pod-stuck-in-terminating-status.mdx b/blogs/en/how-to-fix-pod-stuck-in-terminating-status.mdx index 4ed55f8..a796d72 100644 --- a/blogs/en/how-to-fix-pod-stuck-in-terminating-status.mdx +++ b/blogs/en/how-to-fix-pod-stuck-in-terminating-status.mdx @@ -262,4 +262,11 @@ Some key takeaways: 1. During Pod termination, Kubernetes waits indefinitely for all volume resources to be released. 2. The kubelet handles Pods by assigning each Pod a goroutine responsible for managing its entire lifecycle, from Creating, Running, Terminating, and Terminated. 3. The kubelet’s module for handling volume-related tasks is called the volume manager, which assigns a goroutine to each volume to handle attaching, mounting, unmounting, and detaching. -4. The Hostpath CSI Driver is definitely not suitable for production environments. \ No newline at end of file +4. The Hostpath CSI Driver is definitely not suitable for production environments. + +## Related + +- [InstanceSet: A New Approach to Stateful Workload Management in KubeBlocks](/blog/instanceset-introduction) +- [How to Take Specified Instances Offline?](/blog/take-specified-instances-offline) +- [Gaining Granular Pod Control in KubeBlocks with Instance Templates](/blog/configure-instance-template) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/instance-template.mdx b/blogs/en/instance-template.mdx index 543b625..27dbe1b 100644 --- a/blogs/en/instance-template.mdx +++ b/blogs/en/instance-template.mdx @@ -245,3 +245,10 @@ The `VolumeMounts` field in the instance template overrides the same field in th ### VolumeClaimTemplates The `VolumeClaimTemplates` field in the instance template overrides the same field generated by `ClusterComponentVolumeClaimTemplates` in the Component. If the `PersistentVolumeClaim Name` is the same, the `PersistentVolumeClaimSpec` values from the instance template will be applied; otherwise, it will be added as a new `PersistentVolumeClaim`. + +## Related + +- [InstanceSet: A New Approach to Stateful Workload Management in KubeBlocks](/blog/instanceset-introduction) +- [In-Place Updates in KubeBlocks](/blog/in-place-updates) +- [How to Take Specified Instances Offline?](/blog/take-specified-instances-offline) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/interview-china-mobile-cloud-dingshun.mdx b/blogs/en/interview-china-mobile-cloud-dingshun.mdx index 41395e2..302c2eb 100644 --- a/blogs/en/interview-china-mobile-cloud-dingshun.mdx +++ b/blogs/en/interview-china-mobile-cloud-dingshun.mdx @@ -120,4 +120,11 @@ It can help you **significantly shorten the development cycle, reduce operationa ## **Conclusion:** -Thank you, Ding Shun, for the excellent sharing! China Mobile Cloud's experience in successfully building the He3DB DBaaS platform using KubeBlocks fully demonstrates KubeBlocks' powerful capabilities and immense potential in the cloud-native database management domain. At the same time, the challenges and suggestions raised by Ding Shun also point the way for future optimization in the KubeBlocks community. The KubeBlocks community will continue to listen to user feedback, constantly refine the product, and strive to provide developers with an easier-to-use, more powerful, and more mature cloud-native database management solution. We look forward to working with more pioneers like Ding Shun to jointly advance the development of the cloud-native database ecosystem! \ No newline at end of file +Thank you, Ding Shun, for the excellent sharing! China Mobile Cloud's experience in successfully building the He3DB DBaaS platform using KubeBlocks fully demonstrates KubeBlocks' powerful capabilities and immense potential in the cloud-native database management domain. At the same time, the challenges and suggestions raised by Ding Shun also point the way for future optimization in the KubeBlocks community. The KubeBlocks community will continue to listen to user feedback, constantly refine the product, and strive to provide developers with an easier-to-use, more powerful, and more mature cloud-native database management solution. We look forward to working with more pioneers like Ding Shun to jointly advance the development of the cloud-native database ecosystem! + +## Related + +- [Managing Over 6,000 Self-Hosted Databases Without a DBA](/blog/manage-6k-db-instance-with-kubeblocks) +- [Run Databases on K8s: Insights from Leading Chinese Internet Companies](/blog/run-databases-on-k8s-insights-from-leading-chinese-internet-companies) +- [Run Redis on K8s: Kuaishou's Solution with KubeBlocks](/blog/run-redis-on-k8s-kuaishou-solution-with-kubeblocks) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/kubeblocks-for-oracles.mdx b/blogs/en/kubeblocks-for-oracles.mdx index 60bb526..a0fe9e6 100644 --- a/blogs/en/kubeblocks-for-oracles.mdx +++ b/blogs/en/kubeblocks-for-oracles.mdx @@ -307,4 +307,11 @@ Taking the full backup implemented in Oracle Addon as an example, an ActionSet n Running Oracle clusters stably and efficiently in Kubernetes environments is not simple, but KubeBlocks provides an insightful and effective solution. This article detailed the specifics of supporting Oracle Addon based on the KubeBlocks Operator and introduced its supported features and advantages. Currently, KubeBlocks for Oracle has been launched in [KubeBlocks Enterprise Edition](https://www.apecloud.cn/products/kubeblocks-enterprise). Interested readers are welcome to apply for a trial. -We will continue to optimize and iterate KubeBlocks for Oracle to support more features and improve stability, while also adding support for more Oracle versions, making KubeBlocks for Oracle the best choice for more enterprise users. \ No newline at end of file +We will continue to optimize and iterate KubeBlocks for Oracle to support more features and improve stability, while also adding support for more Oracle versions, making KubeBlocks for Oracle the best choice for more enterprise users. + +## Related + +- [KubeBlocks x MSSQL: Operator-Based Always On AG Revealed](/blog/kubeblocks-x-mssql-operator-based-always-on-ag-revealed) +- [KubeBlocks for MSSQL High Availability Implementation](/blog/kubeblocks-for-mssql-high-availability-implementation) +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks Enterprise](https://kubeblocks.com/products/kubeblocks-enterprise) diff --git a/blogs/en/kubeblocks-on-kata.mdx b/blogs/en/kubeblocks-on-kata.mdx index 3a77b88..09b6dca 100644 --- a/blogs/en/kubeblocks-on-kata.mdx +++ b/blogs/en/kubeblocks-on-kata.mdx @@ -284,4 +284,10 @@ root 19703 13.1 3.8 3436120 591872 ? Sl 09:52 1:31 \_ /opt/kata With KubeBlocks, we can easily run data on Kata Containers. However, to better support Kata Containers, KubeBlocks still needs to natively support the Kubernetes runtimeClass mechanism, in order to support more runtime environments. -Furthermore, we can also feel that due to its good compatibility with CRI, Kata Containers can provide a good user experience while ensuring security. \ No newline at end of file +Furthermore, we can also feel that due to its good compatibility with CRI, Kata Containers can provide a good user experience while ensuring security. + +## Related + +- [Does Containerization Affect the Performance of Databases?](/blog/does-containerization-affect-the-performance-of-databases) +- [Is Kubernetes a Database?](/blog/is-k8s-a-database) +- [KubeBlocks User Documentation](/docs/preview/user_docs) diff --git a/blogs/en/mangage-6k-db-instance-with-kubeblocks.mdx b/blogs/en/mangage-6k-db-instance-with-kubeblocks.mdx index 1279f93..aad9580 100644 --- a/blogs/en/mangage-6k-db-instance-with-kubeblocks.mdx +++ b/blogs/en/mangage-6k-db-instance-with-kubeblocks.mdx @@ -21,7 +21,7 @@ Let’s start with a question: Can a single engineer, without being a profession In today’s era of cloud computing and large-scale distributed systems, databases remain the cornerstone of many applications. As their scale grows, so does the complexity of managing databases. Therefore, when faced with managing thousands of database instances alone, most would say, "That's impossible!" -However, what seems impossible has already been made a reality inside Sealos. Sealos provides its developer users with Kubernetes-based PaaS services, along with essential DBaaS offerings, including **MySQL**, **PostgreSQL**, **Redis**, **MongoDB**, **Kafka**, and **Milvus**, managing **over 6,000 database instances across four regions**. +However, what seems impossible has already been made a reality inside Sealos. Sealos provides its developer users with Kubernetes-based PaaS services, along with essential DBaaS offerings, including **[MySQL](/docs/preview/kubeblocks-for-mysql)**, **[PostgreSQL](/docs/preview/kubeblocks-for-postgresql)**, **[Redis](/docs/preview/kubeblocks-for-redis)**, **[MongoDB](/docs/preview/kubeblocks-for-mongodb)**, **[Kafka](/docs/preview/kubeblocks-for-kafka)**, and **[Milvus](/docs/preview/kubeblocks-for-milvus)**, managing **over 6,000 database instances across four regions**. In this blog, I'll share how I, a K8s engineer without DBA background, successfully manage such a massive number of databases using KubeBlocks in Sealos, transforming what seemed impossible into an everyday operation. @@ -177,3 +177,11 @@ Migration Workflow: ## Conclusion KubeBlocks has transformed database management into a streamlined, fully automatic process. It reduces time and costs while significantly simplifying operations. Whether you're a developer, platform engineer, or system administrator, it enables effective management of large-scale database clusters with ease and efficiency. + +## Related + +- [Run Databases on K8s: Insights from Leading Chinese Internet Companies](/blog/run-databases-on-k8s-insights-from-leading-chinese-internet-companies) +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [KubeBlocks for MongoDB — Operations Guide](/docs/preview/kubeblocks-for-mongodb) diff --git a/blogs/en/moodle-in-kubeblocks-windows.mdx b/blogs/en/moodle-in-kubeblocks-windows.mdx index 1c73e17..a87340e 100644 --- a/blogs/en/moodle-in-kubeblocks-windows.mdx +++ b/blogs/en/moodle-in-kubeblocks-windows.mdx @@ -11,7 +11,7 @@ keywords: KubeBlocks,MySQL Operator,Operatorization,Kubernetes,Moodle,Windows,XA image: /img/blogs/thumbnails/blog-moodle.png --- -# Deploy Moodle on K8s with KubeBlocks MySQL Operator (Windows) +# Deploy Moodle on K8s with KubeBlocks [MySQL](/docs/preview/kubeblocks-for-mysql) Operator (Windows) Moodle is a free online learning management system that allows educators to create their private websites, populate them with dynamic course content, and thereby enable people to learn anytime, anywhere. @@ -169,7 +169,7 @@ In this step, the entire installation is complete, and you can now freely use Mo For more detailed installation steps, please visit [Install Moodle - MoodleDocs](https://docs.moodle.org/404/en/Installing_Moodle). -## Prepare the Redis Database +## Prepare the [Redis](/docs/preview/kubeblocks-for-redis) Database ### Steps @@ -247,3 +247,10 @@ After clicking `Add instance`, fill in the basic settings. In this example, the After clicking `Save changes`, you will see `Handling connection` when you return to KubeBlocks. At this point, you can use Moodle more smoothly! ![Figure 17](/img/blogs/moodle-handling-check.png) + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [Deploy WordPress on KubeBlocks](/blog/deploy-wordpress-on-kubeblocks) +- [Deploy Harbor on KubeBlocks](/blog/deploy-harbor-on-kubeblocks) diff --git a/blogs/en/oci-tcp-blackhole-troubleshooting.mdx b/blogs/en/oci-tcp-blackhole-troubleshooting.mdx index 87e3ed3..f584de3 100644 --- a/blogs/en/oci-tcp-blackhole-troubleshooting.mdx +++ b/blogs/en/oci-tcp-blackhole-troubleshooting.mdx @@ -182,4 +182,10 @@ References: 2. [KubeBlocks Official Blog - SQLServer Addon](https://www.kubeblocks.com/addons/sqlserver) 3. [KubeBlocks Official Blog - KubeBlocks for MSSQL Always On AG Revealed](https://kubeblocks.io/blog/kubeblocks-for-mssql-always-on-ag-revealed) 4. [The strange 15mins timeout of Kubernetes Controller HA](https://duyanghao.github.io/kubernetes-ha-http-keep-alive-bugs/) -5. [In-depth analysis and optimization guide for net.ipv4.tcp_retries2](https://www.cnblogs.com/guoliushui/p/18971017) \ No newline at end of file +5. [In-depth analysis and optimization guide for net.ipv4.tcp_retries2](https://www.cnblogs.com/guoliushui/p/18971017) + +## Related + +- [KubeBlocks x MSSQL: Operator-Based Always On AG Revealed](/blog/kubeblocks-x-mssql-operator-based-always-on-ag-revealed) +- [KubeBlocks for MSSQL High Availability Implementation](/blog/kubeblocks-for-mssql-high-availability-implementation) +- [How to Fix Pods Stuck in Terminating Status in Kubernetes?](/blog/how-to-fix-pods-stuck-in-terminating-status) diff --git a/blogs/en/take-specified-instances-offline.mdx b/blogs/en/take-specified-instances-offline.mdx index 09c95ef..457217b 100644 --- a/blogs/en/take-specified-instances-offline.mdx +++ b/blogs/en/take-specified-instances-offline.mdx @@ -22,7 +22,7 @@ Before v0.9.0, KubeBlocks generated workloads as ***StatefulSets***, which was a One of these limitations is evident in horizontal scaling scenarios, where ***StatefulSets*** offload Pods sequentially based on the *Ordinal* order, potentially impacting the availability of databases running within. -For example, managing a PostgreSQL database with one primary and two secondary replicas using a ***StatefulSet*** named `foo-bar`. And Pod `foo-bar-2` is selected as the primary node. Now, if we decide to scale in this database cluster due to low read load, according to ***StatefulSet*** rules, we can only offload Pod `foo-bar-2`, which is currently the primary node. In this way, we can either directly offload `foo-bar-2`, triggering a failover mechanism to elect a new primary pod from `foo-bar-0` and `foo-bar-1`, or use a switchover mechanism to convert `foo-bar-2` into a secondary pod before offloading it. Either way, there will be a period where write is not applicable. +For example, managing a [PostgreSQL](/docs/preview/kubeblocks-for-postgresql) database with one primary and two secondary replicas using a ***StatefulSet*** named `foo-bar`. And Pod `foo-bar-2` is selected as the primary node. Now, if we decide to scale in this database cluster due to low read load, according to ***StatefulSet*** rules, we can only offload Pod `foo-bar-2`, which is currently the primary node. In this way, we can either directly offload `foo-bar-2`, triggering a failover mechanism to elect a new primary pod from `foo-bar-0` and `foo-bar-1`, or use a switchover mechanism to convert `foo-bar-2` into a secondary pod before offloading it. Either way, there will be a period where write is not applicable. Another issue arises in the same scenario: if the node hosting `foo-bar-1` experiences a hardware failure, causing disk damage and rendering data read-write inaccessible, according to best operation practices, we need to offload `foo-bar-1` and rebuild replicas on healthy nodes. However, performing such operation tasks based on ***StatefulSets*** isn't easy. @@ -101,3 +101,10 @@ In the Cluster API, both `OfflineInstances` and `Replicas` need to be modified s - [Discussions on Pod in the K8s community](https://github.com/kubernetes/kubernetes/issues/83224) - [The horizontal scale feature of KubeBlocks](https://kubeblocks.io/docs/release-0.9/api_docs/maintenance/scale/horizontal-scale) + +## Related + +- [InstanceSet: A New Approach to Stateful Workload Management in KubeBlocks](/blog/instanceset-introduction) +- [Gaining Granular Pod Control in KubeBlocks with Instance Templates](/blog/configure-instance-template) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) diff --git a/blogs/en/validating-kubeblocks-addon-availability-with-chaos-mesh.mdx b/blogs/en/validating-kubeblocks-addon-availability-with-chaos-mesh.mdx index 9e040ec..0e1ff77 100644 --- a/blogs/en/validating-kubeblocks-addon-availability-with-chaos-mesh.mdx +++ b/blogs/en/validating-kubeblocks-addon-availability-with-chaos-mesh.mdx @@ -73,7 +73,7 @@ Through declarative experiments, KubeBlocks' core high availability capabilities Taking the primary node Pod forced deletion scenario as an example: -1. **Environment Deployment:** KubeBlocks deploys the target database cluster (e.g., MySQL Cluster). +1. **Environment Deployment:** KubeBlocks deploys the target database cluster (e.g., [MySQL](/docs/preview/kubeblocks-for-mysql) Cluster). ![](/img/blogs/chaos-mesh/FL9lbzO1doRbSqxPAnkcs5BynKb.png) @@ -145,7 +145,7 @@ kubectl logs -n kubeblocks-cloud-ns mysql-875777cc4-mysql-1 lorry ### Test Results -Based on Chaos Mesh fault injection tests on various database engines managed by KubeBlocks (including MySQL, PostgreSQL, Redis, MongoDB, and SQLServer, etc.), the test results validated KubeBlocks' effectiveness in ensuring database high availability. +Based on Chaos Mesh fault injection tests on various database engines managed by KubeBlocks (including MySQL, [PostgreSQL](/docs/preview/kubeblocks-for-postgresql), [Redis](/docs/preview/kubeblocks-for-redis), [MongoDB](/docs/preview/kubeblocks-for-mongodb), and SQLServer, etc.), the test results validated KubeBlocks' effectiveness in ensuring database high availability. | **Test Scenario** | **Test Metric** | **Test Result** | |---|---|---| @@ -190,4 +190,12 @@ Through deep integration and practice of Chaos Mesh, KubeBlocks has initially es - [1] Introduction to Chaos Mesh: https://chaos-mesh.org/docs/ - [2] Introduction to KubeBlocks: https://kubeblocks.io/docs/preview/user_docs/overview/introduction -- [3] KubeBlocks v1.0.0 High Availability Test Report: https://kubeblocks.io/reports/kubeblocks/v1-0-0/TEST_REPORT_CHAOS \ No newline at end of file +- [3] KubeBlocks v1.0.0 High Availability Test Report: https://kubeblocks.io/reports/kubeblocks/v1-0-0/TEST_REPORT_CHAOS + +## Related + +- [KubeBlocks for MySQL — Operations Guide](/docs/preview/kubeblocks-for-mysql) +- [KubeBlocks for PostgreSQL — Operations Guide](/docs/preview/kubeblocks-for-postgresql) +- [KubeBlocks for Redis — Operations Guide](/docs/preview/kubeblocks-for-redis) +- [Managing Over 6,000 Self-Hosted Databases Without a DBA](/blog/manage-6k-db-instance-with-kubeblocks) +- [Run Databases on K8s: Insights from Leading Chinese Internet Companies](/blog/run-databases-on-k8s-insights-from-leading-chinese-internet-companies)