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
The integrated healthcheck should be able to check a HTTP a status code.
E.g. we are deploying an K3D cluster inside out workspace. The healthcheck is already green but user facing a 404 error page from kubernetes as the app is not up and running. Checking against a status code 200 should solve this.
Setting a explicit statuscode should change the default checking.
Button should be enabled when application is ready and not when kubernetes cluster has started. If a statuscode 200 is set then the button gets enabled when the application is ready.
Actual Behavior
As soon kubernetes cluster is ready the healtcheck is green and buttons are enabled
The text was updated successfully, but these errors were encountered:
Description
The integrated healthcheck should be able to check a HTTP a status code.
E.g. we are deploying an K3D cluster inside out workspace. The healthcheck is already green but user facing a 404 error page from kubernetes as the app is not up and running. Checking against a status code 200 should solve this.
Setting a explicit statuscode should change the default checking.
Expected Behavior
Button should be enabled when application is ready and not when kubernetes cluster has started. If a statuscode 200 is set then the button gets enabled when the application is ready.
Actual Behavior
As soon kubernetes cluster is ready the healtcheck is green and buttons are enabled
The text was updated successfully, but these errors were encountered: