One of the steps in workspace startup is waiting for any servers to be ready. It would be convenient if plugin specs could define an endpoint which can be pinged to check for server readiness/health.
Add health check endpoints to plugin meta model. Potentially a liveness and readiness definition, parallel to what exists in Kubernetes.
Rely on communicating with a port defined for the plugin.
The Che workspace operator needs to be able to check for server readiness before marking a workspace as 'Running', to avoid 503 errors. See PR https://github.com/che-incubator/che-workspace-operator/pull/78 for details.
I believe we have similar issues on Hosted Che when for example theia route is not yet available - https://github.com/redhat-developer/rh-che/issues/1657 / https://github.com/eclipse/che/issues/17542
@ericwill I put P1, but feel free to update the priority based on the team priorities
Not sure which area this one actually falls under -- there's a plugin side change somewhere, but the plugin spec changes would mostly be handled by infra/plugin broker. @ibuziuk @ericwill WDYT about:
Is it something that should be addressed in Devfile 2.x format? @l0rd @davidfestal WDYT?
Most helpful comment
Not sure which area this one actually falls under -- there's a plugin side change somewhere, but the plugin spec changes would mostly be handled by infra/plugin broker. @ibuziuk @ericwill WDYT about: