hanzoai/deploy
2
0
Fork 0
mirror of https://github.com/hanzoai/deploy.git synced 2026-10-07 08:44:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Improve switch to annotation tracking docs, clarifying that a new Git commit may be needed to avoid orphan resources (#25309)

Browse Source 
Signed-off-by: reggie-k <[email protected]>
This commit is contained in:
Regina Voloshin
2025-11-17 23:52:07 -10:00
committed by GitHub
parent 95437e1d52
commit df2ed4e92f
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/operator-manual/upgrading/2.14-3.0.md
+4 -1
View File
@@ -287,7 +287,10 @@ resources.
> resources to be orphaned. If the first sync operation after switching to annotation-based tracking includes a
> resource being deleted, Argo CD will fail to recognize that the resource is managed by the Application and will not
> delete it. To avoid this edge case, it is recommended to perform a sync operation on your Applications, even if
> they are not out of sync, so that orphan resource detection will work as expected on the next sync.
> they are not out of sync, so that orphan resource detection will work as expected on the next sync.
>
> After upgrading to version 3.0, the Argo CD tracking annotation will only appear on an Application’s resources when
> either a new Git commit is made or the Application is explicitly synced.
##### Users who rely on label-based for resources that are not managed by Argo CD
Some users rely on label-based tracking to track resources that are not managed by Argo CD. They may set annotations