You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to restart Che if anything is wrong (it seems to happens when messing around creating, renaming... workspaces), a /healthz page or similar would be useful.
Basically a HTTP GET on /healthz should just respond 200 and with content may be just ok if everything looks fine, and return any non-200 if something's wrong.
Example of similar implementation in some major projects:
I am doing bulk closing of older issues to reduce open enhancement requests from 250 down to 150 along with moving all related issues from Codenvy over to Che, and then further consolidating related issues into unified ones for easier tacking.
In this particular case, we are formalizing Che on k8s support for Che 6 and this will be handled within k8s policies.
In order to restart Che if anything is wrong (it seems to happens when messing around creating, renaming... workspaces), a
/healthz
page or similar would be useful.Basically a HTTP GET on
/healthz
should just respond 200 and with content may be justok
if everything looks fine, and return any non-200 if something's wrong.Example of similar implementation in some major projects:
The text was updated successfully, but these errors were encountered: