[jbosstools-issues] [JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata

[Jiri Pechanec (JIRA)]

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

Jiri Pechanec commented on JBIDE-21448:
---------------------------------------

{noformat}
docker inspect registry.access.redhat.com/jboss-eap-7/eap70-openshift
            "ExposedPorts": {
                "8080/tcp": {},
                "8443/tcp": {},
                "8778/tcp": {}
            },
{noformat}
But if you run the pod with EAP it has management port available bound on localhost - port 9990. It is useful to be able to easily port-forward to such port too

> Port Forwarding: Allow port-forwarding of ports not defined on pod metadata
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-21448
>                 URL: https://issues.jboss.org/browse/JBIDE-21448
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.3.1.Beta1
>            Reporter: Jiri Pechanec
>            Priority: Critical
>              Labels: openshift_v3, port_forwarding_wizard
>             Fix For: 4.5.0.AM2
>
>
> Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too.
> And example is EAP CLI



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)