Add a blog to introduce "MultipleHubs".

Signed-off-by: xuezhaojun <[email protected]>

content/en/blog/_index.md

@@ -3,6 +3,12 @@ title: Blog
 weight: 6
 ---
 
+---
+### [The HA Hub clusters solution -- MultipleHubs]({{< ref "/blog/multiplehubs" >}})
+- Authors: [Zhao Xue](https://github.com/xuezhaojun)
+- Date: Aug 11, 2024
+---
+
 ----
 ### [Using the GitOps way to deal with the upgrade challenges of multi-cluster tool chains]({{< ref "/blog/addon-rollout" >}})
 - Authors: [郝青](https://github.com/haoqing0110)
@@ -26,7 +32,7 @@ weight: 6
 - Date: Oct 26, 2022
 ----
 ### [Karmada and Open Cluster Management: two new approaches to the multicluster fleet management challenge](https://www.cncf.io/blog/2022/09/26/karmada-and-open-cluster-management-two-new-approaches-to-the-multicluster-fleet-management-challenge/)
-- Authors: [David Eads](https://github.com/deads2k) and [Kevin Wang](https://github.com/kevin-wangzefeng) 
+- Authors: [David Eads](https://github.com/deads2k) and [Kevin Wang](https://github.com/kevin-wangzefeng)
 - Date: Sep 26, 2022
 ----
 ### [Extending the Multicluster Scheduling Capabilities with Open Cluster Management Placement](https://cloud.redhat.com/blog/extending-the-multicluster-scheduling-capabilities-with-open-cluster-management-placement)
@@ -45,10 +51,10 @@ weight: 6
 - Authors: [Min Kim](https://github.com/yue9944882) and [Jian Qiu](https://github.com/qiujian16)
 - Date: Sep 22, 2021
 ----
-### [Put together a user walk through for the basic Open Cluster Management API using `kind`, `olm`, and other open source technologies](https://github.com/mdelder/open-cluster-management-getting-started) 
+### [Put together a user walk through for the basic Open Cluster Management API using `kind`, `olm`, and other open source technologies](https://github.com/mdelder/open-cluster-management-getting-started)
 - Authors: [Michael Elder](https://github.com/mdelder)
 - Date: May 24, 2021
 ----
 ### [Setting up Open Cluster Management the hard way](https://github.com/sdminonne/ocm-the-hard-way)
-- Authors: [Dario Minonne](https://github.com/sdminonne) 
+- Authors: [Dario Minonne](https://github.com/sdminonne)
 - Date: April 22, 2021

content/en/blog/multiplehubs/_index.md

@@ -0,0 +1,75 @@
+---
+title: The HA Hub clusters solution -- MultipleHubs
+---
+
+August 11, 2024 [Zhao Xue](https://github.com/xuezhaojun)
+
+{{<toc>}}
+
+The `MultipleHubs` is a new feature in Open Cluster Management (OCM) that allows you to configure a list of bootstrapkubeconfigs of multiple hubs. This feature is designed to provide a high availability (HA) solution of hub clusters. In this blog, we will introduce the MultipleHubs feature and how to use it.
+
+The high availability of hub clusters means that if one hub cluster is down, the agent clusters can still communicate with other hub clusters. Users can also specify the hub cluster that the agent cluster should connect to by configuring the `ManagedCluster` resource.
+
+The `MultipleHubs` feature is currently in the experimental stage and is disabled by default. To enable the `MultipleHubs` feature, you need to set the `featureGate` in `Klusterlet`'s registration configuration. The following is an example of the `Klusterlet`'s registration configuration:
+
+```yaml
+apiVersion: operator.open-cluster-management.io/v1
+kind: Klusterlet
+...
+spec:
+  ...
+  registrationConfiguration:
+    ...
+    featureGates:
+      - feature: MultipleHubs
+        mode: Enable
+```
+
+If `MultipleHubs` is enabled, you don't need to prepare the default `bootstrapKubeConfig` for the agent. The agent will use the `bootstrapKubeConfigs` in the `Klusterlet`'s registration configuration to connect to the hub clusters. An example of `bootstrapKubeConfigs` is like following:
+
+```yaml
+apiVersion: operator.open-cluster-management.io/v1
+kind: Klusterlet
+...
+spec:
+  ...
+  registrationConfiguration:
+    ...
+    featureGates:
+      - feature: MultipleHubs
+        mode: Enable
+    bootstrapKubeConfigs:
+      type: "LocalSecrets"
+      localSecretsConfig:
+        kubeConfigSecrets:
+            - name: "hub1-bootstrap"
+            - name: "hub2-bootstrap"
+        hubConnectionTimeoutSeconds: 600
+```
+
+In the above configuration, the `hub1-bootstrap` and `hub2-bootstrap` are the secrets that contain the kubeconfig of the hub clusters. You should create the secrets before you set the `bootstrapKubeConfigs` in the `Klusterlet`'s registration configuration.
+
+The order of the secrets in the `kubeConfigSecrets` is the order of the hub clusters that the agent will try to connect to. The agent will try to connect to the first hub cluster in the list first. If the agent cannot connect to the first hub cluster, it will try to connect to the second hub cluster, and so on.
+
+Note that the expiration time of the credentials in kubeconfigs should be long enough to ensure the agent can connect to another hub cluster when one hub cluster is down.
+
+The `hubConnectionTimeoutSeconds` is the timeout for the agent to connect to the hub clusters. If the agent cannot connect to the hub cluster within the timeout, it will try to connect to another hub cluster. It is also used to avoid the effect of network disturbance. The default value is 600 seconds and the minimum value is 180 seconds.
+
+Currently, the `MultipleHubs` feature only supports the `LocalSecrets` type of `bootstrapKubeConfigs`.
+
+As we mentioned before, you can also specify the hub's connectivities in the `ManagedCluster` resource from the hub side. We using the `hubAcceptsClient` field in the `ManagedCluster` resource to specify whether the hub cluster accepts the agent cluster. The following is an example of the `ManagedCluster` resource:
+
+```yaml
+apiVersion: cluster.open-cluster-management.io/v1
+kind: ManagedCluster
+...
+spec:
+  ...
+  hubAcceptsClient: false
+```
+
+If the `hubAcceptsClient` is set to `false`, the agent cluster currently connected to the hub will immediately disconnect from the hub and try to connect to another hub cluster.
+
+And the agent clusters that are trying to connect to another hub cluster will ignore the hub cluster that the managedcluster's `hubAcceptsClient` is set to `false`.
+
+That's the brief introduction of the `MultipleHubs` feature in Open Cluster Management. We hope this feature can help you to start building a high availability solution of hub clusters and we are looking forward to your feedback. If you have any questions or suggestions, please feel free to contact us.