diff --git a/website/content/en/docs/upgrading/v1beta1-migration.md b/website/content/en/docs/upgrading/v1beta1-migration.md index 9f1580b535df..7f340e6d537e 100644 --- a/website/content/en/docs/upgrading/v1beta1-migration.md +++ b/website/content/en/docs/upgrading/v1beta1-migration.md @@ -142,12 +142,12 @@ The [`karpenter-convert`](https://github.com/aws/karpenter/tree/release-v0.32.x/ 12. Roll over nodes: With the new NodePool yaml in hand, there are several ways you can begin to roll over your nodes to use the new NodePool: - 1. Periodic Rolling with [Drift]({{< relref "../concepts/disruption#drift" >}}): Enable [drift]({{< relref "../reference/settings/#feature-gates" >}}) in Karpenter, then do the following: + 1. Periodic Rolling with [Expiration]({{< relref "../concepts/disruption#automated-methods" >}}): - Add the following taint to the old Provisioner: `karpenter.sh/legacy=true:NoSchedule` - - Wait as Karpenter marks all machines owned by that Provisioner as having drifted. + - Set the Expiration in your Provisioner to a small value like `ttlSecondsUntilExpired: 300` to mark all nodes older than 5 minutes as expired. *Please note that in beta APIs, this is the same as `disruption.expireAfter`* - Watch as replacement nodes are launched from the new NodePool resource. - Because Karpenter will only roll of one node at a time, it may take some time for Karpenter to completely roll all nodes under a Provisioner. + Because Karpenter will only roll one node at a time, it may take some time for Karpenter to completely roll all nodes under a Provisioner. 2. Forced Deletion: For each Provisioner in your cluster: diff --git a/website/content/en/preview/upgrading/v1beta1-migration.md b/website/content/en/preview/upgrading/v1beta1-migration.md index 9f1580b535df..7f340e6d537e 100644 --- a/website/content/en/preview/upgrading/v1beta1-migration.md +++ b/website/content/en/preview/upgrading/v1beta1-migration.md @@ -142,12 +142,12 @@ The [`karpenter-convert`](https://github.com/aws/karpenter/tree/release-v0.32.x/ 12. Roll over nodes: With the new NodePool yaml in hand, there are several ways you can begin to roll over your nodes to use the new NodePool: - 1. Periodic Rolling with [Drift]({{< relref "../concepts/disruption#drift" >}}): Enable [drift]({{< relref "../reference/settings/#feature-gates" >}}) in Karpenter, then do the following: + 1. Periodic Rolling with [Expiration]({{< relref "../concepts/disruption#automated-methods" >}}): - Add the following taint to the old Provisioner: `karpenter.sh/legacy=true:NoSchedule` - - Wait as Karpenter marks all machines owned by that Provisioner as having drifted. + - Set the Expiration in your Provisioner to a small value like `ttlSecondsUntilExpired: 300` to mark all nodes older than 5 minutes as expired. *Please note that in beta APIs, this is the same as `disruption.expireAfter`* - Watch as replacement nodes are launched from the new NodePool resource. - Because Karpenter will only roll of one node at a time, it may take some time for Karpenter to completely roll all nodes under a Provisioner. + Because Karpenter will only roll one node at a time, it may take some time for Karpenter to completely roll all nodes under a Provisioner. 2. Forced Deletion: For each Provisioner in your cluster: diff --git a/website/content/en/v0.32/upgrading/v1beta1-migration.md b/website/content/en/v0.32/upgrading/v1beta1-migration.md index d46845077595..86e5b8e2fc2f 100644 --- a/website/content/en/v0.32/upgrading/v1beta1-migration.md +++ b/website/content/en/v0.32/upgrading/v1beta1-migration.md @@ -142,12 +142,12 @@ The [`karpenter-convert`](https://github.com/aws/karpenter/tree/release-v0.32.x/ 12. Roll over nodes: With the new NodePool yaml in hand, there are several ways you can begin to roll over your nodes to use the new NodePool: - 1. Periodic Rolling with [Drift]({{< relref "../concepts/disruption#drift" >}}): Enable [drift]({{< relref "../reference/settings/#feature-gates" >}}) in Karpenter, then do the following: + 1. Periodic Rolling with [Expiration]({{< relref "../concepts/disruption#automated-methods" >}}): - Add the following taint to the old Provisioner: `karpenter.sh/legacy=true:NoSchedule` - - Wait as Karpenter marks all machines owned by that Provisioner as having drifted. + - Set the Expiration in your Provisioner to a small value like `ttlSecondsUntilExpired: 300` to mark all nodes older than 5 minutes as expired. *Please note that in beta APIs, this is the same as `disruption.expireAfter`* - Watch as replacement nodes are launched from the new NodePool resource. - Because Karpenter will only roll of one node at a time, it may take some time for Karpenter to completely roll all nodes under a Provisioner. + Because Karpenter will only roll one node at a time, it may take some time for Karpenter to completely roll all nodes under a Provisioner. 2. Forced Deletion: For each Provisioner in your cluster: diff --git a/website/content/en/v0.33/upgrading/v1beta1-migration.md b/website/content/en/v0.33/upgrading/v1beta1-migration.md index 9f1580b535df..7f340e6d537e 100644 --- a/website/content/en/v0.33/upgrading/v1beta1-migration.md +++ b/website/content/en/v0.33/upgrading/v1beta1-migration.md @@ -142,12 +142,12 @@ The [`karpenter-convert`](https://github.com/aws/karpenter/tree/release-v0.32.x/ 12. Roll over nodes: With the new NodePool yaml in hand, there are several ways you can begin to roll over your nodes to use the new NodePool: - 1. Periodic Rolling with [Drift]({{< relref "../concepts/disruption#drift" >}}): Enable [drift]({{< relref "../reference/settings/#feature-gates" >}}) in Karpenter, then do the following: + 1. Periodic Rolling with [Expiration]({{< relref "../concepts/disruption#automated-methods" >}}): - Add the following taint to the old Provisioner: `karpenter.sh/legacy=true:NoSchedule` - - Wait as Karpenter marks all machines owned by that Provisioner as having drifted. + - Set the Expiration in your Provisioner to a small value like `ttlSecondsUntilExpired: 300` to mark all nodes older than 5 minutes as expired. *Please note that in beta APIs, this is the same as `disruption.expireAfter`* - Watch as replacement nodes are launched from the new NodePool resource. - Because Karpenter will only roll of one node at a time, it may take some time for Karpenter to completely roll all nodes under a Provisioner. + Because Karpenter will only roll one node at a time, it may take some time for Karpenter to completely roll all nodes under a Provisioner. 2. Forced Deletion: For each Provisioner in your cluster: