-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected Transient Degraded Status Change During Application Rolling Deployments in Argo CD 2.13.1 #21198
Comments
we've observed the same issue with 2.13.2 as well
|
Thank you @andrii-korotkov-verkada for volunteering to investigate. @atilsensalduz @neiljain Can you share what your apps look like and what healthchecks your resources are using? |
Hey guys, our applications follow a similar structure to the one below. We’ve encountered the same issue across different applications, not specific to one. ArgoCD application:
|
Can you enable debug logs for the application controller and share all the logs relevant to the application, please? |
After upgrading Argo CD to version 2.13.1, I've started observing unusual status behavior in my applications during rolling deployments or restarts. Specifically:
The application status briefly changes to Degraded, and then immediately back to Healthy, even though I can't identify any actual health issues in the deployment components.
I’ve reviewed the application events and didn’t find any readiness or liveness probe failures, or other indicators of degraded health in the resources.
This behavior triggers Degraded state notifications, but since there’s no option to send notifications for transitions from Degraded to Healthy, I end up receiving alerts for transient states that quickly resolve themselves.
This issue was not observed before the upgrade and only seems to happen during rolling deployments or restarts.
Has anyone encountered similar behavior or could this be a regression or configuration issue with health checks in 2.13.1? Any advice on fixing or mitigating this would be greatly appreciated!
Thanks in advance for your help!
The text was updated successfully, but these errors were encountered: