You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/10/21 09:20:59 UTC

[GitHub] [camel-k] astefanutti commented on issue #3761: Ready condition message not always taken from Camel Health Check

astefanutti commented on issue #3761:
URL: https://github.com/apache/camel-k/issues/3761#issuecomment-1286692583

   To add some historical background, the first iteration of that mechanism, that probes into the Camel runtime, has been conservative, so the health endpoint is only probed when the underlying Deployment controller, reports a truthy _progressing_ condition.
   
   Now that this mechanism has proved both useful and reliable, the proposition would be to also probe the health endpoint when the Deployment has ended progression (and also generalising for other underlying controllers), so a more detailed error message can be reported, and fallback on the generic message provided by the underlying controller if probing the endpoint fails, e.g. when the pod(s) is/are not running. 


-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org