Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check servers health before setting status to running #78

Merged
merged 1 commit into from
May 25, 2020

Conversation

amisevsk
Copy link
Collaborator

What does this PR do?

Adds polling to ${ideUrl}/healthz and doesn't set Running phase for workspace until endpoint is responding.

Expects a 2xx response, but will proceed on a 404 for compatibility.

What issues does this PR fix or reference?

503 errors in OpenShift Terminal

Is it tested? How?

Depends on eclipse-che/che-machine-exec#105 ideally. Image is built and available at docker.io/amisevsk/che-machine-exec:dev, which you can use in the internal registry for testing.

Tested on crc with updated image and with default image that doesn't have /healthz endpoint.

On my local crc, I typically see 2-3 seconds of 503 errors before getting a 200

Check /healthz endpoint on

Signed-off-by: Angel Misevski <amisevsk@redhat.com>
Copy link
Contributor

@JPinkney JPinkney left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Member

@sleshchenko sleshchenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good quick solution!

Later we're able to extend it and pull in plugin meta.yaml model.

@@ -18,7 +18,6 @@ spec:
attributes:
protocol: http
type: ide
path: /static/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wonder if we keep web app on that endpoint... Then probably healthz endpoint should be defined as a separate configuration for endpoint I suppose.
So, please consider creating an issue to extend plugin meta model with health checks.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants