wmedvede opened a new issue, #3365: URL: https://github.com/apache/incubator-kie-kogito-runtimes/issues/3365
### Description I the context of kogito-serverless-operator managed kubernetes deployments, it was discussed that it could be nice to have a startup health check to verify the availability of the DataIndex and the JobsService, in order for a given kogito-runtime Pod to start. Since the runtime depends on these services. By having these checks, we can use the kubernetes provided mechanisms to configure a startupProbe that queries these startup health check, and we can maintain more robust kubernetes deployments. Additionally, we can provide some degree of optimization over an initContainers based equivalent check, that might involve more containers initialization, and higher memory consuming deployments. At the runtime side, these checks are disabled by default, and won't execute/interfere with standalone deployments. Instead, they must be explicitly enabled to work. At the kubernetes side, the startupProbes will be automatically generated by kogito-serverless-operator when the DI and JS are detected/configured in the current namespace/cluster. ### Implementation ideas _No response_ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
