[
https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi...
]
Jeff Cantrill edited comment on JBIDE-23015 at 8/31/16 8:28 AM:
----------------------------------------------------------------
Routes will by default use the port(s) specified by the service. You can explicitly
define one
https://github.com/openshift/origin/blob/master/pkg/route/api/types.go#L38
which can be an integer or named port on the services. If a port is not specified, I
believe it will round robin them. I believe there is still a limitation for services
which ties into this where you can specify a single port for a service to target or all of
them; you can not specify a subset. I mentioned that in another issue dealing with the
deploy image workflow.
Editing...the hitch to explicitly defining a port in the route is that it removes the
flexibility for someone to update the service port it exposes without changes to the
route. I'm not saying we shouldn't do it but its one drawback
was (Author: jcantrill):
Routes will by default use the port(s) specified by the service. You can explicitly
define one
https://github.com/openshift/origin/blob/master/pkg/route/api/types.go#L38
which can be an integer or named port on the services. If a port is not specified, I
believe it will round robin them. I believe there is still a limitation for services
which ties into this where you can specify a single port for a service to target or all of
them; you can not specify a subset. I mentioned that in another issue dealing with the
deploy image workflow.
Creating a route should have a default port
-------------------------------------------
Key: JBIDE-23015
URL:
https://issues.jboss.org/browse/JBIDE-23015
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.1.AM3
Reporter: Fred Bricon
Assignee: Jeff MAURY
Fix For: 4.4.1.Final
When deploying a docker image, in the Services and Routing settings, when "Add
route" is checked, if there are multiple ports exposed, then openshift will
round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is
for the web app, then 2/3 of the http connections to the service will fail.
There should be a new column, in the ports table, with 1 checkbox checkable at the time:
checking 1 box will uncheck the others.
The lowest port should be selected by default (that's what the oc client does
apparently, but deserve confirmation)
To reproduce:
- git clone
https://github.com/redhat-helloworld-msa/aloha
- mvn package
- build docker image from Dockerfile, to CDK docker connection
- deploy docker image to openshift
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)