claudio4j commented on issue #5084: URL: https://github.com/apache/camel-k/issues/5084#issuecomment-1904411102
> is the above described "deploying" behaviour on such deployment failure scenarios intended? Not on purpose. As you noted above, the camel-k-operator tries to set a field `startupProbe` on a knative service, which is not supported and the error is not handled, leaving the `Integration` object with the wrong status. In the knative-service trait we have to handle this scenario (health enabled) and not set that field. We have to document this case and have testing in place. -- 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
