Merge pull request #44 from apecloud/support/add-kb-release-notes

chore: add kb release notes

Author: shanshanying

blogs/en/instanceset-introduction.mdx

@@ -136,7 +136,7 @@ By default, InstanceSet updates each instance sequentially in descending order.
 
 If the instances are granted with roles (which will be discussed in the following sections), InstanceSet updates them according to their role priorities, starting from the lowest to the highest. If the role priorities are the same, the instances are updated further in descending ordinal order.
 
-InstanceSet supports more update behaviors by configuring `spec.updateStrategy`. For example, you can control the total number of instances to be updated using `spec.updateStrategy.rollingUpdate.partition` and manage the maximum number of unavailable instances during the update process with `spec.updateStrategy.rollingUpdate.maxUnavailable`. For more details, refer to the [`spec.updateStrategy` API documentation](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster#apps.kubeblocks.io/v1alpha1.UpdateStrategy).
+InstanceSet supports more update behaviors by configuring `spec.updateStrategy`. For example, you can control the total number of instances to be updated using `spec.updateStrategy.rollingUpdate.partition` and manage the maximum number of unavailable instances during the update process with `spec.updateStrategy.rollingUpdate.maxUnavailable`. For more details, refer to the [`spec.updateStrategy` API documentation](../user_docs/references/api-reference/cluster#apps.kubeblocks.io/v1alpha1.UpdateStrategy).
 
 ### In-place update
 

blogs/en/migrate-redis-in-kuaishou-from-bare-metal-to-k8s.mdx

@@ -38,7 +38,7 @@ Consider a typical setup, as shown in the image below, where a single instance o
 ![Data replication](/img/blogs/redis-kuaishou-2.png)
 
 1. This is a single point of failure - the system is highly vulnerable to outages.
-2. The throughput of a single Redis instance is inherently limited. 
+2. The throughput of a single Redis instance is inherently limited.
 3. The risk of data loss is extremely high.
 
 To address these problems, we can scale out the StatefulSet horizontally, increasing the number of replicas from one to three. But this introduces a new set of problems about managing the replication relationships between these replicas.
@@ -71,7 +71,7 @@ The first is called "[In-place Instance Update](https://kubeblocks.io/docs/previ
 
 ![In-place update](/img/blogs/redis-kuaishou-4.png)
 
-We divide database parameters into three types: **Immutable**, **Static** and **Dynamic**. 
+We divide database parameters into three types: **Immutable**, **Static** and **Dynamic**.
 
 - A immutable parameter cannot be changed once set.
 - A static parameter can be changed but need a database restart.
@@ -135,7 +135,7 @@ What are stateful services, and how do they differ from stateless ones?
 
 At first glance, the difference might seem as simple as whether or not the service maintains state information. However, we think **the real distinction lies in the unequal relationship between instances**. Different instances in a stateful service play different roles and store different data, making them irreplaceable. You can’t just discard any instance randomly. This unequal relationship is dynamic and can change during runtime, such as during a switchover. KubeBlocks is built to manage this complexity, offering **role-based management capabilities**.
 
-Furthermore, KubeBlocks supports multiple databases, **eliminating the need to create a dedicated operator for each one**. It also provides **process-oriented APIs through OpsRequest**, simplifying database migration. For those interested in the specifics, you can delve deeper into [KubeBlocks APIs in the official documentation](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster).
+Furthermore, KubeBlocks supports multiple databases, **eliminating the need to create a dedicated operator for each one**. It also provides **process-oriented APIs through OpsRequest**, simplifying database migration. For those interested in the specifics, you can delve deeper into [KubeBlocks APIs in the official documentation](../user_docs/references/api-reference/cluster).
 
 ![Why KubeBlocks](/img/blogs/redis-kuaishou-9.png)
 

docs/en/preview/kubeblocks-for-elasticsearch/02-quickstart.mdx

@@ -157,7 +157,7 @@ spec:
                 storage: 20Gi
 ```
 
-For more API fields and descriptions, refer to the [API Reference](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster).
+For more API fields and descriptions, refer to the [API Reference](../user_docs/references/api-reference/cluster).
 
 ## Verify Cluster Status
 

docs/en/preview/kubeblocks-for-kafka/02-quickstart.mdx

@@ -217,7 +217,7 @@ spec:
           memory: "0.2Gi"
 ```
 
-For more API fields and descriptions, refer to the [API Reference](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster).
+For more API fields and descriptions, refer to the [API Reference](../user_docs/references/api-reference/cluster).
 
 ## Verify Cluster Status
 

docs/en/preview/kubeblocks-for-milvus/02-quickstart.mdx

@@ -233,7 +233,7 @@ spec:
                 storage: 20Gi
 ```
 
-For more API fields and descriptions, refer to the [API Reference](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster).
+For more API fields and descriptions, refer to the [API Reference](../user_docs/references/api-reference/cluster).
 
 ## Verify Cluster Status
 

docs/en/preview/kubeblocks-for-mongodb/02-quickstart.mdx

@@ -255,7 +255,7 @@ spec:
                 storage: 20Gi
 ```
 
-For more API fields and descriptions, refer to the [API Reference](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster).
+For more API fields and descriptions, refer to the [API Reference](../user_docs/references/api-reference/cluster).
 
 ### Create a Version-Specific MongoDB ReplicaSet Cluster
 

docs/en/preview/kubeblocks-for-postgresql/02-quickstart.mdx

@@ -267,7 +267,7 @@ spec:
                 storage: 20Gi
 ```
 
-For more API fields and descriptions, refer to the [API Reference](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster).
+For more API fields and descriptions, refer to the [API Reference](../user_docs/references/api-reference/cluster).
 
 ### Create a Version-Specific PostgreSQL Cluster
 

docs/en/preview/kubeblocks-for-qdrant/02-quickstart.mdx

@@ -244,7 +244,7 @@ spec:
                 storage: 20Gi
 ```
 
-For more API fields and descriptions, refer to the [API Reference](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster).
+For more API fields and descriptions, refer to the [API Reference](../user_docs/references/api-reference/cluster).
 
 ### Create a Version-Specific Qdrant Cluster
 

docs/en/preview/kubeblocks-for-rabbitmq/02-quickstart.mdx

@@ -246,7 +246,7 @@ spec:
                 storage: 20Gi
 ```
 
-For more API fields and descriptions, refer to the [API Reference](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster).
+For more API fields and descriptions, refer to the [API Reference](../user_docs/references/api-reference/cluster).
 
 ### Create a Version-Specific RabbitMQ Cluster
 

docs/en/preview/kubeblocks-for-redis/02-quickstart.mdx

@@ -255,7 +255,7 @@ spec:
                 storage: 20Gi
 ```
 
-For more API fields and descriptions, refer to the [API Reference](https://kubeblocks.io/docs/preview/developer_docs/api-reference/cluster).
+For more API fields and descriptions, refer to the [API Reference](../user_docs/references/api-reference/cluster).
 
 ### Create a Version-Specific Redis Replication Cluster