-
Notifications
You must be signed in to change notification settings - Fork 149
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
fix: don't rewrite 127 to 0.0.0.0 #1051
Conversation
Signed-off-by: Michal Vala <mvala@redhat.com>
would it be an issue in pure DevWorkspace (where there is no all that gateways ?) |
yes, Theia won't be reachable then as it will listen on 127.0.0.1 only. |
FYI @sleshchenko standalone DW won't be able anymore to use the devfiles from che plug-in registry |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested DevWorkspace created with PR's registry and works fine
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: benoitf, sleshchenko, sparkoo The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@sleshchenko you're able to open a terminal inside che-theia ? with only DevWorkspace operator ? |
typescript error is not related to this change, safe to merge |
Signed-off-by: Michal Vala mvala@redhat.com
What does this PR do?
Don't replace 127.0.0.1. It is not secure to listen on all interfaces. After merging eclipse-che/che-operator#1045 it is no longer needed.
Screenshot/screencast of this PR
What issues does this PR fix or reference?
eclipse-che/che#20482
How to test this PR?
image
quay.io/mvala/che-plugin-registry:theiaSec
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.