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

[Jeff Cantrill (JIRA)]

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

Jeff Cantrill commented on JBIDE-23368:
---------------------------------------

[~mlabuda]This was originally added because even though an image metadata does not indicate an image will be listening on a port, it still could be.  For example, a debug port is open but I did not explicitly declare it in the dockerfile.  Adding still allows you to configure a service that will expose the port.  However, [~adietish] and I had a long discussion about this issue and I believe we agreed on doing one of the following:

* Remove the functionality all together to be consistent with the web ui
* Modify button desc, add text to explain the ramifications, update the table to make it obvious these ports are not exposed

I'm not certain what the right direction is other then we should probably follow the web and console as examples.  You could always make the argument that a user can manually edit a service if an image does not explicitly expose ports.  This seems reasonable to me.

> 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
>            Assignee: Andre Dietisheim
>              Labels: deploy_docker_wizard, openshift_v3
>             Fix For: 4.4.2.AM3
>
>
> 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
(v7.2.3#72005)