gansheer commented on issue #3877: URL: https://github.com/apache/camel-k/issues/3877#issuecomment-1339260065
Thank you for the workaround, I will test it. I don't know how efficient the lookup of the port can be after any improvment done. Since the default quarkus port can be changed using `--property quarkus.http.ssl-port=8444` or `--property quarkus.http.port=8081`, I get the feeling that the real truth for the probe should be the quarkus runtime configuration, but I could be missing something. I tried just to check, and as expected we have the same problem with the http in case of overriding the http port using a property. And I didn't even try to change the endpoint yet :smirk:. I don't know if these modifications should be something the _health_ trait should be able to work with :confused:. My opinion is : offering the possibility of an option to provide health probe port would be a good idea. At least, adding the default static configuration to 8443 in case of HTTPS scheme could also be a good default configuration if the default 8080 is kept as fallback static port for the HTTP scheme. -- 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
