christophd opened a new issue, #5351: URL: https://github.com/apache/camel-k/issues/5351
### What happened? The E2E test TestHealthTrait ([health_test.go](https://github.com/apache/camel-k/blob/main/e2e/common/traits/health_test.go#L368)) reveals a flaw that we have for quite some time regarding the Integration condition ready status. An integration with heath trait enabled becomes ready for a short period of time regardless of the health evaluation. This is because before the health trait may evaluate the integration ready status the Deployment ready state has already reported the ready condition to be true. This leads to the situation that a non ready integration (according to the health trait) becomes ready for a short amount of time just after the deployment has become ready. We should make sure to have a consistent ready condition status on the integration resource. When health trait is enabled this should be the source of truth for the ready condition. ### Steps to reproduce 1. Start an integration that never becomes ready according to the health trait (like E2E TestHealthTrait does) 2. Check for the integration condition status to never become ready 3. Make sure to only report ready status based on the health trait evaluation ### Relevant log output _No response_ ### Camel K version 2.3.0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
