You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a FluxCD application is deployed successfully, the app status shows healthy. However, if something goes wrong and the application is technically unhealthy, there is a mismatch of the status.
On the app listing page, the status shows unhealthy for the infra-controllers app.
However, after clicking on the application and expanding it, it shows the status as healthy
👟 Reproduction steps
Deploy a FluxCD app via kustomize
Let it deploy successfully
Update the manifest in the Git repo to intentionally create a faulty deployment
Trigger or wait for a reconciliation
👍 Expected behavior
The application status shown in the app list page, and the status after clicking and expanding the application should match.
👎 Actual Behavior
There is a mismatch of the status
☸ Kubernetes version
GKE v1.31.4
Cloud provider
GKE
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
📜 Description
After a FluxCD application is deployed successfully, the app status shows healthy. However, if something goes wrong and the application is technically unhealthy, there is a mismatch of the status.
On the app listing page, the status shows unhealthy for the infra-controllers app.
However, after clicking on the application and expanding it, it shows the status as healthy
👟 Reproduction steps
👍 Expected behavior
The application status shown in the app list page, and the status after clicking and expanding the application should match.
👎 Actual Behavior
There is a mismatch of the status
☸ Kubernetes version
GKE v1.31.4
Cloud provider
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: