-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
App.status.health.LastTransitionTime
missing from Application Status
#22192
Comments
Issue was created per @andrii-korotkov-verkada request. |
Did you recently upgrade from an earlier version? The last transition time was added in 2.14, so older apps may not have it. But once you deploy an app, it should get it. |
I have tried deploying after upgrading the version, no What's making me suspicious that the application-controller doesn't update this field, is this log message from the application-controller pod - Can you help with that as well? |
Ah, when upgrading the app, did you upgrade the install manifest as well including the CRD with types definitions? |
Using a helm release - 7.8.8 |
Seems like Argo CD CRDs are not updated to latest during upgrade. Can you confirm if CRDs are updated on cluster? $ kubectl get crd applications.argoproj.io -o yaml|grep LastTransitionTime
.......
description: LastTransitionTime is the time the condition was
description: LastTransitionTime is the time the HealthStatus was
description: LastTransitionTime is the time the HealthStatus I created a Argo CD Application with 2.14.4 and could see the status:
....
health:
lastTransitionTime: "2025-03-06T11:37:53Z"
status: Healthy |
It is present in the CRD
|
There are multiple
|
It is not under
|
Okay, then the CRDs are not updated during upgrade. Are CRD upgrades disabled in your helm chart install? |
I will need to upgrade manually in that case. |
I recommend discussing at the contributors meeting about why upgrade doesn't happen https://docs.google.com/document/d/1xkoFkVviB70YBzSEa4bDnu-rUZ1sIFtwKKG1Uw8XsY8/edit?tab=t.0 |
I figured out why the crd upgrade didn't happen. |
Maybe CRD needs a sync wave to be defined before the application controller? You can configure in your overlays if deploying argo with argo |
Checklist:
argocd version
.Describe the bug
Missing field in Application status, causing the suggested trigger for on-deployed template example to fail to send.
Noticed this log warn message by Application-controller
To Reproduce
notifications.argoproj.io/subscribe.on-deployed.slack: "slack-channel"
Expected behavior
Notification sent for an application deployment successfully.
Screenshots
Version
Paste the output from `argocd version` here. argocd: v2.14.4+3d901f2 BuildDate: 2025-03-04T22:56:08Z GitCommit: 3d901f2037888af302a85f518bea70b33ee8e1c7 GitTreeState: clean GoVersion: go1.24.0 Compiler: gc Platform: darwin/arm64 argocd-server: v2.14.2+ad27246
The text was updated successfully, but these errors were encountered: