[jbosstools-issues] [JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13307719#comment-13307719 ] 

Andre Dietisheim commented on JBIDE-23368:
------------------------------------------

I am not sure yet, if this issue is a valid issue. I am currently trying to find out whether our wizard to deploy docker images is right in offering to the ability to add, remove and edit ports.
CLI requires you to do manual steps, web-ui wont allow you, it only shows you the ports that are explosed by the docker image and allow you to pick the routing port.

> Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23368
>                 URL: https://issues.jboss.org/browse/JBIDE-23368
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.2.AM2
>            Reporter: Marián Labuda
>              Labels: deploy_docker_wizard, openshift_v3
>
> When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available)
> Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless).



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