[jbosstools-issues] [JBoss JIRA] (JBIDE-22165) Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon updated JBIDE-22165:
--------------------------------
    Fix Version/s: 4.4.0.Alpha2
                       (was: 4.4.x)
     Story Points: 5
           Sprint: devex #114 May 2017


> Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22165
>                 URL: https://issues.jboss.org/browse/JBIDE-22165
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.3.1.CR1
>            Reporter: Marián Labuda
>            Assignee: Thomas Mäder
>              Labels: deploy_docker_wizard, docker, openshift_v3
>             Fix For: 4.4.0.Alpha2
>
>
> I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself...
> At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)