Added note to migration guide for expiration causing more pods in sch…

…eduling
aws · Dec 2, 2024 · 24838f5 · 24838f5
1 parent b2fcf44
commit 24838f5
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/website/content/en/v1.0/upgrading/v1-migration.md b/website/content/en/v1.0/upgrading/v1-migration.md
@@ -669,6 +669,7 @@ Revisit step 9 of the [upgrade procedure]({{< ref "#upgrading" >}}) and ensure t
   * NodePools now have [status conditions]({{< relref "../concepts/nodepools/#statusconditions" >}}) that indicate if they are ready. If not, then they will not be considered during scheduling.
   * NodeClasses now have [status conditions]({{< relref "../concepts/nodeclasses/#statusconditions" >}}) that indicate if they are ready. If they are not ready, NodePools that reference them through their `nodeClassRef` will not be considered during scheduling.
   * Karpenter will no longer set `associatePublicIPAddress` to false in private subnets by default. Users with IAM policies / SCPs that require this field to be set explicitly should configure this through their `EC2NodeClass` ([ref]({{<ref "../concepts/nodeclasses/#specassociatepublicipaddress">}})).
+  * Due to Node expiration, you may observe an increased number of pods in the "Scheduling" state.
 * API Moves:
   * ExpireAfter has moved from the `NodePool.Spec.Disruption` block to `NodePool.Spec.Template.Spec`, and is now a drift-able field.
   * `Kubelet` was moved to the EC2NodeClass from the NodePool.