-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Regression issue: Wrong port in OpenShift route #16089
Comments
Thanks for reporting! Actually the best way to fix this would be to remove
from the Route definition altogether. @iocanel how can we do that? |
Not sure if this is behavior between different openshift versions, or a doc issue, but I'll have to look at it closer.
|
Yeah, that is nice for getting around the problems now, but the OOTB Route doesn't work - which we definitely need to fix for users :) |
I ran into this again today - @iocanel is this on one your radar? |
This has been fixed in dekorate. Will update to the latest version and align tests asap! |
Is it an issue in 1.13 too? If so, we would need a fix there too. |
It shouldn't affect 1.13 as this is a regression introdcued with dekorate 2.x. |
Yeah, this affects main only |
Describe the bug
(Describe the problem clearly and concisely.)
Actual behavior
The port in the route is set to 80 and it should be 8080.
To Reproduce
Steps to reproduce the behavior:
mvn io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:create -DprojectGroupId=org.acme -DprojectArtifactId=openshift-quickstart -DclassName="org.acme.rest.GreetingResource" -Dpath="/greeting" -Dextensions=openshift
openshift-quickstart
mvn package -Dquarkus.kubernetes.deploy=true -Dquarkus.openshift.expose=true
The maven command finished ok, but when trying to have access to the application, the route endpoint always gets 503 Gateway error.
The problem is that the port is set to 80 and it should be 8080.
See the whole content of the openshift.yml file:
Environment (please complete the following information):
Quarkus version or git rev
999-SNAPSHOT
(It works fine in 1.12+ and 1.13.0.Final)
Additional context
I think this is another regression issue caused by this change. Another related issue is #15953
The text was updated successfully, but these errors were encountered: