From cf4c80282659e13f5d6f143279b5c7fc0e8287ee Mon Sep 17 00:00:00 2001 From: xuezhao Date: Tue, 5 Nov 2024 15:22:16 +0800 Subject: [PATCH] Fix tabpane display issue. (#435) Signed-off-by: xuezhaojun --- .../docs/getting-started/installation/register-a-cluster.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/getting-started/installation/register-a-cluster.md b/content/en/docs/getting-started/installation/register-a-cluster.md index b365c7d0..1d89e4c3 100644 --- a/content/en/docs/getting-started/installation/register-a-cluster.md +++ b/content/en/docs/getting-started/installation/register-a-cluster.md @@ -96,7 +96,7 @@ The hosted mode deploying is till in experimental stage, consider to use it only In hosted mode, the cluster where the klusterlet is running is called the hosting cluster. Running the following command to the hosting cluster to register the managed cluster to the hub. -{{< tabpane header="clusteradm join" >}} +{{< tabpane text=true >}} {{% tab header="kind" %}} ```shell # NOTE for KinD clusters: @@ -136,7 +136,7 @@ cluster. **Note:** to run klusterlet in singleton mode, you must have a clusteradm version equal or higher than `v0.12.0` -{{< tabpane header="clusteradm join" >}} +{{< tabpane text=true >}} {{% tab header="kind" %}} ```shell # NOTE: For KinD clusters use the parameter: --force-internal-endpoint-lookup