From 2631858face9a66ee1bfbef34451c56c8d28be97 Mon Sep 17 00:00:00 2001 From: Jen Travinski Date: Wed, 24 Nov 2021 14:39:14 -0500 Subject: [PATCH] Update content/rancher/v2.5/en/deploy-across-clusters/fleet/_index.md Co-authored-by: Billy Tat --- content/rancher/v2.5/en/deploy-across-clusters/fleet/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.5/en/deploy-across-clusters/fleet/_index.md b/content/rancher/v2.5/en/deploy-across-clusters/fleet/_index.md index 61de588ea67..340c2de633b 100644 --- a/content/rancher/v2.5/en/deploy-across-clusters/fleet/_index.md +++ b/content/rancher/v2.5/en/deploy-across-clusters/fleet/_index.md @@ -52,7 +52,7 @@ For details on using Fleet behind a proxy, see [this page.](./proxy) * **Temporary Workaround:**
1. Find the two service account tokens listed in the fleet-controller and the fleet-controller-bootstrap service accounts. These are under the fleet-system namespace of the local cluster.
2. Remove the non-existent token secret. Doing so allows for only one entry to be present for the service account token secret that actually exists.
- 3. Delete the fleet-controller Pod in the fleet-system Namespace to reschedule.
+ 3. Delete the fleet-controller Pod in the fleet-system namespace to reschedule.
4. After the service account token issue is resolved, you can force redeployment of the fleet-agents. In the Rancher UI, go to **☰ > Cluster Management**, click on **Clusters** page, then click **Force Update**.
5. If the fleet-agent bundles remain in a `Modified` state after Step 4, update the field `spec.forceSyncGeneration` for the fleet-agent bundle to force re-creation.