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

Andre Dietisheim (JIRA) issues at jboss.org
Fri Nov 4 04:36:00 EDT 2016


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

Andre Dietisheim edited comment on JBIDE-23368 at 11/4/16 4:35 AM:
-------------------------------------------------------------------

[~mlabuda] the basic takeaway here is the following: the port mapping in the wizard is purely operating on the service. It wont open ports on the pods/containers, it just makes sure that the user can have service ports exposed. If those ports actually are backed by container ports (that are listened to and reachable: actual daemon running, port exposed via docker -p or -P) is not in the scope of this wizard. The wizard therefore should not add those ports to the replication controller, which operates pods.
[~jcantrill] Can you please chime in and provide more details/insights?


was (Author: adietish):
[~mlabuda] the basic takeaway here is the following: the port mapping in the wizard is a purely operating on the service. It wont open ports on the ports, it just makes sure existing ports (that you can expose in the Dockerfile or when launching the container) are specified in the service. If those ports actually are backed by container ports (that are listened to and reachable) is not in the scope of this wizard. It's up to the developer to make sure the service ports are actually backed by the containers in the port. The wizard therefore should not add those ports to the replication controller, which operates pods.
[~jcantrill] Can you please chime in and provide more details/insights?

> 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)



More information about the jbosstools-issues mailing list