From 328f915d2ac767add43448c89820f7c2bb86b782 Mon Sep 17 00:00:00 2001 From: Lenny Chen Date: Tue, 18 Jun 2024 15:20:16 -0700 Subject: [PATCH] docs: move cluster definition page --- .../clusters/edge/site-deployment/cluster-deployment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs-content/clusters/edge/site-deployment/cluster-deployment.md b/docs/docs-content/clusters/edge/site-deployment/cluster-deployment.md index 12c4c5c7aa..fe3842681d 100644 --- a/docs/docs-content/clusters/edge/site-deployment/cluster-deployment.md +++ b/docs/docs-content/clusters/edge/site-deployment/cluster-deployment.md @@ -188,7 +188,7 @@ review detailed logs. 4. Review the **Cluster Status**. Ensure the **Cluster Status** field displays **Running**. You can also use the command `kubectl get nodes` to review the status of all nodes in the cluster. Check out the -[Access Cluster with CLI](../../../cluster-management/palette-webctl.md) guide to learn how to use `kubectl` with a host +[Access Cluster with CLI](../../cluster-management/palette-webctl.md) guide to learn how to use `kubectl` with a host cluster. ## Add an Edge Host to a Host Cluster @@ -198,7 +198,7 @@ node pool. ### Limitations -- In a multi-node cluster with [PXK-E](../../../../integrations/kubernetes-edge.md) as its Kubernetes layer, you cannot +- In a multi-node cluster with [PXK-E](../../../integrations/kubernetes-edge.md) as its Kubernetes layer, you cannot change custom Network Interface Card (NIC). When you add an Edge host to such a cluster, leave the NIC field as its default value.