[ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugi... ] Jeff Cantrill edited comment on JBIDE-20601 at 10/20/15 9:37 AM: ----------------------------------------------------------------- [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service editing based clarification <code> pweil: externally, routes are only ever available on 80/443 (ingress to the router). The route itself points to either a) a specific port or b) all ports <code> was (Author: jcantrill): [~maxandersen] revisiting this issue as some movement has been made upstream. Routes point to a service and can be configured to: * allow access to every port exposed by the service * allow access to a specific port exposed by the service Current implementation produces the former which is what we desire. What more do we need to provide? It seems to me we should allow a user to modify the exposed port which should be addressed in JBIDE-20531. We may need additional prompts and texts to clarify what this page allows you to configure. User's may wish to have additional routes, but I think that should be a follow-on action; this flow is supposed to be the fastest path to deploying an image. We should consider closing this issue or modifying it to reflect the need for additional verbiage for the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)