lsergio commented on issue #5552: URL: https://github.com/apache/camel-k/issues/5552#issuecomment-2135000892
In this specific case, I think the Deployment is correct by not reporting an error before the deadline expires. Per the [docs](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/), the deployment status should change to ProgressDeadlineExceeded after the 10min default timeout (or the progressDeadlineSeconds values) expires . And it does: ``` conditions: - lastTransitionTime: "2024-05-28T11:23:11Z" lastUpdateTime: "2024-05-28T11:23:11Z" message: Deployment does not have minimum availability. reason: MinimumReplicasUnavailable status: "False" type: Available - lastTransitionTime: "2024-05-28T11:24:12Z" lastUpdateTime: "2024-05-28T11:24:12Z" message: ReplicaSet "deploy-2f9e3f35-141a-46e6-a264-f5b82ad00adb-55659fcd77" has timed out progressing. reason: ProgressDeadlineExceeded status: "False" type: Progressing ``` For monitoring purposes, I have enabled the Health trait, and I consider the Integration to be healthy when the Ready condition is true, the KnativeServiceReady condition is also true when applicable. This allows me to detect when an Integration is successfully deployed My other use case, though, is to detect when an Integration is failing due to a bad component configuration that causes the CamelContext to not start. In this scenario, the Ready condition will be false, but I sill need to check the reason or phase to distinguish between a Camel Context that is still starting up and one that has failed. When it fails, the reason changes to Error and I can trigger an alert. Having that Error status also when the deployment is still in progress leads me to a false alert. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
