[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ] 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? -- This message was sent by Atlassian JIRA (v7.2.3#72005)