-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Display warning instead of error if ports 80/443 in use #11600
Display warning instead of error if ports 80/443 in use #11600
Conversation
[test] |
Evaluated for origin test up to 86f064f |
@coreydaley this change looks good to me and we should make it, but it doesn't quite fix the #10665 issue. We're checking that we can open those ports on the server, which we need to. However, in the case we do port-forwarding and start 'socat' (which is only required for the Mac), we also need to make sure that the client machine allows opening ports 80 and 443. If not, we should print warnings. Maybe we should do that on a separate PR. |
LGTM [merge] |
test failure was due to #11560 |
@bparees ptal |
[merge] |
flake #10773 |
Evaluated for origin merge up to 86f064f |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10757/) (Base Commit: 0403599) |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10770/) (Base Commit: 5494a7e) (Image: devenv-rhel7_5262) |
Display warnings if ports 80 and/or 443 are already in use instead of an error,
as these ports are only needed for routing requests to the applications
Replaces pull request #10717