[
https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-23368 at 11/4/16 9:12 AM:
-------------------------------------------------------------------
[~mlabuda] yes, I agree and this was my initial impression, too (see
https://issues.jboss.org/browse/JBIDE-23352?focusedCommentId=13308084&...).
This seems to be confirmed by the fact that the web-ui wont allow you to add/remove ports.
Web-UI only allows you to chose the routing port.
On the ohter hand, offering this ability is giving power to the users and works as long as
the users take care to expose those ports on the pod/container.
[~jeffmaury] can you reiterate the reasons that made you think that we should allow users
to add/remove ports?
was (Author: adietish):
[~mlabuda] yes, I agree and this was my initial impression, too. This seems to be
confirmed by the fact that the web-ui wont allow you to add/remove ports. Web-UI only
allows you to chose the routing port.
On the ohter hand, offering this ability is giving power to the users and works as long as
the users take care to expose those ports on the pod/container.
[~jeffmaury] can you reiterate the reasons that made you think that we should allow users
to add/remove ports?
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)