From 4aaa76420a4348cae274822781df1ffa195f7a30 Mon Sep 17 00:00:00 2001
From: Badrish Shanbhag <124841347+badrish-s@users.noreply.github.com>
Date: Tue, 16 Jan 2024 13:52:00 -0800
Subject: [PATCH] Update faq.md

Updated faq.md to reflect the correct default behavior for Karpenter Drift in v0.33.x (issue : https://github.com/aws/karpenter-provider-aws/issues/5466)
---
 website/content/en/v0.33/faq.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/en/v0.33/faq.md b/website/content/en/v0.33/faq.md
index 517c725eb24a..72220ec20a21 100644
--- a/website/content/en/v0.33/faq.md
+++ b/website/content/en/v0.33/faq.md
@@ -211,7 +211,7 @@ For information on upgrading Karpenter, see the [Upgrade Guide]({{< ref "./upgra
 
 ### How do I upgrade an EKS Cluster with Karpenter?
 
-When upgrading an Amazon EKS cluster, [Karpenter's Drift feature]({{<ref "./concepts/disruption#drift" >}}) can automatically upgrade the Karpenter-provisioned nodes to stay in-sync with the EKS control plane. Karpenter Drift currently needs to be enabled using a [feature gate]({{<ref "./reference/settings#feature-gates" >}}).
+When upgrading an Amazon EKS cluster, [Karpenter's Drift feature]({{<ref "./concepts/disruption#drift" >}}) can automatically upgrade the Karpenter-provisioned nodes to stay in-sync with the EKS control plane. Karpenter Drift is enabled by default starting v0.33.x using Drift=true in [feature gate]({{<ref "./reference/settings#feature-gates" >}}).
 
 {{% alert title="Note" color="primary" %}}
 Karpenter's default [EC2NodeClass `amiFamily` configuration]({{<ref "./concepts/nodeclasses#specamifamily" >}}) uses the latest EKS Optimized AL2 AMI for the same major and minor version as the EKS cluster's control plane, meaning that an upgrade of the control plane will cause Karpenter to auto-discover the new AMIs for that version.