[jbosstools-issues] [JBoss JIRA] (JBIDE-23015) Creating a route should have a default port

[ 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)