[
https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi...
]
Marián Labuda commented on JBIDE-23368:
---------------------------------------
In that case it does not make sense to add new ports in the wizard page. Bcs. those ports
listed in the table are obtained from docker image, adding additional ports would not make
sense. I think ports in the table are retrieved from image metadata and if something went
wrong and it was not retrieved, it would be bug on tooling side and we should fix it. But
adding ports mapping does not make sense for 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)