Updated doc for adding support of Extended Duration Pods on GKE Autopilot (#4139)

* Updated the doc for adding support of Extended-Duration-Pods

* comments incorporated

Author: kamaljeeti

site/content/en/docs/Advanced/controlling-disruption.md

@@ -59,7 +59,7 @@ To maintain backward compatibility with Agones prior to the introduction of `evi
 {{</ alert >}}
 
 {{< alert title="Note" color="info" >}}
-GKE Autopilot supports only `Never` and `Always`, not `OnUpgrade`.
+GKE Autopilot supports only `Never` and `Always`, not `OnUpgrade`. However, with Kubernetes 1.27, Autopilot introduces support for `extended duration pods` that can run for up to `7 days`, helping to maintain game server sessions without disruption during this period.
 {{< /alert >}}
 
 ## What's special about ten minutes and one hour?
@@ -72,6 +72,9 @@ GKE Autopilot supports only `Never` and `Always`, not `OnUpgrade`.
 
 Outside of Cluster Autoscaler, the main source of disruption for long sessions is node upgrade. On some cloud products, such as GKE Standard, node upgrades are entirely within your control. On others, such as GKE Autopilot, node upgrade is automatic. Typical node upgrades use an eviction based, rolling recreate strategy, and may not honor `PodDisruptionBudget` for longer than an hour. See [Best Practices]({{< relref "Best Practices" >}}) for information specific to your cloud product.
 
+## [Extended Duration Pods in GKE Autopilot](https://cloud.google.com/kubernetes-engine/docs/how-to/extended-duration-pods) (Kubernetes 1.27+)
+Starting with Kubernetes 1.27, GKE Autopilot introduces support for extended duration pods, allowing them to run continuously for up to 7 days. This feature is ideal for game servers that need longer operational periods. It helps to minimize disruptions during node upgrades over the 7-day duration.
+
 ## Implementation / Under the hood
 
 Each option uses a slightly different permutation of: