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

NetworkIsReachableProbe for registry has hard-coded http protocol and fails if registry is not listening on port 80 #9660

Closed
corneliusludmann opened this issue Apr 29, 2022 · 3 comments
Labels
priority: highest (user impact) Directly user impacting team: workspace Issue belongs to the Workspace team

Comments

@corneliusludmann
Copy link
Contributor

registry-facade [1, 2] and blobserve [3]. have readiness checks hardcoded with http protocol, e.g.:

health.AddReadinessCheck("registry", kubernetes.NetworkIsReachableProbe(fmt.Sprintf("http://%v", staticLayerRef)))

However, when the registry listens on port 443 only or the user specified a custom port in the Gitpod config like this:

repository: registry-1.testing.gitpod-self-hosted.com:5000/gitpod

The check fails because there is nothing listening on port 80 or the registry on the custom port speaks https only. The checks fail and the registy-facade would not start and would logs messages like this:

unexpected error checking URL http://registry-1.testing.gitpod-self-hosted.com/gitpod/supervisor:commit-2a82d5e93851dfddb79c28859509687da1858e33: Get \"http://registry-1.testing.gitpod-self-hosted.com/gitpod/supervisor:commit-2a82d5e93851dfddb79c28859509687da1858e33\": dial tcp 34.89.239.41:80: connect: connection refused

or

NetworkIsReachableProbe: unexpected status code checking URL

(internal discussion)

@corneliusludmann corneliusludmann added the team: workspace Issue belongs to the Workspace team label Apr 29, 2022
@corneliusludmann corneliusludmann added the priority: highest (user impact) Directly user impacting label May 2, 2022
@AllMight2099
Copy link

Hey there!
Is it possible to get access to Gitpod's slack? I would like to try solving this issue

@corneliusludmann
Copy link
Contributor Author

Hi @AllMight2099! Thank you very much for the initiative. Appreciate this!

Unfortunately, this has been fixed already by #9727 (sorry that we haven't closed this issue).

Are you interested in contributing something else? If you're interested, I'd be happy to help you to find another suitable issue.

@AllMight2099
Copy link

Oh, that's alright!
And yessssss! I would love to have your guidance. I want to work on Gitpod's infrastructure so I was thinking of picking up issues #9274 and #8021 cause it seems like it would give me a good opportunity to go through Gitpod's code. Would you recommend I take these issues up? Or are there other issues that you'd suggest I work on? Also, there's another link to an internal discussion for issue #8021, which I'd like to get access to, if that's possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: highest (user impact) Directly user impacting team: workspace Issue belongs to the Workspace team
Projects
No open projects
Archived in project
Development

No branches or pull requests

2 participants