public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-08-17 23:01:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update content/rancher/v2.5/en/deploy-across-clusters/fleet/_index.md

Browse Source 
Co-authored-by: Billy Tat <btat@suse.com>
This commit is contained in:
Jen Travinski
2021-11-24 14:39:14 -05:00
committed by GitHub
co-authored by Billy Tat
parent f40f06ab42
commit 2631858fac
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.5/en/deploy-across-clusters/fleet/_index.md
+1 -1
View File
@@ -52,7 +52,7 @@ For details on using Fleet behind a proxy, see [this page.](./proxy)
* **Temporary Workaround:** </br>
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. </br>
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. </br>
3. Delete the fleet-controller Pod in the fleet-system Namespace to reschedule. </br>
3. Delete the fleet-controller Pod in the fleet-system namespace to reschedule. </br>
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**. </br>
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.