Argo cd notification annotation in Application grow unbounded? #27722
-
|
I understand the notification controller use the Here's my annotation list just after a couple deployments |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
No, the notifications-engine caps it at 100 entries. There is a |
Beta Was this translation helpful? Give feedback.
-
|
Oh gotcha that makes sense thank you!
…On Tue, May 19, 2026 at 5:48 AM Vijay S ***@***.***> wrote:
No, the notifications-engine caps it at 100 entries. There is a notifiedHistoryMaxSize
= 100 constant in state.go and on every persist cycle the truncate
function drops the oldest entries first until it is back at 100. So even if
it is already bloated it will clean itself up on the next reconcile.
—
Reply to this email directly, view it on GitHub
<#27722 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD7WDW7MGTARMXW7YL2KDXT43RJY5AVCNFSM6AAAAACYTMTKHKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOJXGYZDSNQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
No, the notifications-engine caps it at 100 entries. There is a
notifiedHistoryMaxSize = 100constant in state.go and on every persist cycle the truncate function drops the oldest entries first until it is back at 100. So even if it is already bloated it will clean itself up on the next reconcile.