From dff4152e8e0adaad6156f963003be60fac4ff1a4 Mon Sep 17 00:00:00 2001
From: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
Date: Thu, 17 Oct 2024 04:05:13 -0400
Subject: [PATCH] docs: update note about timeout.reconciliation (#20407)

Signed-off-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
---
 docs/operator-manual/argocd-cm.yaml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/operator-manual/argocd-cm.yaml b/docs/operator-manual/argocd-cm.yaml
index ea7cee4638e6e..59edf5f156bd1 100644
--- a/docs/operator-manual/argocd-cm.yaml
+++ b/docs/operator-manual/argocd-cm.yaml
@@ -325,7 +325,8 @@ data:
 
   # Application reconciliation timeout is the max amount of time required to discover if a new manifests version got
   # published to the repository. Reconciliation by timeout is disabled if timeout is set to 0. Three minutes by default.
-  # > Note: argocd-repo-server deployment must be manually restarted after changing the setting.
+  # > Note: The argocd-repo-server deployment and the argocd-application-controller statefulset (or deployment, if
+  # configured) must be manually restarted after changing the setting.
   timeout.reconciliation: 180s
   # With a large number of applications, the periodic refresh for each application can cause a spike in the refresh queue
   # and can cause a spike in the repo-server component. To avoid this, you can set a jitter to the sync timeout, which will