add missing nodeclass status conditions

aws · May 29, 2024 · 0c1f3d5 · 0c1f3d5
1 parent 1967f7a
commit 0c1f3d5
Show file tree

Hide file tree

Showing 4 changed files with 101 additions and 2 deletions.
diff --git a/website/content/en/docs/concepts/nodeclasses.md b/website/content/en/docs/concepts/nodeclasses.md
@@ -1246,3 +1246,36 @@ spec:
 status:
   instanceProfile: "${CLUSTER_NAME}-0123456778901234567789"
 ```
+
+## status.conditions
+
+[`status.conditions`]({{< ref "#statusconditions" >}}) indicates EC2NodeClass readiness. This will be `Ready` when Karpenter successfully discovers AMIs, Instance Profile, Subnets, Cluster CIDR and SecurityGroups for the EC2NodeClass.
+
+```yaml
+spec:
+  role: "KarpenterNodeRole-${CLUSTER_NAME}"
+status:
+  conditions:
+    Last Transition Time:  2024-05-06T06:04:45Z
+    Message:               Ready
+    Reason:                Ready
+    Status:                True
+    Type:                  Ready
+```
+
+If any of the underlying conditions are not resolved then `Status` is `False` and `Message` indicates the dependency that was not resolved.
+
+```yaml
+spec:
+  role: "KarpenterNodeRole-${CLUSTER_NAME}"
+status:
+  conditions:
+    Last Transition Time:  2024-05-06T06:19:46Z
+    Message:               unable to resolve instance profile for node class
+    Reason:                NodeClassNotReady
+    Status:                False
+    Type:                  Ready
+```
+{{% alert title="Note" color="primary" %}}
+An EC2NodeClass that uses AL2023 requires the cluster CIDR for launching nodes. Cluster CIDR will not be resolved for EC2NodeClass that doesn't use AL2023.
+{{% /alert %}}
diff --git a/website/content/en/preview/concepts/nodeclasses.md b/website/content/en/preview/concepts/nodeclasses.md
@@ -1246,3 +1246,36 @@ spec:
 status:
   instanceProfile: "${CLUSTER_NAME}-0123456778901234567789"
 ```
+
+## status.conditions
+
+[`status.conditions`]({{< ref "#statusconditions" >}}) indicates EC2NodeClass readiness. This will be `Ready` when Karpenter successfully discovers AMIs, Instance Profile, Subnets, Cluster CIDR and SecurityGroups for the EC2NodeClass.
+
+```yaml
+spec:
+  role: "KarpenterNodeRole-${CLUSTER_NAME}"
+status:
+  conditions:
+    Last Transition Time:  2024-05-06T06:04:45Z
+    Message:               Ready
+    Reason:                Ready
+    Status:                True
+    Type:                  Ready
+```
+
+If any of the underlying conditions are not resolved then `Status` is `False` and `Message` indicates the dependency that was not resolved.
+
+```yaml
+spec:
+  role: "KarpenterNodeRole-${CLUSTER_NAME}"
+status:
+  conditions:
+    Last Transition Time:  2024-05-06T06:19:46Z
+    Message:               unable to resolve instance profile for node class
+    Reason:                NodeClassNotReady
+    Status:                False
+    Type:                  Ready
+```
+{{% alert title="Note" color="primary" %}}
+An EC2NodeClass that uses AL2023 requires the cluster CIDR for launching nodes. Cluster CIDR will not be resolved for EC2NodeClass that doesn't use AL2023.
+{{% /alert %}}
diff --git a/website/content/en/v0.37/concepts/nodeclasses.md b/website/content/en/v0.37/concepts/nodeclasses.md
@@ -1246,3 +1246,36 @@ spec:
 status:
   instanceProfile: "${CLUSTER_NAME}-0123456778901234567789"
 ```
+
+## status.conditions
+
+[`status.conditions`]({{< ref "#statusconditions" >}}) indicates EC2NodeClass readiness. This will be `Ready` when Karpenter successfully discovers AMIs, Instance Profile, Subnets, Cluster CIDR and SecurityGroups for the EC2NodeClass.
+
+```yaml
+spec:
+  role: "KarpenterNodeRole-${CLUSTER_NAME}"
+status:
+  conditions:
+    Last Transition Time:  2024-05-06T06:04:45Z
+    Message:               Ready
+    Reason:                Ready
+    Status:                True
+    Type:                  Ready
+```
+
+If any of the underlying conditions are not resolved then `Status` is `False` and `Message` indicates the dependency that was not resolved.
+
+```yaml
+spec:
+  role: "KarpenterNodeRole-${CLUSTER_NAME}"
+status:
+  conditions:
+    Last Transition Time:  2024-05-06T06:19:46Z
+    Message:               unable to resolve instance profile for node class
+    Reason:                NodeClassNotReady
+    Status:                False
+    Type:                  Ready
+```
+{{% alert title="Note" color="primary" %}}
+An EC2NodeClass that uses AL2023 requires the cluster CIDR for launching nodes. Cluster CIDR will not be resolved for EC2NodeClass that doesn't use AL2023.
+{{% /alert %}}
diff --git a/website/content/en/v0.37/getting-started/getting-started-with-karpenter/_index.md b/website/content/en/v0.37/getting-started/getting-started-with-karpenter/_index.md
@@ -32,7 +32,7 @@ Install these tools before proceeding:
 
 1. [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2-linux.html)
 2. `kubectl` - [the Kubernetes CLI](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/)
-3. `eksctl` (>= v0.169.0) - [the CLI for AWS EKS](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html)
+3. `eksctl` (>= v0.179.0) - [the CLI for AWS EKS](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html)
 4. `helm` - [the package manager for Kubernetes](https://helm.sh/docs/intro/install/)
 
 [Configure the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html)
@@ -46,7 +46,7 @@ After setting up the tools, set the Karpenter and Kubernetes version:
 ```bash
 export KARPENTER_NAMESPACE="kube-system"
 export KARPENTER_VERSION="0.37.0"
-export K8S_VERSION="1.29"
+export K8S_VERSION="1.30"
 ```
 
 Then set the following environment variable: