From 54a2f80c9d02fcbcf1717a3f247d11cc16ce74a4 Mon Sep 17 00:00:00 2001 From: Niall Thomson Date: Fri, 27 Sep 2024 13:21:57 -0600 Subject: [PATCH] fix: Skip testing node watch --- .../managed-node-groups/basics/adding-nodes/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/fundamentals/managed-node-groups/basics/adding-nodes/index.md b/website/docs/fundamentals/managed-node-groups/basics/adding-nodes/index.md index 20ce910fb..85e6eae6d 100644 --- a/website/docs/fundamentals/managed-node-groups/basics/adding-nodes/index.md +++ b/website/docs/fundamentals/managed-node-groups/basics/adding-nodes/index.md @@ -20,7 +20,7 @@ $ aws eks update-nodegroup-config --cluster-name $EKS_CLUSTER_NAME \ After making changes to the node group it may take up to **2-3 minutes** for node provisioning and configuration changes to take effect. Let's retrieve the nodegroup configuration again and look at **minimum size**, **maximum size** and **desired capacity** of nodes using `eksctl` command below: -```bash +```bash hook=wait-node $ eksctl get nodegroup --name $EKS_DEFAULT_MNG_NAME --cluster $EKS_CLUSTER_NAME ``` @@ -30,7 +30,7 @@ Monitor the nodes in the cluster using the following command with the `--watch` It can take a minute or so for the node to appear in the output below, if the list still shows 3 nodes be patient. ::: -```bash hook=wait-node +```bash test=false $ kubectl get nodes --watch NAME STATUS ROLES AGE VERSION ip-10-42-104-151.us-west-2.compute.internal Ready 3h vVAR::KUBERNETES_NODE_VERSION