docs: 1 year wait time for upgrading (#36784)

Follow-up to #36782

Author: def-

doc/user/content/self-managed-deployments/upgrading/_index.md

@@ -234,7 +234,7 @@ The behavior of the new version rollout follows your `rolloutStrategy` setting.
 #### *WaitUntilReady* - ***Default***
 
 `WaitUntilReady` creates a new generation of pods and automatically cuts over to them as soon as they catch up to the old generation and become `ReadyToPromote`. This strategy temporarily doubles the required resources to run Materialize.
-{{< warning >}} `WaitUntilReady` waits up to 72 hours (configurable by the `with_0dt_deployment_max_wait` flag) for the new pods to become ready. If the promotion has not occurred by then, the new pods are automatically promoted. {{< /warning >}}
+{{< warning >}} `WaitUntilReady` waits up to 1 year (configurable by the `with_0dt_deployment_max_wait` flag) for the new pods to become ready. If the promotion has not occurred by then, the new pods are automatically promoted. {{< /warning >}}
 
 #### *ImmediatelyPromoteCausingDowntime*
 {{< warning >}} Using the `ImmediatelyPromoteCausingDowntime` rollout flag will cause downtime. {{< /warning >}}